lab-retro/SKILL.md
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 skillsauth add glebis/claude-skills lab-retroInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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:
"Что вы умели ДО лаборатории?" (multiSelect)
"Что вы умеете ПОСЛЕ?" (multiSelect)
"Сколько часов в неделю экономит Claude Code?" (singleSelect)
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:
"Для какой задачи был промт?" (singleSelect)
"Что сделало его эффективным?" (multiSelect)
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:
"Главная рабочая задача на месяц?" (singleSelect)
"Сколько времени в неделю готовы уделять?" (singleSelect)
"Какой риск выгорания вы оцениваете для себя?" (singleSelect)
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 textdevelopment
--- name: agency-docs-updater description: End-to-end pipeline for publishing Claude Code lab meetings. Accepts optional args: date (YYYYMMDD, "yesterday", "today") and lab number (e.g. "04"). Examples: "yesterday 04", "20260420 05", "04" (today, lab 04), "" (today, auto-detect lab). --- # Agency Docs Updater Execute ALL steps automatically in sequence. Only pause if a step fails and cannot be recovered. Read `references/learnings.md` before starting for known pitfalls. **Configuration**: pat
tools
This skill should be used when applying proper typography to prose text or files in Russian, English, German, or French — smart quotes per locale («ёлочки», “curly”, „Gänsefüßchen“, « guillemets »), correct dashes (тире, em/en dash, Gedankenstrich, tiret), non-breaking spaces, ranges, ellipsis, and French espaces insécables before ! ? ; :. Fully deterministic via a pinned typograf-based CLI; never apply these rules by hand. Triggers on "типографика", "typograf", "оттипографь", "smart quotes", "fix typography", "неразрывные пробелы".
development
This skill should be used when inspecting or applying advanced OpenType features of a font (woff2/otf/ttf) — ligatures, stylistic sets (ss01–ss20), character variants (cvXX), texture healing, slashed zero, tabular/oldstyle figures, fractions, small caps, case-sensitive forms — and generating the CSS to enable them. Interviews the user via cenno to pick features. Triggers on "OpenType features", "font features", "stylistic sets", "ligatures", "texture healing", "tabular figures", "what can this font do".
tools
--- name: pre-session-portrait description: Build a compressed, visualizable "portrait" of a consulting/coaching client before a session, so the paid hour is spent solving, not scoping. Runs a 7-lens JTBD-inspired interview (where / how / what / problem / ideal / tension / jobs-to-be-done) that takes rich open answers in and compresses them to an 11-field YAML portrait out. Delivers three ways: raw paste-into-a-clean-chat prompt, a secret GitHub gist link, or a Codex CLI one-liner. Use when prep