agentleFS
Sign inStart free
tunahanaliozturktunahanaliozturk/atelier/skills/capability-routing/SKILL.md

capability-routing

Skill1 starsChanged 5 months agoMITView on GitHub

Use when the lead assigns a task to an agent, to match the task to the best-fit specialist by capability.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. farky-tech/containers★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

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:

    Call route(task, agents). It coarse-filters by layer and task_kinds, scores each candidate by task_kinds and capabilities overlap, and …

    line 13
  2. Very specific:

    If route returns fallback: true, no agent fits.

    line 16

≈ “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

Capability Routing

Route each task with the lib/routing.mjs helper, then apply judgment:

  1. Build the task descriptor { kind, layer?, capabilities? } from the planner's tagged step. The registry is in context from the SessionStart hook; if it is not (a session started without the hook), read the agents/ directory with readRegistry first.
  2. Call route(task, agents). It coarse-filters by layer and task_kinds, scores each candidate by task_kinds and capabilities overlap, and breaks ties deterministically (score descending, then name ascending).
  3. If route returns fallback: true, no agent fits. Do not force a poor match: tell the user and use the writing-agents skill to scaffold a new agent that follows the capability schema.
  4. Otherwise take pick as the default. You may override it for a documented reason by reading the candidates' descriptions — but record the final choice and the reason (including the score) in the mission decision log.

The orchestration and review layers are cross-cutting: the planner, lead, and reviewers are invoked by name in a fixed order, not selected by this filter.

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.

Check your setup, free