write-skill
Skill4 starsChanged 2 days agoApache-2.0View on GitHub
Create or change an agent skill in Pnyx, either a contributor skill in .agents/skills or a skill shipped with the CLI in skills/. Covers naming, frontmatter, what belongs in a skill versus docs, keeping it short, and registering it. Read before writing any SKILL.md.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- leejianrong/claude-skillstheir own version, first seen Nov 16, 2026
- dzianisv/skillstheir own version, first seen Nov 15, 2026
- serionist/claude-session-restoretheir own version, first seen Nov 8, 2026
- protokol11/skillstheir own version, first seen Nov 8, 2026
- AlomoesDataScience/claude-skillstheir own version, first seen Nov 8, 2026
- maideps/ai-harness-frameworktheir own version, first seen Nov 8, 2026
Used with
Projects with it also use grill, write-docs and 8 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
renatorozasSkillgrill
Adversarial code review. Don't let me ship until the changes pass your scrutiny.
Also in 5 projects that use this
SentrySkillwrite-docs
Create or update documentation pages for the Abacus docs site. Use when adding new documentation, updating existing pages, or ensuring docs stay in sync with code changes. Ensures pages follow Starlight patterns and build correctly.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 4 projects that use this
Google CloudSkilltriage
Gather context on a change or bug and plan the implementation.
Also in 4 projects that use this
SentrySkillreview
Fixture review skill.
Also in 5 projects that use this
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- garrytan/gstack★ 142ksame name
- primer/react★ 3.9ksame name
- iliaal/whetstone★ 36same name
- evist0/okf-matt-skills★ 13same name
- day-ai/gtm-brain★ 9same name
- agentpatterns-ai/skills★ 7same name
- viknesh20-20/claude-code-tool-kit★ 7same name
- hassan-mohiddin/freeflow★ 5same name
- umararshad4/honey-stack★ 5same name
- dzianisv/skills★ 4same name
17 more not listed
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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- audit-testsSkill
- deslopSkill
- follow-conventionsSkill
- review-codeSkill
- write-ci-workflowSkill
- write-front-endSkill
- write-pull-requestSkill
- inscribeSkill
- pnyx-arrange-columnsSkill
- pnyx-cliSkill
- pnyx-firstmate-as-hydraSkill
- pnyx-manage-workersSkill
- pnyx-orchestrateSkill
- pnyx-report-progressSkill
- pnyx-set-upSkill
The file
Files
Write a skill
Skills follow the Agent Skills format: a folder holding a SKILL.md with YAML frontmatter and Markdown instructions. Pnyx has two kinds:
- Contributor skills live in
.agents/skills/<name>/and guide work on this repository. Claude Code finds them through.claude/skills, a committed link to../.agents/skills, so a new one needs no extra link. - Shipped skills live in
skills/<name>/, are installed by Pnyx's setup and read by agents using Pnyx. Their names start withpnyx-except the owner-facinginscribe, and tests read them, sopnpm verifyruns those tests when they change.
Naming and frontmatter
- Name the action, verb first where it reads naturally (
review-code,write-front-end,pnyx-manage-workers), not the tool that runs it or a vague category. Use lowercase letters, numbers and single hyphens. The frontmatternamemust equal the folder name. - Give the frontmatter
nameanddescription. The description, under 1,024 characters, says what the skill does and when to read it, with the words a future agent would match on. Addpathsonly when the skill applies to a fixed set of files, aswrite-front-enddoes forweb/**.
Body
- Write instructions for doing the task: the checks, their order and what to report. Use checklists or numbered steps, with plain sentences.
- Point to the rule's home (
AGENTS.md,docs/, another skill) instead of restating it, so rules have one home and cannot drift apart. A skill holds what an agent needs only while doing that task. - Keep it short. Detail needed only sometimes goes in a
references/file the body links to. - Describe the current project. A skill never asks for session journals, handoff files or a running history of reviews and test results.
- Apply deslop to the text.
Registration
- For a shipped skill, add its name to
src/setup/skill-names.ts, inGLOBAL_SKILLSfor every agent orHYDRA_SKILLSfor Hydra's own, so setup installs it, and to theskills/row of the layout table inAGENTS.md. - For a contributor skill that is a required step, link it where the step is described (
AGENTS.md,CONTRIBUTING.mdordocs/development.md). - Re-check the hard rules before committing:
namematches the folder, the description fits, and the file reads as plain Markdown.
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.

