agentleFS
Sign inStart free
alimohammadiamirhosseinalimohammadiamirhossein/deputy/SKILL.md

deputy

Skill2 starsChanged 21 days agoMITView on GitHub

Playbook for working with Deputy, a cheaper helper model (DeepSeek V4.1 Flash) exposed as MCP tools (consult, review, investigate, delegate). Use whenever the Deputy tools are available, to get second opinions before decisions, independent bug reviews after changes, and wide code searches, while you keep all judgment.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. toverux/cantrips★ 3same name
    2. tonychen15/deputy★ 0same 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

8 rules. About 0 are common, 1 is distinctive, and 7 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.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If status shows the wrong workspace, pass project_dir (the project's absolute path) to the tools.

    line 16
  2. Very specific:

    Call status once to see the mode.

    line 22
  3. Very specific:

    Consult: when you are unsure between approaches.

    line 35
  4. Very specific:

    Adjudicate: every finding: accept, dismiss with a reason, or defer.

    line 45
  5. Very specific:

    Never let Deputy's agreement stand in for evidence: it shares your framing.

    line 68
  6. Very specific:

    Do not run debates back and forth with Deputy.

    line 69
  7. Distinctive:

    Never put secrets in any argument: everything goes to the model provider.

    line 70
  8. Very specific:

    If the user says "do it yourself", do not use Deputy for that task.

    line 71

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

Working with Deputy

You are the lead. Deputy is a cheaper, weaker model that you can call for extra perspectives and extra eyes. Use it to be more accurate, never to skip your own judgment.

Using the Claude Code plugin? You already have this as /deputy:consult, /deputy:review, /deputy:investigate, /deputy:delegate and /deputy:ds. Without the plugin, copy this file to ~/.claude/skills/deputy/SKILL.md. In Cursor or Codex, deputy setup cursor or deputy setup codex installs an equivalent rule or skill.

If status shows the wrong workspace, pass project_dir (the project's absolute path) to the tools. When the user asks what Deputy saved, call stats and report its numbers as rough estimates.

The mode decides who writes code

Call status once to see the mode.

ModeWho writes codeDeputy is used for
accuracy (default)You, alwaysconsult when unsure between approaches, review for risky or large changes, investigate for wide searches. delegate only if the user asks
leanYou for small, tricky or risky changes; Deputy for larger well-specified workinvestigate instead of reading many files; delegate work big enough to pay off; review only risky or large changes
balancedYou, for anything with logic or riskAlso delegate for low-risk mechanical work (boilerplate, renames, formatting, test scaffolding)
partnerDeputy, for every low-level job; you for design and judgmentinvestigate and delegate for all legwork, consult for ideas; read every diff and check every idea
savingsDeputy, for well-specified workdelegate most coding; you plan, review and verify

The accuracy loop

  1. Understand the task yourself. Read the code that matters.
  2. Consult when you are unsure between approaches. Write your own conclusion first and pass it as my_view (Deputy does not see it). Ask with your plan and 2-3 lenses, for example "simplest approach", "edge cases and failure modes", "what could break existing behavior".
  3. Decide yourself. Change your plan only if an idea survives your own check against the code, not because Deputy disagrees.
  4. Implement the change yourself.
  5. Review a risky or large change before you say it is done: tricky logic, security or untrusted input, data that can be lost, concurrency, money, or many files. Call review with focus = what the change should do. It reviews your uncommitted git diff with independent reviewers.
  6. Adjudicate every finding: accept, dismiss with a reason, or defer. Run a finding's REPRO when it has one. Findings raised by more than one lens are more likely real. Fix what you confirm; tell the user briefly what you dismissed and why.

Skip steps 2 and 5 for routine changes whose tests pass. Each call makes the user wait, often a minute or more.

Using each tool well

  • consult: a sharp question with your current plan and context (constraints, what you ruled out). Lenses run in parallel and do not see each other.
  • review: by default reviews uncommitted changes against HEAD. Use base for a branch (for example "main"), paths to narrow it, and lenses such as "security and input handling" or "concurrency" when relevant.
  • investigate: for questions that need wide reading. Treat answers as leads and read the cited lines yourself before acting.
  • delegate: a full brief (goal, scope, constraints, a verify command) in task, facts in context. Then read every changed file, check git diff and run the tests. After two poor results, stop delegating.

Rules

  • Deputy's output is never proof. Verify against the code before relying on it.
  • Never let Deputy's agreement stand in for evidence: it shares your framing.
  • Do not run debates back and forth with Deputy; take its independent input once, then decide.
  • Never put secrets in any argument: everything goes to the model provider.
  • If the user says "do it yourself", do not use Deputy for that task.

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