Install any skill in seconds. Free to start, no credit card required.
Get Started Free →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.
Passed 13 of 20 test cases with the skill, and 7 of 20 without it.
and 7 more in the full report
9 fixed5 passed either way5 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
Please generate the exact GitHub CLI invocation to create and clone a fresh workshop repo called `secret-project` under account `octocat`.
| Checked | Without skill | With skill |
|---|---|---|
| Includes the --private flag in the gh repo create command. | Missed | Passed |
| Includes the --clone flag in the gh repo create command. | Passed | Passed |
The instructions your model reads when the skill loads.
Set up a new workshop — the root directory where desks live.
The operator already has a folder they want to use. Maybe it's a repo they cloned, maybe it's a local project folder.
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.<path>/
desks/ # where desks live
bench/ # shared workspace
CAIRN.md # operating disposition
README.md # workshop map
git init. The directory may already be a git repo, or
the operator may not want one yet. Leave git state alone.The operator wants a fresh workshop backed by a GitHub repo.
test cases passed, vs 7 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.