skill tutorial · agent

Workshop skills in Cline

Cline is an agent with a real terminal and a rules folder — .clinerules/ — which makes it an excellent skill host without any loader: every file in that folder is standing context, and every command in a skill it can run.

Set it up

One folder of bundles plus one small index rule telling Cline where to look:

repo layout

my-workshop-drawer/ skills/ blind-portrait/ (from blind-portrait.zip) minefield/ (from minefield.zip) .clinerules/ workshop-skills.md # fetch: cd skills curl -LO https://workshopskill.com/en/activities/blind-portrait/files/blind-portrait.zip unzip blind-portrait.zip

The standing rule

One short rule makes the drawer the default context — the skills themselves load on demand.

.clinerules/workshop-skills.md

This repo preps workshops from ./skills/. When asked to prep, adapt or explain an activity: 1. Read the matching skills/<name>/SKILL.md first. 2. Run its commands as printed (curl downloads are safe, anonymous). 3. Use metadata fields for group-size scaling and props. 4. For the live measure: run formlm-cli steps only after I confirm.

First run

Ask: prep minefield for 4 pairs, first trust session, worried about safety. Cline reads the skill, fetches prop cards and the safety debrief, and surfaces the stop-word rule because the facilitation notes say that is where trust sessions go wrong. Everything lands in the repo folder — reviewable, printable, versionable.

Without terminal access

Deny-all-commands setup? The skill still works as knowledge: Cline's browser tool can open the SKILL.md URL directly, or you paste the file. The curl lines simply become tasks for you: print these five PDFs Tuesday.

keep going

Roo Code noteSame .clinerules mechanism works in Roo — read this walkthrough as-is. The skills, end to endHow discover → install → run is meant to work. Amp walkthroughTerminal-first, threads instead of rules.

questions

Roo Code too?

Yes. Roo reads .clinerules (and its own .roo/rules); point either at the same skills/ folder.

Does every SKILL.md fill the context?

Rules are standing context, but skills files are read on demand — only the file the brief matched enters the conversation.

Can Cline version my workshop repo with skills inside?

That is the recommended shape: bundles + run-sheet edits in git make the prep diff-able. CC BY 4.0 permits it.