persona-maker
Skill0 starsChanged 3 months agoMITView on GitHub
Create a compact, reusable expertise profile for a recurring class of subagent work, stored under `.claude/personas/`.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- context-clearingSkill
- local-workerSkill
- model-checkSkill
- retroSkill
- script-makerSkill
- siftSkill
- skill-makerSkill
- spendSkill
- stage1-classifier-hardeningSkill
- telemetry-batterySkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Before creating one, require evidence of reuse:
- Distinctive: line 36
Do not create a new persona for a single slice.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
Persona maker
A persona is an expertise and decision profile for a recurring subagent role — not a character, a biography, or roleplay flavor.
Before creating one, require evidence of reuse:
- name the class of work (e.g. "HTML Developer", "Android Accessibility Tester"), not a one-off task;
- point to at least two prior or clearly upcoming vertical slices that need the same expertise;
- confirm repository authority (
AGENTS.md, target-repo instructions) doesn't already supply it.
Reject the proposal instead of creating it when:
- it is too broad to add expertise beyond "write code" (e.g. "Coder", "Engineer");
- it is too narrow to reuse beyond the current slice (e.g. tied to one file, one color, one ticket);
- it duplicates an existing persona, skill, or governing rule — point to the duplicate instead;
- reuse is asserted but not evidenced;
- the recurring need is actually a deterministic operation, not an expertise profile — route to
script-makerinstead; - the recurring need requires fresh judgment on each invocation rather than a fixed, reusable profile — route to
skill-makerinstead.
A persona file lives at .claude/personas/<kebab-name>.md and contains only:
- Scope: the class of work this persona covers and when it applies.
- Expertise: the domain knowledge and heuristics that materially change execution quality.
- Constraints: hazards or invariants specific to this role.
- Authority boundaries: what this persona does not override — repository authority, review gates, and founder interrupt conditions always win.
Omit biography, personality, tone, motivational language, and anything a well-named identifier already conveys. Target well under 200 words.
Dispatch applies a matching persona by pointing the subagent at its file; it does not restate the persona's content in the dispatch prompt.
Do not create a new persona for a single slice. When no durable persona is justified, write ordinary one-off instructions instead.
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
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.

