glebis/lab-retro
Final retrospective and self-assessment for participants of Claude Code Lab. Runs four sequential interactive parts — progress audit, best prompt, monthly plan, and feedback — using AskUserQuestion. Triggers on "/lab-retro", "lab retrospective", "claude code lab final", or after completing the 6-week Claude Code Lab cohort.
npx skills add https://github.com/glebis/claude-skills --skill lab-retro
This skill walks a Claude Code Lab graduate through four sequential exercises that consolidate their learning, capture their best work, plan next steps, and collect structured feedback for the organizer.
Default flow: run all four parts in order. The user can also jump to a specific part with /lab-retro 2 (or just say "part 3").
Between parts, briefly summarize what just happened and ask "ready for part N?" so the user controls the pace.
All artifacts are saved into a single folder lab-retro-output/ in the current working directory:
01-progress.md02-best-prompt.md03-month-plan.md04-feedback.json + 04-feedback-report.mdCreate the folder if missing.
Goal: help the participant see concrete before/after.
Use AskUserQuestion:
Then output a markdown table comparing before/after with skill levels (0–5) and save to lab-retro-output/01-progress.md.
Goal: turn one prompt the participant is proud of into a reusable Skill.
Ask the participant: *"Скопируйте или опишите ваш самый полезный промт из лабы."*
Then AskUserQuestion:
Reformat the prompt as a proper Skill (frontmatter + body), suggest an description line that would trigger it, and save to lab-retro-output/02-best-prompt.md. Suggest where to put it (~/.claude/skills/<name>/SKILL.md).
Goal: concrete 4-week plan so momentum doesn't die after the cohort.
AskUserQuestion:
If risk = high, insert a mandatory rest day into the plan and a recommendation to read the AI hygiene slide again.
Generate lab-retro-output/03-month-plan.md with:
Goal: structured feedback that goes back to the lab organizer.
AskUserQuestion:
Save TWO files:
lab-retro-output/04-feedback.json — structured for the organizerlab-retro-output/04-feedback-report.md — human-readable summary for the participantThen submit to the public proxy (no secrets needed):
curl -sS -X POST https://lab-feedback-proxy.vercel.app/api/feedback \
-H "Content-Type: application/json" \
-d "$(jq -nc --arg name "<participant name>" --slurpfile notes lab-retro-output/04-feedback.json '{name:$name, notes:($notes[0]|tostring)}')"
The proxy forwards to Baserow table 746002 with a server-side token. Response is {"ok":true,"row_id":<N>}. Confirm row ID with the participant.
If the request fails, fall back to local files only and tell the participant: "submit failed — your feedback is saved locally in lab-retro-output/04-feedback.json, send it to the organizer manually."
After all four parts, print:
lab-retro-output/ folder to a personal repo or vault.AskUserQuestion for structured questions — don't ask in plain textTake glebis/lab-retro from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.