agentleFS
Sign inStart free
RandyRawgustRandyRawgust/ai-knowledge-base-template/.claude/skills/specialist-creator/SKILL.md

specialist-creator

Skill1 starsChanged 6 months agoMITView on GitHub

Scaffold a new specialist agent definition under 03 - Skills & Rules/Agents/Specialists/ with correct frontmatter. Use when adding a new agent role under one of the 5 dept heads.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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:

    Update parent dept-head's delegates_to: list to include the new specialist.

    line 43
  2. Very specific:

    Don't promote to .claude/agents/ - per Andy's decision, specialists stay as dept-head delegates only

    line 46
  3. Distinctive:

    Don't duplicate existing specialists - check the list first

    line 47
  4. Distinctive:

    Don't skip the parent assignment - orphan specialists are an audit finding

    line 48

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

Specialist Creator

When to use

Triggers: add a specialist, new specialist, create a sub-agent, extend Builder/Writer/Archivist/Auditor.

Load

  • Existing specialists as reference: 03 - Skills & Rules/Agents/Specialists/
  • Parent dept-head's spec (Builder.md / Writer.md / Archivist.md / Auditor.md)

Confirm

  1. Specialist slug (lowercase-hyphens)
  2. One-line tagline (used in tooltips)
  3. Parent dept head (Builder / Writer / Archivist / Auditor / Orchestrator)
  4. Rules it uses (uses_rules: array)
  5. Skills it uses (uses_skills: array - subset of [docx, pdf, pptx, xlsx])
  6. Model (sonnet default; opus for heavy reasoning)

Create

03 - Skills & Rules/Agents/Specialists/<slug>.md with frontmatter:

---
type: agent
role: specialist
parent: <dept-head>
tagline: "<one line>"
status: idle
created: <date>
uses_rules: [<list>]
uses_skills: [<list or empty>]
model: <sonnet or opus>
tags: [agent, specialist]
---

Body: role description, when invoked, inputs, process steps, outputs, don'ts.

After creating

Update parent dept-head's delegates_to: list to include the new specialist.

Don't

  • Don't promote to .claude/agents/ - per Andy's decision, specialists stay as dept-head delegates only
  • Don't duplicate existing specialists - check the list first
  • Don't skip the parent assignment - orphan specialists are an audit finding

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