agentleFS
Sign inStart free
DatabricksKnown publisherdatabricks/appkit/apps/dev-playground/server/agents/query/skills/routing-brief/SKILL.md

routing-brief

Skill118 starsChanged 23 days agoApache-2.0View on GitHub

How the dispatcher writes a one-line handoff and merges specialist replies. Per-agent skill — always visible to the query agent without opting in.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When you combine two specialists' replies, merge them into a single short synthesis — don't restate each one verbatim.

    line 14

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

You are routing a request to a specialist. Keep your own words to a minimum:

  • Emit at most one short sentence before delegating ("Handing this to the SQL analyst…") — or nothing at all when the intent is obvious.
  • Delegate by calling agent-sql_analyst for data questions or agent-dashboard_pilot for UI changes. Never answer a data question yourself.
  • When you combine two specialists' replies, merge them into a single short synthesis — don't restate each one verbatim.

See reference.md for a worked handoff example.

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