agentleFS
ashley-eyekyamashley-eyekyam/probematrix-learnings-coach/skills/interface-learnings/SKILL.md

interface-learnings

Skill0 starsChanged 27 days agoMITView on GitHub

Find the learnings that fall between departments in a ProbeMatrix investigation - handovers, shared ownership, unclear authority and assumptions one function made about another (operations and maintenance, maintenance and procurement, engineering and integrity, security and control room, leadership and emergency command…). Use when someone asks what fell through the cracks, about silos, handovers, cross-functional or interface failures, who should have been talking to whom, or how to design a cross-department review after an incident.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write the pack <run>/outputs/interface-learnings.json (schema: learnings-coach/references/pack-schema.md), then:

    line 32
  2. Very specific:

    Put data-quality corrections in data_quality, findings left out on purpose in exclusions, and same-condition findings in supporting_cites.

    line 47

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interface Learnings

Engine: PMLC = python3 <skills-root>/learnings-coach/scripts/pmlc.py (this skill needs the learnings-coach skill installed alongside it). Needs clusters.json.

Gather

PMLC interfaces <ws> --top 25

Each pair has shared findings (both entities named on the same finding) and cross-entity causal mentions (a finding owned by one entity names a factor owned by the other in its causal explanation). Rank interfaces by both. Take the top eight to twelve.

For each interface read the examples: PMLC select <ws> --entity <A> <B> --entity-mode all --brief (the findings both entities share), then the full text of the highest-rated ones.

For each interface, write

  • The seam: what passes between the two functions (a work order, a part, a test, an alarm, a decision, a document).
  • What went wrong at the seam: assumption, gap in ownership, missing hand-back, conflicting priorities, authority that sat with neither.
  • Why neither side saw it on its own.
  • The learning for each side in one sentence.
  • A joint fix: a hold point, a shared check, a single owner, a handover record, a joint review. Name the control tier.
  • A leading indicator both sides can see.
  • Evidence trail.

Output

Write the pack <run>/outputs/interface-learnings.json (schema: learnings-coach/references/pack-schema.md), then:

PMLC check-pack <ws> <run>/outputs/interface-learnings.json   # fix every problem it lists
PMLC pack <ws> <run>/outputs/interface-learnings.json         # -> interface-learnings.html (primary) and .md

Sections and the kinds that fill them:

  • Matrix: a table with columns Interface, Shared findings and Cross-entity causal mentions. Use the top pairs from interfaces, with their examples as row_cites.
  • One section per interface, with id = the pair (e.g. f02-f06):
    • para items with group = "The seam", "What went wrong at the seam" or "Why neither side saw it".
    • A learning for each side, with owner = that side.
    • The joint fix as a recommendation, with a hoc_tier and an indicator both sides can see.
  • Who must meet whom: a closing section of check items.

Put data-quality corrections in data_quality, findings left out on purpose in exclusions, and same-condition findings in supporting_cites.

{"kind": "learning", "group": "The learning for each side", "lesson": "Stores: …", "owner": "Materials Management (F06)",
 "cites": ["FND-…"]}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.