/ Annuaire / Playground / craftdesk
● Communauté mensfeld ⚡ Instantané

craftdesk

par 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.

Pourquoi l'utiliser

Fonctionnalités clés

Démo en direct

Aperçu en pratique

craftdesk-skill.replay ▶ prêt
0/0

Installation

Dépôt de l’auteur · Documentation officielle des Skills Claude

Cas d'usage

Usages concrets : craftdesk

Manage a team-standard skill set across multiple developers

👤 Platform teams standardizing AI tooling ⏱ ~30 min intermediate

Quand l'utiliser : Team members each pick different skills; you want everyone on the same set.

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

Résultat : A reproducible skill environment like a package.json for AI.

Pièges
  • Committing secrets from embedded skills — Embedded skills shouldn't carry creds — keep those in env
Combiner avec : filesystem · github

Sync skills across Claude Code, Cursor, and Windsurf

👤 Developers using multiple agents ⏱ ~10 min beginner

Quand l'utiliser : You install a skill in Claude Code and want it in Cursor too.

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

Résultat : Consistent tooling no matter which agent you open.

Publish an internal craft to a private registry

👤 Teams with proprietary skills ⏱ ~20 min intermediate

Quand l'utiliser : You built a skill for internal processes and want it installable by craftdesk add.

Déroulement
  1. Publish
    craftdesk publish — push this craft to our registry.✓ Copié
    → Published with version

Résultat : An internal library of crafts versioned like any code dependency.

Combiner avec : github

Combinaisons

Associez-le à d'autres MCPs pour un effet X10

craftdesk-skill + github

Install crafts directly from GitHub URLs

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

Embedded skills under ./skills/ get picked up automatically

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

Outils

Ce que ce MCP expose

OutilEntréesQuand appelerCoût
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

Coût et limites

Coût d'exécution

Quota d'API
None
Tokens par appel
Minimal — CraftDesk is CLI-driven
Monétaire
Free
Astuce
Use the lockfile — avoids re-resolving on every install

Sécurité

Permissions, secrets, portée

Stockage des identifiants : Registry tokens in env if publishing privately
Sortie de données : Only to git hosts you install from + any configured registry

Dépannage

Erreurs courantes et correctifs

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 autres

AlternativeQuand l'utiliserCompromis
Manual git clone into skills dirSingle machine, no teamNo pinning, no sync
gsd-skill-creatorYou want skills authored for you, not managedDifferent problem

Plus

Ressources

📖 Lire le README officiel sur GitHub

🐙 Voir les issues ouvertes

🔍 Parcourir les 400+ serveurs MCP et Skills