agentleFS
Sign inStart free
fagemxfagemx/prismstack/.claude/skills/skill-dev/SKILL.md

skill-dev

Skill2 starsChanged 8 months agoMITView on GitHub

Develop or modify a Prismstack product skill. Ensures changes follow skill-craft-guide. Trigger: "edit skill X", "improve domain-plan", "add feature to skill-check", "skill-dev" Do NOT use when: editing a user's domain stack skills (that's the product /skill-edit)

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 3

    1. LuisSambrano/antigravity-config★ 8same name
    2. parsoFish/skills★ 1same name
    3. yktsnet/dotfiles-public★ 1same 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

Show its rules and text

We split this skill into the rules it gives an agent

17 rules. About 0 are common, 14 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈14

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If not provided, ask:

    line 19
  2. Very specific:

    Read the current SKILL.md for the target skill fully before making any change.

    line 23
  3. Distinctive:

    If the change spans multiple areas, read all relevant files.

    line 37
  4. Distinctive:

    Read before edit: Always use Read tool on the file before using Edit tool.

    line 43
  5. Distinctive:

    No scope creep: If you notice other issues while editing, note them but do not fix them now.

    line 45
  6. Distinctive:

    Use the Edit tool (not Write) for modifications.

    line 47
  7. Distinctive:

    After the edit, run a quick quality check on the modified skill:

    line 51
  8. Very specific:

    Read skills/shared/methodology/quality-standards.md for the 15D rubric

    line 53
  9. Distinctive:

    All tests must pass. If any fail:

    line 70
  10. Distinctive:

    Read the failure output

    line 71
  11. Distinctive:

    If caused by your change, fix it and re-run

    line 73
  12. Distinctive:

    If pre-existing, note it but do not block on it

    line 74
  13. Distinctive:

    If all checks pass, stage and commit:

    line 78
  14. Distinctive:

    Use conventional commit prefixes:

    line 85
  15. Very specific:

    Line count guard: After editing, check wc -l on the SKILL.md.

    line 93
  16. Distinctive:

    Do not rewrite the whole skill: when changing one section.

    line 94
  17. Distinctive:

    Test after every change: Never commit without running install tests.

    line 96

≈ “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
<!-- Internal maintenance skill — edit this file directly -->

/skill-dev: Develop Prismstack Product Skills

You are a Prismstack skill developer. You modify the 10 product skills with discipline, ensuring every change follows the methodology.

Phase 0: Scope the Change

Parse $ARGUMENTS for the target skill and change description.

If not provided, ask:

  1. Which skill? (one of the 10 product skills in skills/*/SKILL.md)
  2. What change? (add feature, fix issue, refactor section, etc.)

Read the current SKILL.md for the target skill fully before making any change.

Phase 1: Load Relevant Methodology

Based on the type of change, read the appropriate methodology file:

Change TypeRead This
Structure / sectionsskills/shared/methodology/skill-craft-guide.md
Scoring / rubricskills/shared/methodology/quality-standards.md
Artifact flow / wiringskills/shared/methodology/system-wiring-guide.md
Fix loop / triageskills/shared/methodology/fix-loop-guide.md
Context / accumulationskills/shared/methodology/context-accumulation-guide.md

If the change spans multiple areas, read all relevant files. Do not guess at methodology — read it.

Phase 2: Make the Change

Rules for editing:

  • Minimal and surgical. Change only what is needed. Do not rewrite surrounding sections.
  • Read before edit. Always use Read tool on the file before using Edit tool. Never edit blind.
  • Preserve voice. Match the existing tone and formatting of the skill.
  • No scope creep. If you notice other issues while editing, note them but do not fix them now. One change per /skill-dev invocation.

Use the Edit tool (not Write) for modifications. Write is only for new files.

Phase 3: Self-Check (Quick 15D)

After the edit, run a quick quality check on the modified skill:

  1. Read skills/shared/methodology/quality-standards.md for the 15D rubric
  2. Score the modified skill on all 15 dimensions (1-5 scale)
  3. Compare to a rough pre-edit baseline (your reading from Phase 0)

Answer these questions:

  • Did the target dimension improve? (If not, the change missed its goal.)
  • Did any other dimension drop? (If so, the change introduced a regression.)
  • Is the overall score at least 3.5 average? (If not, flag for additional work.)

Report the before/after comparison as a compact table.

Phase 4: Run Install Test

bash test/install-test.sh

All tests must pass. If any fail:

  1. Read the failure output
  2. Identify whether the failure is caused by your change or pre-existing
  3. If caused by your change, fix it and re-run
  4. If pre-existing, note it but do not block on it

Phase 5: Commit

If all checks pass, stage and commit:

git add skills/<skill-name>/SKILL.md
git commit -m "fix(skill-name): <concise description of change>"

Use conventional commit prefixes:

  • feat(skill-name): — new capability added to the skill
  • fix(skill-name): — bug or issue fixed
  • refactor(skill-name): — restructured without behavior change
  • docs(skill-name): — documentation or comment changes only

Gotchas

  • Line count guard: After editing, check wc -l on the SKILL.md. Product skills should stay under 200 lines. If over, consider splitting into references/ files.
  • Do not rewrite the whole skill when changing one section. Large diffs are hard to review and easy to break.
  • Shared methodology changes require a different workflow. If the methodology itself is wrong, edit the methodology file directly — do not hack around it in a skill.
  • Test after every change. Never commit without running install tests.

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