new-role-type
Skill7 starsChanged 16 days agoApache-2.0View on GitHub
Create a role type from templates/role-type.md, validate it and regenerate the catalog. Use only when a human asks for a new type.
In this repository29 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- docs/llms.txtllms.txt
- adrSkill
- agent-evalSkill
- agent-security-hardeningSkill
- agent-self-evaluationSkill
- checkpointSkill
- commit-styleSkill
- conventional-commit-reviewSkill
- councilSkill
- cpp-coding-standardsSkill
- cpp-testingSkill
- doc-gardeningSkill
- docs-governanceSkill
- escalateSkill
- eval-harnessSkill
- handoffSkill
- intakeSkill
- loop-tickSkill
- postgres-patternsSkill
- python-patternsSkill
- python-testingSkill
- releaseSkill
- resume-stageSkill
- running-specagent-pipelinesSkill
- run-stageSkill
- specSkill
- wiki-ingestSkill
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
- Very specific: line 13
Write the contract docs/roles/types/$0.md with the sections Receives, Returns, When it stops, Never.
- Very specific: line 15
Add the type to docs/roles/stages.yaml only when the human named the stage it serves.
≈ “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
New role type
python3 ${CLAUDE_SKILL_DIR}/scripts/new_type.py $0copies the template to.claude/agents/$0.mdwithname: $0.- Fill
descriptionwith the three sentences the template asks for, thenmodel,effortandtools(neverAgent). - Give every numbered step of the Working method its rule at the step's end,
<!-- check: ... -->in the language ofpackages/harness/src/harness/gates/steps.py(read:, ran:, wrote:, output:, when:, trust:); oncedocs/roles/need-to-know.yamlgives the type astepsmode,uv run harness validatenames a step without one. - Write the contract
docs/roles/types/$0.mdwith the sections Receives, Returns, When it stops, Never. uv run harness catalogvalidates every type againstschemas/role-type.schema.jsonand regeneratesdocs/generated/role-types.md.- Add the type to
docs/roles/stages.yamlonly when the human named the stage it serves.
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.

