Design SDK
Design, build, and publish Workshop SDKs with sdkcraft — interview and research the software, generate sdkcraft.yaml with hooks and spread smoke tests, iterate via sdkcraft try plus workshop refresh, write the README, then onboard the SDK repo with version branches, CI workflows, and renovate. Use when creating or maintaining a publisher-side (Store) SDK from its own repository — "design an SDK for X", "create an sdkcraft.yaml", "set up renovate and CI for my SDK repo".
Install
/plugin marketplace add canonical/use-workshop-skillThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add canonical/use-workshop-skill --skill design-sdkgit clone --depth 1 https://github.com/canonical/use-workshop-skill.git /tmp/use-workshop-skill
mkdir -p ~/.claude/skills
cp -r /tmp/use-workshop-skill/.github/skills/design-sdk ~/.claude/skills/design-sdkPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
<essential_principles>
Five rules that always apply to designing SDKs. Every workflow assumes them.
1. **Interview first; design from named patterns.** Before writing any file,
settle: what software — and whether it is a standalone application or a
library/environment other SDKs consume — how upstream distributes it,
what must persist,
whether it serves a network service, hardware needs, bases and
architectures, version scheme, renovate datasource, track count. Every
proposed construct maps to a pattern in
`references/reference-sdk-patterns.md` or
`references/design-best-practices.md` — never an invented field or flag.
A pattern whose catalog entry is marked evolving (hermes — the Python
mechanism SDKcraft's maintainers call unsettled) is recommended WITH that
caveat, as the current exemplar to prove in the try loop, never as
settled convention. Every question carries a recommendation ("Options:
A / B — Recommendation: A, because <evidence>"), batched into one
message.
2. **Copy, don't synthesize, YAML.** Shapes come from `templates/` here, the
reference SDKs, and `../use-workshop/templates/` — never from memory.
Schema facts come from `references/sdkcraft-definition.md`; if a key is
not there, it does not exist. `stage-packages`/`stage-snaps` are
hard-rejected — apt work belongs in `setup-base`. There is no `apps:` or
`services:` key — daemons ship as a dump part plus a systemd user unit.Details
- Skill name
design-sdk- Repository
- canonical/use-workshop-skill
- Path
.github/skills/design-sdk/SKILL.md- License
- GPL-3.0
- Repo updated
- 18 November 2026
FAQ
What does the Design SDK skill do?
Design, build, and publish Workshop SDKs with sdkcraft — interview and research the software, generate sdkcraft.yaml with hooks and spread smoke tests, iterate via sdkcraft try plus workshop refresh, write the README, then onboard the SDK repo with version branches, CI workflows, and renovate. Use when creating or maintaining a publisher-side (Store) SDK from its own repository — "design an SDK for X", "create an sdkcraft.yaml", "set up renovate and CI for my SDK repo".
How do I install the Design SDK skill?
Claude Code plugin: /plugin marketplace add canonical/use-workshop-skill. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Design SDK popular?
It lives in canonical/use-workshop-skill, which has 9 GitHub stars and 2 forks.
Related skills
Onboard Workshop
9canonical/use-workshop-skill
Analyze an arbitrary repository and bootstrap a tailored Workshop definition from its existing build, test, and debug toolchain — feasibility verdict first, then propose, generate, launch, and verify. Use when a repo has no workshop definition yet and the user wants one derived from how the repo already builds and tests — "set up a workshop for this repo", "workshop-ify this project", "can this repo run in Workshop?".
Use Workshop
9canonical/use-workshop-skill
Operate the Workshop CLI fluently — launch and refresh workshops, run commands inside them, manage interfaces, debug failed changes, and orchestrate parallel environments via git worktrees. Use when the user mentions workshop, .workshop.yaml, an LXD-backed dev environment, or wants to plan/edit a workshop definition.
Dmk Intent Vocabulary
9LedgerHQ/agent-skills
Map developer intent and natural language to the correct Ledger Device Management Kit (DMK) components, operations, and API methods. Use when a developer's request is phrased informally, incompletely, or in terms of outcomes rather than API methods, when the intent is ambiguous and needs mapping to a specific DMK component or operation, or when a developer asks 'how do I...', 'what's the difference between...', or describes a symptom rather than an API.
Code Acceptance
9leyuan0602-glitch/cc-claude-codex
Independent code acceptance skill. Use when verifying completed work before committing, merging, or claiming done. Performs test-based verification only: unit tests, E2E tests, and integration tests. Only cares whether outcomes match expectations, not code implementation. Works standalone or as cc-claude-codex Phase 3.
Ledger Dmk Implementation
9LedgerHQ/agent-skills
Execute Ledger Device Management Kit (DMK) signing operations safely: initialize the SDK, establish a device session, verify device state, open the correct chain app, perform signing or device management operations, and return the result. Use when a developer needs to implement a signing operation (transaction, message, typed data), derive or retrieve an address from a Ledger device, send any command to a Ledger device, or perform device management operations such as genuine check, app install, or app uninstall.
Cc Claude Codex
9leyuan0602-glitch/cc-claude-codex
Development skill where Claude Code acts as supervisor and Codex acts as executor. Auto-trigger for implementation, debugging, refactoring, testing, and other dev tasks.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.