mcp-distribution
Skill9 starsChanged 5 months agoMITView on GitHub
Distribution workflow for ableton-mind: MCPB/DXT bundle, npm, Docker, Smithery, GitHub Actions, setup scripts, README, CHANGELOG and docs.
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when working on dxt/, package.json, Dockerfile, docs/, install scripts, workflows, README.md, CHANGELOG.md or smithery.yaml.
- Distinctive: line 23
Keep README, docs, CHANGELOG, package metadata, DXT manifest and Smithery metadata aligned.
- Distinctive: line 26
Do not add dependencies casually.
- Distinctive: line 30
Run typecheck, lint, tests, build, build:dxt:check and docs:build when the touched surface requires it.
≈ “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
MCP Distribution
Use this skill when working on dxt/, package.json, Dockerfile, docs/, install scripts, workflows, README.md, CHANGELOG.md or smithery.yaml.
Distribution Targets
| Target | Artifact | Audience |
| Codex/Claude Desktop | .mcpb / DXT bundle | one-click users |
| npm | package and CLI bins | developers and MCP clients |
| Docker | image | CI and sandboxed server runs |
| Smithery | listing | MCP discovery |
| GitHub release | bundle and notes | manual installs |
Rules
- Root repo docs are English. Localized pages live under docs/pt.
- Keep README, docs, CHANGELOG, package metadata, DXT manifest and Smithery metadata aligned.
- Bundle checks must verify dist, manifest version, README, LICENSE and embedded knowledge.
- Install docs must cover Remote Script location, Control Surface activation and doctor troubleshooting.
- Do not add dependencies casually; package size and attack surface matter.
Verification
Run typecheck, lint, tests, build, build:dxt:check and docs:build when the touched surface requires it. If Live is needed and unavailable, state exactly what remained unverified.
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-server-developmentSkill
- recipe-authoringSkill
- refactor-maintainabilitySkill
- runtime-release-auditSkill
- 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.
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.