skill tutorial · agent
Workshop skills in Gemini CLI
Gemini CLI has no skills directory of its own — but it has context files and a shell, and that is exactly what a WorkshopSkill folder needs: import the SKILL.md, let the model run its printed commands.
Install the folder
Keep a drawer folder anywhere — ~/skills works:
download two skills
mkdir -p ~/skills && cd ~/skills curl -LO https://workshopskill.com/en/activities/blind-portrait/files/blind-portrait.zip curl -LO https://workshopskill.com/en/activities/the-orange/files/the-orange.zip unzip -o '*.zip'
Wire it in through GEMINI.md
Gemini CLI reads GEMINI.md as context and supports @file imports. From your workshop-prep folder, import the skills you run this season; /memory reloads the context.
GEMINI.md in the prep folder
# Workshop prep Skills from https://workshopskill.com (CC BY 4.0). Import the ones installed: @~/skills/blind-portrait/SKILL.md @~/skills/the-orange/SKILL.md When I describe a session brief, match it against the imported skills, then run their prep commands as printed.
First run
Inside Gemini CLI:
exchange
> prep the orange for two teams, 45 minutes, conflict training Gemini reads the imported skill, curls prop cards, briefs and debrief into the folder, prints the run sheet digest, and offers the live pre/post measure command (needs a FormLM login).
Troubleshooting
- Too many imports bloating context? Import one or two per project; the rest stay in skills.json one curl away.
- Tool confirmation slowing curls? Approve the first curl; identical commands are auto-approved in the same session.
- Chinese materials? Use the zh or zh-hant bundles — the whole workflow is identical, files named in Chinese.
keep going
questions
Does Gemini CLI support SKILL.md natively?
As of writing, no native skills loader — the GEMINI.md import pattern gives the same effect: the file is in context, the shell is available.
Where do the printed PDFs go?
Into the current directory — the curl steps use -O/-LO. Keep one folder per upcoming session and print from it.
Do I need an API key for the downloads?
No. Discovery and install are anonymous HTTPS; only the optional FormLM measure step needs a (free) account login.