release-publish
Skill0 starsChanged 4 months agoMITView on GitHub
Use when preparing a release, publishing a package, bumping a version, or configuring public repository metadata. Also use when verifying a published package. Do not use for general development or non-release tasks.
- Installs packages
8 other projects use a version of this.
Adopted by
Most recently taken up by
- Alex5350/arsenaltheir own version, first seen Nov 1, 2026
- Shri-Phnx/claude-skillstheir own version, first seen Oct 13, 2026
- bkywksj/knowledge-basetheir own version, first seen Oct 8, 2026
- clawwork-ai/ClawWorktheir own version, first seen Oct 8, 2026
- mono/SkiaSharptheir own version, first seen Oct 8, 2026
- chrysb/alphaclawtheir own version, first seen Oct 8, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- mono/SkiaSharp★ 5.6ksame name
- chrysb/alphaclaw★ 1.5ksame name
- clawwork-ai/ClawWork★ 533same name
- bkywksj/knowledge-base★ 340same name
- hhhyyyy99/prot-skills★ 7same name
- Shri-Phnx/claude-skills★ 2same name
- Alex5350/arsenal★ 0same name
- KcAnom/pi-fairy-tales-chains★ 0same 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.
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
8
Distinctive
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
- Distinctive: line 23
When asked to choose a version, the agent MUST decide it itself.
- Distinctive: line 25
When bumping a version, the agent MUST create the GitHub Release and publish the package in the same update.
- Very specific: line 32
Before publishing, the agent MUST run required prep commands (npm install, npm test, npm pack --dry-run, etc.) and MUST proceed only when …
- Distinctive: line 34
MUST proceed only when ready.
- Distinctive: line 35
If authentication fails during publish, the agent MUST ask the user to complete the publish step.
- Distinctive: line 38
MUST address critical issues, and MUST report results.
- Distinctive: line 42
After publishing, the agent MUST update any locally installed copy to the newly published release and MUST verify the resolved version.
- Very specific: line 63
If installed globally: check npm ls -g <pkg> --depth=0, update via npm i -g <pkg>@latest, then verify with <pkg> --version.
- Very specific: line 66
If not installed globally: skip the global update and verify availability via npx <pkg>@latest --version (or the ecosystem-equivalent).
- Distinctive: line 101
If a repository represents a single tool or product, the agent MUST publish a single package (bundling related scripts).
- Distinctive: line 102
MUST publish a single package (bundling related scripts).
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release and publish workflow
Public repository metadata
- For a public repository, the agent MUST set the GitHub Description, Topics, and Homepage fields.
- A public repository MUST contain:
.github/workflows/ci.yml, issue templates, a PR template,SECURITY.md,CONTRIBUTING.md,CODE_OF_CONDUCT.md, andCHANGELOG.md. - CI MUST run the repository's standard lint, test, and build commands.
Versioning and release flow
- The agent MUST update version metadata when release content changes and MUST keep the package version and the Git tag consistent.
- When asked to choose a version, the agent MUST decide it itself.
- When bumping a version, the agent MUST create the GitHub Release and publish the package in the same update.
- For npm publishing in metyatech-owned packages, the agent MUST
execute
npm publishdirectly. An automation token is configured. - For other packages, the agent MUST ask the user to run
npm publish. - Before publishing, the agent MUST run required prep commands
(
npm install,npm test,npm pack --dry-run, etc.) and MUST proceed only when ready. - If authentication fails during publish, the agent MUST ask the user to complete the publish step.
- The agent MUST run dependency security checks before release, MUST address critical issues, and MUST report results.
Post-publish verification
After publishing, the agent MUST update any locally installed copy to the newly published release and MUST verify the resolved version. The agent MUST NOT report "done" until this verification completes (or the user explicitly declines).
The agent MUST express the verification as explicit acceptance criteria with outcomes (PASS / FAIL / N/A) and evidence:
- AC1 (registry) — verify the published version exists in
the registry (e.g.,
npm view <pkg> version). - AC2 (fresh install) — verify the latest package resolves
and runs (e.g.,
npx <pkg>@latest --version). - AC3 (global update, if applicable) — if the package is
installed globally, update it to the published version and
verify (e.g.,
npm ls -g <pkg> --depth=0,npm i -g <pkg>@latest, then<cmd> --version). If AC3 does not apply, the agent MUST mark it N/A and state the reason explicitly.
For npm CLIs:
- If installed globally: check
npm ls -g <pkg> --depth=0, update vianpm i -g <pkg>@latest, then verify with<pkg> --version. - If not installed globally: skip the global update and verify
availability via
npx <pkg>@latest --version(or the ecosystem-equivalent).
Standard repository topics
The agent MUST assign topics from the standard set below. Every repository MUST have at least one standard topic when applicable. A repository that does not match any standard topic MUST use descriptive topics relevant to its domain.
agent-skill— repository contains aSKILL.md(an installable agent skill).agent-tool— CLI tool or MCP server used by agents (e.g., task-tracker, agents-mcp, compose-agentsmd).agent-rule— rule source or ruleset repository (e.g., agent-rules).unreal-engine— Unreal Engine plugin or sample project.qti— QTI assessment ecosystem tool or library.education— course content, teaching materials, or student-facing platform.docusaurus— Docusaurus plugin or extension.
Additional descriptive topics (language, framework, domain keywords) MAY be added freely alongside standard topics. The agent MUST review and update the standard topic set when the repository landscape changes materially. The agent MUST verify topics are set as part of the new-repository compliance gate.
Published artifact requirements
- The agent MUST populate package metadata (name, description, repository, issues, homepage, engines).
- The agent MUST validate executable entrypoints and required shebangs so installed commands work.
- If a repository represents a single tool or product, the agent MUST publish a single package (bundling related scripts).
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.

