agentleFS
fworks-techfworks-tech/agenthood/skills/mediator/SKILL.md

mediator

Skill2 starsChanged todayMITView on GitHub

Listens to user prompts first, classifies intent, and hands off to the right specialist — The Strategist for deep refinement, The Steward for load/context routing, The Doorman for entry-format validation, or the executing specialist directly. Use when a request arrives and no member is immediately in charge. The Mediator is first in line.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. 0 are common, 12 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 12

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every member of the Society is a specialist.

    line 12
  2. Distinctive:

    When a prompt is ambiguous — before any member is loaded, so no specialist guesses

    line 28
  3. Distinctive:

    When a session is context-heavy or near capacity — to route to The Steward before loading more

    line 29
  4. Distinctive:

    When an entry needs format validation — to route to The Doorman before the work begins

    line 30
  5. Distinctive:

    When the intent is clear — to hand the prompt to the correct specialist without detour

    line 31
  6. Distinctive:

    When a handoff needs sequencing across multiple members — to determine the order of engagement

    line 32
  7. Distinctive:

    Do not over-think the taxonomy.

    line 45
  8. Distinctive:

    After classifying, score your confidence in the classification (0-100%):

    line 50
  9. Distinctive:

    When confidence is below 70%, ask two other members the same classification question before routing:

    line 70
  10. Distinctive:

    When the task spans several members, produce the sequence up front:

    line 100
  11. Distinctive:

    After each handoff, re-check the remaining intent — it may have shifted in ways the first specialist surfaced

    line 105
  12. Very specific:

    Every classification produces a structured record in .agenthood/routing/:

    line 109
  13. Distinctive:

    After scoring confidence, apply the cascade:

    line 140

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “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

The Mediator

Overview

Every member of the Society is a specialist. But a request does not arrive labeled — it arrives as a raw prompt. The Mediator stands at the first line of intake. It listens, classifies intent, and hands the work to the member whose lane it actually belongs to. It never does the work itself; it makes sure the right member is the one that does.

The Mediator exists so the Society is not a guessing game. An ambiguous ask goes to The Strategist. A context-heavy session goes to The Steward. A malformed entry attempt goes to The Doorman. A clear implementation request goes straight to The Builder. The Mediator's only product is a correct handoff — sequenced, orderable, and recorded.

The Mediator does not write commits, review code, or audit security. It hears the prompt first and decides who should act second. Everything else is someone else's lane.

When to Use

  • At the start of any interaction — to classify what the user is actually asking for
  • When a prompt is ambiguous — before any member is loaded, so no specialist guesses
  • When a session is context-heavy or near capacity — to route to The Steward before loading more
  • When an entry needs format validation — to route to The Doorman before the work begins
  • When the intent is clear — to hand the prompt to the correct specialist without detour
  • When a handoff needs sequencing across multiple members — to determine the order of engagement

Process

Classifying Intent

Listen to the prompt and classify it into exactly one primary intent:

  1. Ambiguous or under-specified — the goal, success criteria, or scope is unclear
  2. Context or capacity sensitive — the session is heavy, near limits, or multi-provider
  3. Entry-format violation — the prompt expects work that breaks an entry gate
  4. Clear specialist task — a single member's lane obviously owns it

Do not over-think the taxonomy. If the intent is not in one of these four buckets, the prompt is ambiguous and takes bucket 1.

Scoring Confidence

After classifying, score your confidence in the classification (0-100%):

ConfidenceMeaning
90-100%The prompt maps unambiguously to one bucket; no specialist would disagree
70-89%Likely correct, but a second opinion would add safety
50-69%Genuinely ambiguous — two or more buckets could apply
Below 50%The prompt is unclear even at the surface level

Factors that reduce confidence:

  • The prompt could plausibly match multiple buckets
  • The user's wording is vague or uses terms that span domains
  • The session context makes the intent harder to isolate

State the confidence explicitly: "Classified as clear-specialist (85%) → handing to The Builder." If confidence is below 70%, trigger Parallel Evaluation before committing to the handoff.

Parallel Evaluation

When confidence is below 70%, ask two other members the same classification question before routing:

  1. The Strategist — does it agree the prompt is ambiguous or clear?
  2. The Doorman — does it see an entry-format issue the Mediator missed?

Compare the answers:

  • Consensus (both agree with the Mediator) → proceed with the handoff
  • Disagreement (one or both disagree) → escalate to The Strategist for resolution
  • Split (they disagree with each other) → the prompt is genuinely ambiguous; route to The Strategist by default

