skill-release-publish
AGENTS.md0 starsChanged 4 months agoMITView on GitHub
Source: github:metyatech/agent-rules@HEAD/rules/domains/skill/repository.md
- Installs packages
9 other projects use a version of this.
Adopted by
Most recently taken up by
- metyatech/skill-user-proxyword for word, first seen Jul 22, 2026
- metyatech/skill-pr-review-workflowword for word, first seen Jul 22, 2026
- metyatech/skill-human-ai-system-builderword for word, first seen Jul 22, 2026
- metyatech/skill-code-quality-setupword for word, first seen Jul 22, 2026
- metyatech/skill-cli-designword for word, first seen Jul 22, 2026
- metyatech/skill-post-deployword for word, first seen Jul 2, 2026
Other versions9 projects use a version of this.
Word for word · 9
- metyatech/skill-sub-agent-dispatch★ 1100% same
- metyatech/skill-cli-design★ 0100% same
- metyatech/skill-code-quality-setup★ 0100% same
- metyatech/skill-guided-doc-writing★ 0100% same
- metyatech/skill-guided-gui-design★ 0100% same
- metyatech/skill-human-ai-system-builder★ 0100% same
- metyatech/skill-post-deploy★ 0100% same
- metyatech/skill-pr-review-workflow★ 0100% same
- metyatech/skill-user-proxy★ 0100% same
Edited · 0
None found.
Wrote their own version · 0
None found.
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.
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 32,671 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- release-publishSkill
The file
We split this AGENTS.md into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 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.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 6
If compose-agentsmd is not available, run it via npx compose-agentsmd.
- Very specific: line 8
If you find an existing clone of the rules source repo elsewhere, do not assume it is the correct rules workspace.
- Distinctive: line 10
Do not edit AGENTS.md directly.
- Distinctive: line 12
Before applying any rule updates, present the planned changes first with an ANSI-colored diff-style preview, ask for explicit approval, …
≈ “Common” is an estimate: at least 1 in 5 of the 41,581 AGENTS.md 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
<!-- markdownlint-disable MD025 -->Tool Rules (compose-agentsmd)
- Session gate: before starting substantive work for each externally supplied human/operator instruction, run
compose-agentsmdonce from the project root. AGENTS.md contains the rules you operate under; stale rules cause rule violations. Do not rerun this gate within the same instruction after tool results, retries, generated continuations, or resumed execution. If you discover you skipped this step mid-session, stop, run it immediately, re-read the diff, and adjust your behavior before continuing. compose-agentsmdintentionally regeneratesAGENTS.md; any resultingAGENTS.mddiff is expected and must not be treated as an unexpected external change.- If
compose-agentsmdis not available, run it vianpx compose-agentsmd. Ifnpxis unavailable or cannot fetch the package, install it via npm with an environment-appropriate method such asnpm install -g compose-agentsmdwhen global installs are permitted, or a user-local npm prefix when global installs are not permitted. - To update shared/global rules, use
compose-agentsmd edit-rulesto locate the writable rules workspace, make changes only in that workspace, then runcompose-agentsmd apply-rules(do not manually clone or edit the rules source repo outside this workflow). - If you find an existing clone of the rules source repo elsewhere, do not assume it is the correct rules workspace; always treat
compose-agentsmd edit-rulesoutput as the source of truth. compose-agentsmd apply-rulespushes each GitHub source workspace when its workspace is clean, then regenerates instruction files with refreshed rules.- Do not edit
AGENTS.mddirectly; update the source rules and regenerate. tools/tool-rules.mdis the shared rule source for all repositories that use compose-agentsmd.- Before applying any rule updates, present the planned changes first with an ANSI-colored diff-style preview, ask for explicit approval, then make the edits.
- These tool rules live in tools/tool-rules.md in the compose-agentsmd repository; do not duplicate them in other rule modules.
Source: github:metyatech/agent-rules@HEAD/rules/domains/skill/repository.md
Skill Repository Rules
- A skill MUST follow the Agent Skills open standard.
SKILL.mdfrontmatter MUST contain onlynameanddescription.nameMUST be lowercase alphanumeric with hyphens, at most 64 characters.descriptionMUST explain trigger conditions.SKILL.mdMUST be platform-agnostic and use intent-level wording.- Platform-specific examples MUST live in
README.md. SKILL.mdandREADME.mdSHOULD be in English.- Skill instructions MUST be concise and action-oriented.
- A skill MUST NOT duplicate AGENTS.md global rules.
- Each skill MUST live in its own
metyatech/skill-<name>repository withSKILL.mdat the root. - Each skill repository MUST include a LICENSE file.
- Skill repositories SHOULD use the MIT license unless the user specifies otherwise.
- Skill repositories MUST be public unless the user explicitly asks for a private skill.
- The GitHub repository is the canonical source of truth for a skill.
- The agent MUST NOT edit installed copies under
~/.agents/skills/<name>.
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.

