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 textdocumentation
Cut a software release and maintain a tiered compatibility policy. Use when the user wants to release, ship a version, bump the version, tag a release, write a changelog, or update COMPATIBILITY. Config-driven via release.config.json; bumps version files, runs a readiness gate, updates COMPATIBILITY.md tiers and deprecations, tags (→ release workflow), and reports closed issues. Teaches the underlying standards as it runs.
development
Sync and manage bilingual (EN/RU) library content for agency-docs. Use when adding, updating, or reviewing library articles. Handles translation, sync checks, and Russian stylistic review.
development
This skill should be used to watch a long-running background job (ffmpeg/media encode, qmd or other embedding/vector-DB run, batch agent/LLM pipeline, or a real-browser/agent-browser daemon) until it finishes or wedges, then deliver a verdict (done, needs-attention, or blocked) plus the exact next command, without burning dozens of manual poll commands. Triggers on "babysit this job", "watch this until it's done", "ping me when the encode/embed/batch finishes", "is this background process stuck", "monitor this ffmpeg/qmd run", or any request to wait on a long-running process and be told when it's complete or hung.
development
Use when the user wants Claude Code, Codex, or other AI coding/business agents to work together as peers. This skill should be used whenever the user mentions coordinating Claude Code and Codex, agent handoffs, multi-agent workflows, parity, respect, pushback between agents, deciding which agent should lead, or turning a business/code workflow into a two-agent operating model.