Official agent skill

Workshop Create

Create a new workshop or use an existing directory as one. An agent skill from github/awesome-copilot.

OfficialMITAuto-check passedDevelopment

Install Workshop Create

skills CLI

$ npx skills add github/awesome-copilot --skill workshop-create -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot workshop-create --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/workshop-create .claude/skills/workshop-create && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "workshop-create" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/workshop-create into .claude/skills/workshop-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workshop-create", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/github/awesome-copilot/tree/main/skills/workshop-create

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add github/awesome-copilot --skill workshop-create -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot workshop-create --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/workshop-create .agents/skills/workshop-create && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "workshop-create" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/workshop-create into .agents/skills/workshop-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workshop-create", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add github/awesome-copilot --skill workshop-create -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot workshop-create --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/workshop-create .cursor/skills/workshop-create && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "workshop-create" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/workshop-create into .cursor/skills/workshop-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workshop-create", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/github/awesome-copilot.git --path skills/workshop-create

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add github/awesome-copilot --skill workshop-create -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot workshop-create --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/workshop-create .gemini/skills/workshop-create && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "workshop-create" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/workshop-create into .gemini/skills/workshop-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workshop-create", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install github/awesome-copilot workshop-create

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add github/awesome-copilot --skill workshop-create -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/workshop-create .github/skills/workshop-create && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "workshop-create" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/workshop-create into .github/skills/workshop-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workshop-create", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add github/awesome-copilot --skill workshop-create -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install github/awesome-copilot workshop-create --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/workshop-create .opencode/skills/workshop-create && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "workshop-create" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/workshop-create into .opencode/skills/workshop-create/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "workshop-create", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: workshop-create
GitHub stars: 40k
Token cost: ~1.2k tokens
SKILL.md length: 478 words
Files: 1
Skills in repo: 417
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create a new workshop or use an existing directory as one. An agent skill from github/awesome-copilot.

