agentleFS
ghvinashvilighvinashvili/specagent/.claude/skills/new-role-type/SKILL.md

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.

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
  1. Very specific:

    Write the contract docs/roles/types/$0.md with the sections Receives, Returns, When it stops, Never.

    line 13
  2. Very specific:

    Add the type to docs/roles/stages.yaml only when the human named the stage it serves.

    line 15

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

New role type

  1. python3 ${CLAUDE_SKILL_DIR}/scripts/new_type.py $0 copies the template to .claude/agents/$0.md with name: $0.
  2. Fill description with the three sentences the template asks for, then model, effort and tools (never Agent).
  3. Give every numbered step of the Working method its rule at the step's end, <!-- check: ... --> in the language of packages/harness/src/harness/gates/steps.py (read:, ran:, wrote:, output:, when:, trust:); once docs/roles/need-to-know.yaml gives the type a steps mode, uv run harness validate names a step without one.
  4. Write the contract docs/roles/types/$0.md with the sections Receives, Returns, When it stops, Never.
  5. uv run harness catalog validates every type against schemas/role-type.schema.json and regenerates docs/generated/role-types.md.
  6. Add the type to docs/roles/stages.yaml only when the human named the stage it serves.

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.