agentleFS
zdnemzzdnemz/claude-team/.claude/skills/manage-agents/SKILL.md

manage-agents

Skill1 starsChanged 5 months agoMITView on GitHub

Create, modify, or remove agents, skills, hooks, and MCP servers for this project. Use when the team needs a new specialty or automation, or to retire ones no longer needed.

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. gokite-ai/passport-skills★ 2same 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 4

    Very specific

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

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

    Check .claude/agents/ — don't duplicate an existing specialty.

    line 11
  2. Very specific:

    Delete .claude/agents/<role>.md + its registry row.

    line 19
  3. Very specific:

    Keep hooks fast (<2s) and fail-open (exit 0).

    line 31
  4. Very specific:

    Add to .mcp.json: {"mcpServers": {"<name>": {"command": "...", "args": ["..."]}}}.

    line 35

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

Manage Agents & Tooling

Model policy + roster: .claude/system/registry.md. Update its table on EVERY create/remove, and progress_log the change.

Create an agent

  1. Check .claude/agents/ — don't duplicate an existing specialty; sharpen the existing one instead.
  2. Copy .claude/system/templates/agent-template.md → .claude/agents/<role-slug>.md. Fill: name, description ("Use for …" so auto-selection works), model per registry policy, 5–8 specialty bullets that would actually change how the work is done.
  3. New agent TYPES register at the next session start. Until then, spawn general-purpose with the file body prepended + the model param — same file, either path.

Modify an agent

Edit .claude/agents/<role>.md directly — description, model tier (justify against registry policy), specialty bullets. Typical at init: retuning a generic role to the project's domain (e.g. backend-engineer → "REST + Postgres" bullets swapped for "gRPC + embedded sqlite"). Sync the registry row. Named-type changes load next session; immediate need → general-purpose + updated file body.

Remove an agent

Delete .claude/agents/<role>.md + its registry row. Never remove a role with in-flight tasks — reassign first. If the user created it manually, ask before deleting.

Create a skill

.claude/skills/<name>/SKILL.md — frontmatter (name, description with a "Use when …" trigger), body = the procedure. Worth creating when a procedure has ≥3 steps and will run ≥2 times. Loads next session; follow the file directly until then.

Hooks

Scripts live in .claude/hooks/; register in .claude/settings.json under hooks.<Event> (SessionStart, UserPromptSubmit, PreToolUse, PostToolUse, Stop):

{"hooks": [{"type": "command", "command": "bash \"$CLAUDE_PROJECT_DIR/.claude/hooks/<script>.sh\""}]}

Keep hooks fast (<2s) and fail-open (exit 0). Changes load at next session start. NEVER remove session-start.sh or on-prompt.mjs — they are the system's lifelines.

MCP servers

Add to .mcp.json: {"mcpServers": {"<name>": {"command": "...", "args": ["..."]}}}. Prefer stdio + zero/low-dependency (see memory-server.mjs as the pattern). Loads next session. NEVER remove the memory server — the system is amnesiac without it.

Removal safety (all artifact types)

State why, progress_log it, and if the artifact was user-added rather than system-created, ask the user first.

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.