/ Directory / Playground / craftdesk
● Community mensfeld ⚡ Instant

craftdesk

by mensfeld · mensfeld/craftdesk

npm for Claude Code skills — install, pin, lockfile, sync across Claude Code / Cursor / Windsurf / Continue, with checksum verification and collections.

CraftDesk is a CLI package manager for AI capabilities (skills, agents, commands, hooks, plugins). Install from GitHub URLs or git repos, with monorepo subdirectory support and recursive dependency resolution. Produces a craftdesk.json + lockfile for reproducible environments. Syncs installed crafts across Claude Code, Cursor, Windsurf, and Continue.dev. Supports embedded/local skills so project-specific ones can live in your repo.

Why use it

Key features

Live Demo

What it looks like in practice

craftdesk-skill.replay ▶ ready
0/0

Install

Author repository · Claude Skills documentation

Use Cases

Real-world ways to use craftdesk

Manage a team-standard skill set across multiple developers

👤 Platform teams standardizing AI tooling ⏱ ~30 min intermediate

When to use: Team members each pick different skills; you want everyone on the same set.

Flow
  1. Init a project manifest
    craftdesk init — set up craftdesk.json for this repo.✓ Copied
    → craftdesk.json created
  2. Add skills
    craftdesk add planning-with-files agent-skill-tdd swing-skills — pin versions.✓ Copied
    → Manifest updated, lockfile written
  3. Team installs
    Teammate runs craftdesk install on clone.✓ Copied
    → Same skills and versions land on their machine

Outcome: A reproducible skill environment like a package.json for AI.

Pitfalls
  • Committing secrets from embedded skills — Embedded skills shouldn't carry creds — keep those in env
Combine with: filesystem · github

Sync skills across Claude Code, Cursor, and Windsurf

👤 Developers using multiple agents ⏱ ~10 min beginner

When to use: You install a skill in Claude Code and want it in Cursor too.

Flow
  1. Sync
    craftdesk sync — make all installed crafts available to all my agents.✓ Copied
    → Per-agent install paths populated
  2. Verify
    craftdesk verify — any drift?✓ Copied
    → Green across agents

Outcome: Consistent tooling no matter which agent you open.

Publish an internal craft to a private registry

👤 Teams with proprietary skills ⏱ ~20 min intermediate

When to use: You built a skill for internal processes and want it installable by craftdesk add.

Flow
  1. Publish
    craftdesk publish — push this craft to our registry.✓ Copied
    → Published with version

Outcome: An internal library of crafts versioned like any code dependency.

Combine with: github

Combinations

Pair with other MCPs for X10 leverage

craftdesk-skill + github

Install crafts directly from GitHub URLs

craftdesk add https://github.com/org/skill✓ Copied
craftdesk-skill + filesystem

Embedded skills under ./skills/ get picked up automatically

Create an embedded skill at ./skills/custom-review and run craftdesk sync.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
craftdesk init none Start of a new project 0
craftdesk install (reads craftdesk.json + lockfile) After clone / pull 0
craftdesk add name or URL Add a dependency 0
craftdesk list none Inventory check 0
craftdesk sync none After install or update 0
craftdesk publish craft path Internal release 0
craftdesk verify none Sanity check 0

Cost & Limits

What this costs to run

API quota
None
Tokens per call
Minimal — CraftDesk is CLI-driven
Monetary
Free
Tip
Use the lockfile — avoids re-resolving on every install

Security

Permissions, secrets, blast radius

Credential storage: Registry tokens in env if publishing privately
Data egress: Only to git hosts you install from + any configured registry

Troubleshooting

Common errors and fixes

Install fails with checksum mismatch

Upstream changed; pin to a commit sha or reconcile the lockfile deliberately

craftdesk sync misses one agent

Confirm the agent path exists and is writable; see craftdesk config

Alternatives

craftdesk vs others

AlternativeWhen to use it insteadTradeoff
Manual git clone into skills dirSingle machine, no teamNo pinning, no sync
gsd-skill-creatorYou want skills authored for you, not managedDifferent problem

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills

Continue exploring

Related tools and workflows

Choose another guide for your workflow, or explore a collection.

Browse all topic collections → · See 29 new official additions →