agentleFS
joaoajmatosjoaoajmatos/ze/.claude/skills/ze-recruit/SKILL.md

ze-recruit

Skill2 starsChanged 47 days agoUnlicenseView on GitHub

Recruits an agent with the right role and model tier and confirms its brief arrived. Use when the Maestro staffs a floor or a lane.

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 brief to a file in your own scratchpad first.

    line 9
  2. Very specific:

    If it exits 1, the brief did not arrive.

    line 18

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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

Recruit an agent (Maestro only)

Write the brief to a file in your own scratchpad first. The brief must name: the state-file path (journal/state/<terminal id>.md), the scratchpad rule, the pre-review checklist, the commit trailer, the reviewer's name and the throwaway ze_e2e_* DB.

Then run exactly:

scripts/process/recruit.sh "<Name>" <role> <tier> "<Floor>" <brief-file> --note "<Floor> Handoffs"

  • role: maestro, architect, eng, jr, review, qa or docs. scripts/process/roles.toml lists which tiers each role may use. The script refuses a mismatch such as an engineer on Opus.
  • It lints the brief, recruits with ZE_ROLE set, waits for the terminal to be ready, sends the brief with a "reply ready" ping, and retries once with recruit --replace.
  • --connect "<Agent>" (repeatable) wires the new agent to that agent right after the recruit. maestri ask reaches connected agents only, so review requests and verdicts depend on it. Pass the floor's reviewer for every lead and engineer, and the lead for every lane agent. When you recruit the reviewer after the crew, wire each one with maestri connect "<Reviewer>" "<Agent>" --agent.
  • If it exits 1, the brief did not arrive. Read the agent's terminal with maestri check before trying again; do not assume the agent is working.

Preview with --dry-run.

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.