Publish a portable SKILL.md pack from an MCP server
You ship a versioned skills folder from an MCP server or agent pack with digest metadata so clients discover verified skills without copying ad-hoc prompts.
A publishable directory (SKILL.md per skill plus manifest), a checksum or version stamp clients can verify, and install notes for Cursor and Claude Code.
- 1
Freeze one skill as the reference shape
Pick the smallest real SKILL.md you already trust. The pack format should mirror that file, not an abstract template.
- 2
Add manifest and digest generation
Script or CI step that hashes each SKILL.md and writes manifest.json. Clients skip install when the hash mismatches.
- 3
Test install on a clean clone
Copy or symlink the published pack into a fresh repo and invoke one skill. Metadata is useless if the path wiring is wrong.
The prompt to paste
Design how this MCP server (or internal agent pack) publishes portable skills clients can install without hand-copying markdown. Server or pack context: [repo path, MCP SDK language, existing tools/resources, where skills should live on disk] Skills to publish (1–3 names): [e.g. deploy-checklist, incident-triage] Deliver: ## Folder layout Tree for a publishable bundle e.g. skills-pack/<version>/ with one subdirectory per skill containing SKILL.md and optional references.md. ## manifest.json schema Fields you recommend: name, version, publishedAt, skills[] with slug, title, summary, skillPath, sha256 of SKILL.md (or describe how to compute), minClientVersion if known [verify]. ## SKILL.md template Shared sections both humans and MCP clients need: purpose, when to use, inputs, steps with checks, pitfalls, done checklist. Keep MCP transport details out of the skill body. ## Publish steps Plain-language steps: bump version, compute digests, tag git, attach bundle to release or MCP resource URI pattern [verify against your SDK docs]. ## Client install notes - Cursor: where to copy or symlink under .cursor/skills/ and one AGENTS.md line. - Claude Code: skills root path and config file to update [verify in docs]. - How a client should verify digest before trusting a downloaded skill. ## Example MCP resource or tool description One paragraph a server manifest could expose so clients list available skills with metadata (no fake endpoint URLs — use placeholders). Rules: - Do not claim MCP “Skills over MCP” features unless you mark [verify in SDK release notes]. - No invented analytics or download counts. - Markdown and JSON examples only.
Floating main as the distribution channel defeats verification. Pin version or digest in client config and document how to upgrade.
Sample case written by Hidden Logic Lab. Not affiliated with Cursor or Claude Code.
More in Coding
Get new cases in your inbox
Weekly notes on new use cases and agent workflows. No product pitches.