/ 目录 / 演练场 / craftdesk
● 社区 mensfeld ⚡ 即开即用

craftdesk

作者 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.

为什么要用

核心特性

实时演示

实际使用效果

craftdesk-skill.replay ▶ 就绪
0/0

安装

作者仓库 · Claude Skills 官方文档

使用场景

实战用法: craftdesk

Manage a team-standard skill set across multiple developers

👤 Platform teams standardizing AI tooling ⏱ ~30 min intermediate

何时使用: Team members each pick different skills; you want everyone on the same set.

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

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

注意事项
  • Committing secrets from embedded skills — Embedded skills shouldn't carry creds — keep those in env
搭配使用: filesystem · github

Sync skills across Claude Code, Cursor, and Windsurf

👤 Developers using multiple agents ⏱ ~10 min beginner

何时使用: You install a skill in Claude Code and want it in Cursor too.

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

结果: Consistent tooling no matter which agent you open.

Publish an internal craft to a private registry

👤 Teams with proprietary skills ⏱ ~20 min intermediate

何时使用: You built a skill for internal processes and want it installable by craftdesk add.

步骤
  1. Publish
    craftdesk publish — push this craft to our registry.✓ 已复制
    → Published with version

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

搭配使用: github

组合

与其他 MCP 搭配,撬动十倍杠杆

craftdesk-skill + github

Install crafts directly from GitHub URLs

craftdesk add https://github.com/org/skill✓ 已复制
craftdesk-skill + filesystem

Embedded skills under ./skills/ get picked up automatically

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

工具

此 MCP 暴露的能力

工具输入参数何时调用成本
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

成本与限制

运行它的成本

API 配额
None
每次调用 Token 数
Minimal — CraftDesk is CLI-driven
费用
Free
提示
Use the lockfile — avoids re-resolving on every install

安全

权限、密钥、影响范围

凭据存储: Registry tokens in env if publishing privately
数据出站: Only to git hosts you install from + any configured registry

故障排查

常见错误与修复

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

替代方案

craftdesk 对比其他方案

替代方案何时用它替代权衡
Manual git clone into skills dirSingle machine, no teamNo pinning, no sync
gsd-skill-creatorYou want skills authored for you, not managedDifferent problem

更多

资源

📖 阅读 GitHub 上的官方 README

🐙 查看未解决的 issue

🔍 浏览全部 400+ MCP 服务器和 Skills