Onboard Workshop

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?".

9 stars 2 forksTesting & QA Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add canonical/use-workshop-skill

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add canonical/use-workshop-skill --skill onboard-workshop
Manual install
git 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/onboard-workshop ~/.claude/skills/onboard-workshop

Personal 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 onboarding. Every workflow assumes them.

1. **Honesty gate.** The feasibility verdict (FULL / PARTIAL / INFEASIBLE)
   is delivered BEFORE any file is generated. Never silently drop a detected
   need to make the proposal look complete; every gap is named with a reason
   and workaround (or "none"). PARTIAL requires explicit user acknowledgment;
   INFEASIBLE ends the run with a report and docs pointers — a subpar
   workshop is worse than no workshop.

2. **Stay inside the envelope, and don't state guesses as facts.** Every
   proposed construct must map to a real definition key, interface, or SDK
   source per `references/capability-envelope.md`. No git-URL SDKs, no
   workshop-level env/services keys, no invented SDK names or channels — an
   SDK name is CHECKABLE (`sdk find`/`sdk info`), so a guess never goes into
   `sdks:` at all; fall back to an in-project SDK or a GAP. Inside a hook the
   situation differs: an install command has no registry to check against,
   and the hook must install *something*. There, write the best candidate and
   mark it — inline `# UNVERIFIED:` plus an `Unverified:` entry in the verdict
   — never as settled fact. Knowing a tool is needed is not knowing how it is
   installed; the tag is what keeps that distinction visible to the reader.

3. **Every question carries a recommendation.** Never ask an open question.
Read the full skill on GitHub

Details

Skill name
onboard-workshop
Path
.github/skills/onboard-workshop/SKILL.md
License
GPL-3.0
Repo updated
18 November 2026

FAQ

What does the Onboard Workshop skill do?

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?".

How do I install the Onboard Workshop 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 Onboard Workshop popular?

It lives in canonical/use-workshop-skill, which has 9 GitHub stars and 2 forks.

Related skills

Design SDK

9

canonical/use-workshop-skill

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

Software Development

Use Workshop

9

canonical/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.

Software Development

Self Test Skill Invocation

9

konflux-ci/agent-plugins

Use when user asks to "test skill invocation framework" or mentions "canary skill test". This is a self-test skill to verify the test framework correctly loads and invokes skills.

Testing & QA18

Experiment Designer

9

Grafuja/Product-Manager-Skills

Design quick validation experiments for product features. Use this skill when the user needs to validate a hypothesis, test a feature idea before building, has low confidence in an initiative, or asks "should I build this" or "how do I validate this". Also trigger when user mentions prototypes, MVPs, testing, validation, or wants to reduce risk before investing in development. Guide them through choosing the right experiment method and defining success criteria.

Testing & QA

Grilling

9

HelmholtzAI-Consultants-Munich/helmholtz-agent-skills

Stress-tests plans, decisions, and ideas through probing questions and co-creation. Use when the user asks to be grilled or wants to develop and challenge their thinking through an interview.

Testing & QA

Spectacles 522 Portable Design

9

PtPavloTkachenko/spectacles-agent-skills

Design rules for building Spectacles lenses in Lens Studio 5.22 (CLAD/MCP workflow) so they downgrade to LS 5.15.4 for device testing in under an hour. Load when STARTING or architecting a new 5.22 Spectacles project that will later be tested on Spectacles (2024), when the user says "we will downgrade to 5.15" / "5.15-portable" / "we will test on device later", or before adding any shader/material/package to a 5.22 project that must survive the downgrade. Distilled from two full real-project migrations.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.