runtime-release-audit
Skill9 starsChanged 5 months agoMITView on GitHub
Audit ableton-mind runtime and release readiness. Use for npm pack dry-runs, DXT/MCPB, Docker, docs build, bin smoke, manifest version sync, release workflows, real Live smoke and final publish gates.
- Commits and pushes
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
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
- Distinctive: line 8
Use this skill to prove that the current checkout can build, package and run without performing irreversible publish actions.
- Very specific: line 12
Verify version sync across package.json, package-lock.json, dxt/manifest.json, server.json and safeskill.manifest.json.
- Distinctive: line 14
Run DXT/MCPB check mode and inspect generated bundle contents when needed.
- Distinctive: line 15
Run npm pack dry-run and compare included files with package expectations.
- Distinctive: line 18
Run mock bridge tests. Run real Live or Push smoke only when the user confirms the environment is ready.
- Distinctive: line 19
Do not run npm publish, gh release create/upload, Docker push or registry submit without explicit confirmation.
- Very specific: line 23
Write _workspace/quality-audit/runtime-release-{N}.md with:
≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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.
Files
Runtime Release Audit
Use this skill to prove that the current checkout can build, package and run without performing irreversible publish actions.
Workflow
- Verify version sync across package.json, package-lock.json, dxt/manifest.json, server.json and safeskill.manifest.json.
- Build and inspect dist and bin entrypoints.
- Run DXT/MCPB check mode and inspect generated bundle contents when needed.
- Run npm pack dry-run and compare included files with package expectations.
- Build docs and Docker image when required by the audit scope.
- Smoke CLI bins after build.
- Run mock bridge tests. Run real Live or Push smoke only when the user confirms the environment is ready.
- Do not run npm publish, gh release create/upload, Docker push or registry submit without explicit confirmation.
Report Format
Write _workspace/quality-audit/runtime-release-{N}.md with:
- Artifact.
- Command.
- Result.
- Evidence.
- Release risk.
- Blocked checks with prerequisites.
In this repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ableton-mind-buildSkill
- ableton-remote-scriptSkill
- cross-boundary-qaSkill
- device-schema-extractionSkill
- mcp-distributionSkill
- mcp-server-developmentSkill
- recipe-authoringSkill
- ableton-mind-buildSkill
- ableton-mind-quality-auditSkill
- ableton-remote-scriptSkill
- command-surface-auditSkill
- cross-boundary-qaSkill
- device-schema-extractionSkill
- local-copilotSkill
- mcp-distributionSkill
- mcp-server-developmentSkill
- recipe-authoringSkill
- refactor-maintainabilitySkill
- security-auditSkill
- test-coverage-expansionSkill
- usability-flow-auditSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
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.