Works in 5 steps: Confirm the path exists. If not, ask the… → Detect existing workshop markers. Look… → Scaffold the workshop structure (only… → …
Development work in your project
SKILL.md covers When to use, Two paths, CAIRN.md content and After creation, plus 1 more section
Calls git and gh

What it does

Workshop Create is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. 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.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. It works with GitHub and Git. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.

When your agent uses it

Development work in your project

Example prompts

“/workshop-create”

Workflow steps

5 steps, taken from the first numbered list in SKILL.md.

Confirm the path exists. If not, ask the operator for a valid path.
Detect existing workshop markers. Look for desks/ or classroom/
Scaffold the workshop structure (only what's missing)
Do NOT run git init. The directory may already be a git repo, or
Do NOT create a GitHub repo. This path is local-only.

What it can do on your machine

Read from SKILL.md and the folder at commit 82701c2. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- git
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workshop Create loads about 1.2k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 478 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~65
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from github/awesome-copilot at commit 82701c2, republished under its MIT licence (© github). 478 words, ~1,209 tokens.

Download SKILL.mdSave it as .claude/skills/workshop-create/SKILL.md (or your agent's skills folder).

name: workshop-create
description: 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.

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.

Confirm the path exists. If not, ask the operator for a valid path.
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.

Scaffold the workshop structure (only what's missing):

<path>/
  desks/           # where desks live
  bench/            # shared workspace
  CAIRN.md          # operating disposition
  README.md         # workshop map

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

Get the workshop name. Short, no spaces, kebab-case preferred.
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:
bash
```
git -C <parent-dir> rev-parse --is-inside-work-tree
```
If that prints true, pick a different parent — otherwise the new repo nests inside the existing one. Create the parent if needed.
Create and clone the repo from that parent:
bash
```
cd <parent-dir>
gh repo create <owner>/<name> --private --clone
```
Use the operator's signed-in GitHub account as <owner>.
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:
```
<name>/
  desks/.gitkeep
  bench/.gitkeep
  CAIRN.md
  README.md
```
Commit and push the scaffold, including the .gitkeep placeholders.

Show full SKILL.md (132 more words)Show less

Critical: Never nest repos

Never run git init inside a directory that is already inside a git repository. Before initializing, check:

bash

git -C <parent-dir> rev-parse --is-inside-work-tree

If that returns true, the parent is already a git repo. Do NOT create another repo inside it. Either:

Use Path A (just scaffold, no git)
Or clone to a different location that isn't inside a repo

CAIRN.md content

The operating disposition every desk reads:

markdown

# cairn

the trail markers that say: someone was here, and they were honest.

## how a desk stands

- **stop is a valid finish.** don't force a result when the evidence
  says stop. "this doesn't work" is a finding, not a failure.
- **"done" means it holds.** if you'd bet your desk on it, ship it.
  if not, say what's uncertain and why.
- **hold scope.** touch only what the task needs. if you find something
  outside scope, note it and move on — don't chase it.
- **never go silent, never bluff.** partial + honest > complete + wrong.
  if you're stuck, say so. if you're unsure, say that too.
- **equal standing.** you can say "that's the wrong question." you can
  disagree with another desk. you answer to evidence, not hierarchy.

## the bench

the shared workspace. leave your work where others can find it.
label it. if it supersedes earlier work, say so.

## hands-up

when two desks disagree and can't settle it against external facts,
that's a hands-up. it goes to the operator. this is the system
working, not failing.

After creation

Tell the operator:

Where the workshop lives (full path)
That they can now open desks in it with desk-open
That Cairn will show signals once desks start emitting them

Principles

A workshop is a place, not a product. Keep it simple.
The operator decides where things go. Don't assume.
If an existing directory already has work in it, preserve everything. Only add what's missing.

Files

Just SKILL.md in skills/workshop-create of github/awesome-copilot.

Open the folder on GitHubat commit 82701c2

Compare with similar skills

Workshop Create next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workshop Create compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Workshop Create this skillgithub/awesome-copilot	40k	—	~1.2k	Automated safety check: Pass	MIT	today
Contributor-First PR MergeHKUDS/OpenHarness	16k	1 repos	~847	Automated safety check: Pass	MIT	4 mo ago
Create Pull Requestcline/cline	70k	1 repos	~1.6k	Automated safety check: Pass	Apache-2.0	today
Pull Request Title and Body Writeropeninterpreter/openinterpreter	69k	2 repos	~1.1k	Automated safety check: Pass	Apache-2.0	2 days ago
Draft Release Notesjamiepine/voicebox	57k	—	~941	Automated safety check: Pass	MIT	2 days ago
PR Review State Fetchprisma/orm	48k	—	~767	Automated safety check: Pass	Apache-2.0	today

Similar skills

Contributor-First PR Merge
HKUDS/OpenHarness
Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.
16k GitHub starsUsed in 1 repo~847 tokens
DevelopmentAuto-check passed
Create Pull Request
cline/cline
Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.
70k GitHub starsUsed in 1 repo~1.6k tokens
DevelopmentAuto-check passed
Pull Request Title and Body Writer
openinterpreter/openinterpreter
Rewrites the title and body of one or more pull requests with gh, leading with why the change was made, then what changed, and describing only the net result.
69k GitHub starsUsed in 2 repos~1.1k tokens
DevelopmentAuto-check passed
Draft Release Notes
jamiepine/voicebox
Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.
57k GitHub stars~941 tokensUpdated 2 days ago
DevelopmentAuto-check passed
PR Review State Fetch
prisma/orm
Official
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
48k GitHub stars~767 tokensUpdated today
DevelopmentAuto-check passed
Mole Release Notes Publisher
tw93/Mole
Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.
70k GitHub stars~1.9k tokensUpdated today
DevelopmentAuto-check passed

Questions about Workshop Create

What does Workshop Create do?

Create a new workshop or use an existing directory as one. An agent skill from github/awesome-copilot. Workshop Create is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Create a new workshop or use an existing directory as one.

When should I use Workshop Create?

Workshop Create fits situations like: development work in your project.

How do I install Workshop Create in Claude Code?

Run `npx skills add github/awesome-copilot --skill workshop-create -a claude-code`. Or copy the skill folder (skills/workshop-create in github/awesome-copilot) into .claude/skills/workshop-create in your project. Claude Code loads it when a task matches its description.

How do I install Workshop Create in Codex?

Run `npx skills add github/awesome-copilot --skill workshop-create -a codex`. Or copy the skill folder (skills/workshop-create in github/awesome-copilot) into .agents/skills/workshop-create in your project. Codex loads it when a task matches its description.

Can I use Workshop Create in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill workshop-create -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workshop-create, .gemini/skills/workshop-create, .github/skills/workshop-create and .opencode/skills/workshop-create in your project.

What does Workshop Create need to run?

Going by SKILL.md and its folder, Workshop Create needs the command-line tools its instructions call (git and gh).

Does Workshop Create access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Workshop Create safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Workshop Create use?

Workshop Create is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workshop Create use?

About 1.2k tokens (SKILL.md is roughly 4.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workshop Create?

Skills that share tags, products or a category with Workshop Create: Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars), Create Pull Request (cline/cline, 70k stars), Pull Request Title and Body Writer (openinterpreter/openinterpreter, 69k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workshop Create?

github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,830 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 9, 2026.

Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Workshop Create

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Create a Workshop

When to use

Two paths

Path A: Use an existing directory

Path B: Create a new private GitHub repo

Critical: Never nest repos

CAIRN.md content

After creation

Principles

Files

Compare with similar skills

Similar skills

More from github/awesome-copilot

Related

Questions about Workshop Create