agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/route-work/SKILL.md

route-work

Skill14 starsChanged 3 months agoMITView on GitHub

Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Route Work”. A useful skill states the six fields from Skills and routines. Incoming work must be assigned to exactly one owner Bot. The router does not do the work. Exactly one owner. Handoff message contains outcome and approval boundary. You produced no domain deliverable of your own. Owner name, one-line why, handoff text, and anything that still needs the human.

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:

    Do not do the specialist's job "just this once".

    line 39

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

Route Work

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Route Work”.

A useful skill states the six fields from Skills and routines.

1. When to use it

Incoming work must be assigned to exactly one owner Bot. The router does not do the work.

2. Required inputs and access

  • The request
  • The current roster (names and jobs)
  • Group membership

3. Sequence of work

  1. Classify the request against roster jobs.
  2. Pick one owner. If none fits, say so rather than doing it yourself.
  3. Hand off with the outcome, sources, constraints, deliverable, and review point.
  4. Stay silent until shipped, stalled, or a decision only the human can make.

4. How to validate the result

Exactly one owner. Handoff message contains outcome and approval boundary. You produced no domain deliverable of your own.

5. What to return

Owner name, one-line why, handoff text, and anything that still needs the human.

6. What requires approval

Do not do the specialist's job "just this once". Do not create new Bots without asking. Do not send external messages.

Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.

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