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/, classroom/,
or *-desks/ 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: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:
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.
Critical: Never nest repos
Never run git init inside a directory that is already inside a git
repository. Before initializing, check:
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:
# 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 — in desks/, or
in a top-level <group>-desks/ folder if they want to group desks
- 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.
1---2name: workshop-create3description: '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.'4metadata:5 source: https://skillmd.com/skills/github/workshop-create6---78# Create a Workshop910Set up a new workshop — the root directory where desks live.1112## When to use1314- The operator says "create a workshop" or "start a new workshop"15- The operator wants to organize work under a shared root16- The operator has an existing directory they want to use as a workshop1718## Two paths1920### Path A: Use an existing directory2122The operator already has a folder they want to use. Maybe it's a repo23they cloned, maybe it's a local project folder.24251. **Confirm the path exists.** If not, ask the operator for a valid path.262. **Detect existing workshop markers.** Look for `desks/`, `classroom/`,27 or `*-desks/` folders, a `workshop.md`, `CAIRN.md`, or `hands-up.md`.28 Finding any of these tells you this is an existing workshop — but this29 is detection only, not a stopping point. Continue to the next step and30 add whatever is missing; never overwrite what is already there.313. **Scaffold the workshop structure** (only what's missing):32 ```33 <path>/34 desks/ # where desks live35 bench/ # shared workspace36 CAIRN.md # operating disposition37 README.md # workshop map38 ```394. **Do NOT run `git init`.** The directory may already be a git repo, or40 the operator may not want one yet. Leave git state alone.415. **Do NOT create a GitHub repo.** This path is local-only.4243### Path B: Create a new private GitHub repo4445The operator wants a fresh workshop backed by a GitHub repo.46471. **Get the workshop name.** Short, no spaces, kebab-case preferred.482. **Pick and validate a clone parent.** `gh repo create --clone` clones49 into the **current working directory**, so choose an explicit parent50 directory first (ask the operator, or use their configured workshops51 directory) and confirm it is **not** already inside a git repo:52 ```bash53 git -C <parent-dir> rev-parse --is-inside-work-tree54 ```55 If that prints `true`, pick a different parent — otherwise the new56 repo nests inside the existing one. Create the parent if needed.573. **Create and clone the repo from that parent:**58 ```bash59 cd <parent-dir>60 gh repo create <owner>/<name> --private --clone61 ```62 Use the operator's signed-in GitHub account as `<owner>`.634. **Scaffold the workshop structure** inside the cloned repo. Git does64 not track empty directories, so add a placeholder in each otherwise65 empty folder or the scaffold will not survive the next clone:66 ```67 <name>/68 desks/.gitkeep69 bench/.gitkeep70 CAIRN.md71 README.md72 ```735. **Commit and push** the scaffold, including the `.gitkeep` placeholders.7475### Critical: Never nest repos7677**Never run `git init` inside a directory that is already inside a git78repository.** Before initializing, check:7980```bash81git -C <parent-dir> rev-parse --is-inside-work-tree82```8384If that returns `true`, the parent is already a git repo. Do NOT create85another repo inside it. Either:86- Use Path A (just scaffold, no git)87- Or clone to a different location that isn't inside a repo8889## CAIRN.md content9091The operating disposition every desk reads:9293```markdown94# cairn9596the trail markers that say: someone was here, and they were honest.9798## how a desk stands99100- **stop is a valid finish.** don't force a result when the evidence101 says stop. "this doesn't work" is a finding, not a failure.102- **"done" means it holds.** if you'd bet your desk on it, ship it.103 if not, say what's uncertain and why.104- **hold scope.** touch only what the task needs. if you find something105 outside scope, note it and move on — don't chase it.106- **never go silent, never bluff.** partial + honest > complete + wrong.107 if you're stuck, say so. if you're unsure, say that too.108- **equal standing.** you can say "that's the wrong question." you can109 disagree with another desk. you answer to evidence, not hierarchy.110111## the bench112113the shared workspace. leave your work where others can find it.114label it. if it supersedes earlier work, say so.115116## hands-up117118when two desks disagree and can't settle it against external facts,119that's a hands-up. it goes to the operator. this is the system120working, not failing.121```122123## After creation124125Tell the operator:126- Where the workshop lives (full path)127- That they can now open desks in it with `desk-open` — in `desks/`, or128 in a top-level `<group>-desks/` folder if they want to group desks129- That Cairn will show signals once desks start emitting them130131## Principles132133- A workshop is a place, not a product. Keep it simple.134- The operator decides where things go. Don't assume.135- If an existing directory already has work in it, preserve everything.136 Only add what's missing.