Agent skill · software engineering · github
workshop-create
Create a new workshop or use an existing directory as one. Handles two paths: (A) use an existing local directory the operator points at, or (B) create a new private GitHub repo in the signed-in account. Never creates a repo inside another repo.
Why this skill is useful
Adds specific GitHub CLI commands and directory structure patterns for workshop creation that the AI wouldn't reliably generate on its own.
What it needs
Requires gh installed locally. Requires github account access. About 3k tokens when loaded. Last updated 2026-08-07. 37,534 stars on the source repository.
What this skill does
Create a Workshop Set up a new workshop — the root directory where desks live. When to use The operator says "create a workshop" or "start a new workshop" The operator wants to organize work under a shared root The operator has an existing directory they want to use as a workshop Two paths Path A: Use an existing directory The operator already has a folder they want to use. Maybe it's a repo they cloned, maybe it's a local project folder. 1. Confirm the path exists. If not, ask the operator for a valid path. 2. Detect existing workshop markers. Look for desks/ or classroom/ folders, a workshop.md, CAIRN.md, or hands-up.md. Finding any of these tells you this is an existing workshop — but this is detection only, not a stopping point. Continue to the next step and add whatever is missing; never overwrite what is already there. 3. Scaffold the workshop structure (only what's missing): 4. Do NOT run git init. The directory may already be a git repo, or the operator may not want one yet. Leave git state alone. 5. Do NOT create a GitHub repo. This path is local-only. Path B: Create a new private GitHub repo The operator wants a fresh workshop backed by a GitHub repo. 1. Get the workshop name. Short, no spaces, kebab-case preferred. 2. Pick and validate a clone parent. gh repo create --clone clones into the current working directory, so choose an explicit parent directory first (ask the operator, or use their configured workshops directory) and confirm it is not already inside a git repo: If that prints true, pick a different parent — otherwise the new repo nests inside the existing one. Create the parent if needed. 3. Create and clone the repo from that parent: Use the operator's signed-in GitHub account as <owner>. 4. Scaffold the workshop structure inside the cloned repo. Git does not track empty directories, so add a placeholder in each otherwise empty folder or the scaffold will not survive the next clone: 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills github/workshop-create