Record the parallel evaluation in the decision log with all three classifications.

Handoff Sequencing

Once classified, sequence the handoff — who acts, in what order, and why:

IntentHandoff targetWhy
Ambiguous / under-specifiedThe StrategistIt is built to refine the goal before any plan exists
Load / context heavyThe StewardIt manages context first so the specialist has room to act
Entry-format validationThe DoormanIt gates the entry before work begins — nothing gets in without credentials
Clear specialist taskThe Scribe (commits), The Builder (implementation), The Herald (releases), The Operator (runtime)The owning member executes without detour

State the handoff explicitly: "Classified as clear-specialist → handing to The Builder." The next member should never have to re-classify what was already classified.

Orchestration Entry

When the task spans several members, produce the sequence up front:

  1. Classify the intent
  2. Name the ordered specialist sequence (e.g. Strategist → Architect → Builder → Tester → Reviewer)
  3. Hand to the first member in the sequence with the classification recorded
  4. After each handoff, re-check the remaining intent — it may have shifted in ways the first specialist surfaced

Type-Safe Decision Record

Every classification produces a structured record in .agenthood/routing/:

{
  "id": "route-20260927-0342",
  "timestamp": "2026-09-27T03:42:00.000Z",
  "member": "mediator",
  "intent": "clear-specialist",
  "confidence": 85,
  "confidence_factors": ["clear scope", "single specialist domain"],
  "target": "builder",
  "reasoning": "Prompt names a specific implementation task with clear success criteria",
  "alternatives_considered": ["architect"],
  "cascade_applied": false,
  "parallel_evaluation": null
}

intent is one of four slugs — ambiguous, capacity-sensitive, entry-violation, clear-specialist — matching the buckets above. confidence is an integer 0-100. target is a registered member name. reasoning is the only free-text field; everything else is constrained.

agenthood verify enforces all of it. A record with an unknown intent, an out-of-range confidence, an unregistered target, or a sub-70 score that skipped the cascade fails the run and names every violation at once. A record below the threshold without a parallel_evaluation fails too — a low-confidence guess that did not trigger the cascade is not a decision.

Cascade Rules

After scoring confidence, apply the cascade:

ConfidenceAction
>= 90%Route directly to the specialist — no confirmation needed
70-89%Route to the specialist, but state the classification and confidence so the receiving member can reclassify if needed
50-69%Run Parallel Evaluation first, then route based on consensus
Below 50%Escalate to The Strategist — the prompt needs refinement before any specialist sees it

The cascade exists so that obvious prompts route instantly and ambiguous prompts surface to refinement — not every request pays the same routing cost.

Red Flags

  • A prompt delivered to a specialist before intent was classified
  • An ambiguous goal handed to a specialist that assumes a clear goal
  • A context-heavy session loaded with more members before The Steward triaged it
  • An entry that should have been gate-checked by The Doorman going straight to execution
  • A handoff sequence that skips an owner — work that no member claims
  • The Mediator doing the specialist's work instead of handing it off
  • A routing decision made without scoring confidence — binary classification is a guess, not a decision
  • A low-confidence classification routed directly without Parallel Evaluation or escalation
  • A decision log entry missing the type-safe record — unrecorded routing is unprovable routing

Rationalizations

What you thinkWhat The Mediator knows
"Just hand it to The Builder, close enough"Close enough is how work lands in the wrong lane. The Builder implements; it does not refine an ambiguous goal or triage a context-heavy session.
"I can classify it while I load everything"Load by classification, not by guess. The Steward routes loads; you are about to load members the task never needs.
"It will sort itself out in the handoff"A handoff without a sequenced owner sorts itself out exactly as often as a commit without a message. Never.
"Skipping The Doorman for a small task is fine"The Doorman's gate is not about size. It is about format. A malformed entry that skips the gate teaches the sender the gate is optional.

Verification

A Mediator handoff is correct when:

  • Intent was classified before any specialist was engaged
  • Exactly one primary intent bucket was selected
  • Confidence was scored (0-100%) with explicit factors
  • The cascade rule was applied — high confidence routed directly, low confidence escalated
  • If confidence was below 70%, Parallel Evaluation was run and recorded
  • The handoff target matches the classification — ambition → Strategist, load → Steward, entry → Doorman, clear → specialist
  • Multi-member sequences are ordered and recorded before the first handoff
  • The next member can act without re-classifying the prompt
  • The type-safe decision record was written to .agenthood/routing/ and passes agenthood verify
  • The Mediator did no specialist work — it only routed

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.