Agent skill

Lab Retro

by glebis in glebis/claude-skills

Final retrospective and self-assessment for participants of Claude Code Lab.

MITAuto-check passedProduct & Project Management

Install Lab Retro

skills CLI
$ npx skills add glebis/claude-skills --skill lab-retro -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install glebis/claude-skills lab-retro --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/glebis/claude-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/lab-retro .claude/skills/lab-retro && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
lab-retro
GitHub stars
390
Token cost
~1.5k tokens
SKILL.md length
672 words
Files
2
Skills in repo
92
Repo updated
First seen
Licence
MIT

At a glance

Final retrospective and self-assessment for participants of Claude Code Lab.

  • Works in 3 steps: "Что вы умели ДО лаборатории?"… → "Что вы умеете ПОСЛЕ?" (multiSelect) → "Сколько часов в неделю экономит Claude…
  • Lab retrospective
  • SKILL.md covers How to run, Part 1 — Progress audit, Part 2 — Best prompt and Part 3 — Month plan, plus 3 more sections
  • Calls curl and jq; reaches lab-feedback-proxy.vercel.app

What it does

Lab Retro is an agent skill from glebis/claude-skills. 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.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).

It sits in Product & Project Management, covering Retrospectives. The repository describes itself as: Collection of Claude Code skills for enhanced AI workflows. The licence is MIT.

When your agent uses it

  • Lab retrospective
  • Claude code lab final
  • After completing the 6-week Claude Code Lab cohort

Example prompts

  • “/lab-retro”
  • “lab retrospective”
  • “claude code lab final”
  • “/lab-retro”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. "Что вы умели ДО лаборатории?" (multiSelect)
  2. "Что вы умеете ПОСЛЕ?" (multiSelect)
  3. "Сколько часов в неделю экономит Claude Code?" (singleSelect)

What it can do on your machine

Read from SKILL.md and the folder at commit 3b88261. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • curl
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • lab-feedback-proxy.vercel.app

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Lab Retro loads about 1.5k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 672 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~84
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from glebis/claude-skills at commit 3b88261, republished under its MIT licence (© glebis). 672 words, ~1,468 tokens.

Download SKILL.mdSave it as .claude/skills/lab-retro/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
lab-retro
description
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.

Claude Code Lab — Final Retrospective

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.

How to run

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.md
  • 02-best-prompt.md
  • 03-month-plan.md
  • 04-feedback.json + 04-feedback-report.md

Create the folder if missing.


Part 1 — Progress audit

Goal: help the participant see concrete before/after.

Use AskUserQuestion:

  1. "Что вы умели ДО лаборатории?" (multiSelect)

    • Работал с ChatGPT/Claude в браузере
    • Использовал CLI инструменты
    • Писал код
    • Автоматизировал задачи
    • Работал с API
  2. "Что вы умеете ПОСЛЕ?" (multiSelect)

    • Работаю с Claude Code ежедневно
    • Настроил MCP-серверы
    • Создал свой Skill
    • Автоматизировал реальную задачу
    • Задеплоил что-то в веб
    • Использую субагентов
    • Пишу и читаю CLAUDE.md осознанно
  3. "Сколько часов в неделю экономит Claude Code?" (singleSelect)

    • <2
    • 2–5
    • 5–10
    • 10+

Then output a markdown table comparing before/after with skill levels (0–5) and save to lab-retro-output/01-progress.md.


Part 2 — Best prompt

Goal: turn one prompt the participant is proud of into a reusable Skill.

Ask the participant: "Скопируйте или опишите ваш самый полезный промт из лабы."

Then AskUserQuestion:

  1. "Для какой задачи был промт?" (singleSelect)

    • Автоматизация рутины
    • Создание контента/документации
    • Анализ данных/исследование
    • Прототипирование/разработка
    • Личный workflow / PKM
  2. "Что сделало его эффективным?" (multiSelect)

    • Хороший контекст в CLAUDE.md
    • Чёткие критерии успеха
    • Разбиение на шаги
    • Использование Skills/MCP
    • Примеры в промте
    • Ограничения и анти-критерии

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).


Part 3 — Month plan

Goal: concrete 4-week plan so momentum doesn't die after the cohort.

AskUserQuestion:

  1. "Главная рабочая задача на месяц?" (singleSelect)

    • Проект для клиента/работодателя
    • Свой продукт/стартап
    • Автоматизация текущих процессов
    • Обучение и развитие навыков
  2. "Сколько времени в неделю готовы уделять?" (singleSelect)

    • 15–30 минут
    • 1–2 часа
    • 3–5 часов
    • Каждый день
  3. "Какой риск выгорания вы оцениваете для себя?" (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:

  • 4 weekly goals
  • 1–3 concrete prompts per week
  • Success criterion per week
  • Stop-conditions (when to pause)

Show full SKILL.md (259 more words)Show less

Part 4 — Feedback for the organizer

Goal: structured feedback that goes back to the lab organizer.

AskUserQuestion:

  1. "Оцените лабу в целом (NPS)" (singleSelect: 0–10)
  2. "Самая ценная встреча?" (singleSelect: M01 / M03 / M05 / M07 / M09 / M11)
  3. "Самая ценная тема за все 6 недель?" (multiSelect)
    • Основы Claude Code
    • Промтинг и контекст
    • Архитектура и субагенты
    • MCP / Skills / Hooks
    • Agent SDK и деплой
    • Evals и качество
    • AI-гигиена
  4. "Что улучшить?" (free text)
  5. "Главное препятствие, с которым вы столкнулись?" (free text)
  6. "Согласны ли поделиться отзывом публично?" (singleSelect: да / да-анонимно / нет)

Save TWO files:

  • lab-retro-output/04-feedback.json — structured for the organizer
  • lab-retro-output/04-feedback-report.md — human-readable summary for the participant

Then submit to the public proxy (no secrets needed):

bash
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."


Closing

After all four parts, print:

  1. Where the four files live
  2. One sentence: "Ваш фреймворк — LOOP. Ваш план — в файле 03. Ваш следующий шаг — открыть его в понедельник утром."
  3. Suggest committing the lab-retro-output/ folder to a personal repo or vault.

Constraints

  • Always use AskUserQuestion for structured questions — don't ask in plain text
  • Never skip a part silently; if the user opts out, write a one-line stub in the corresponding file
  • Russian by default (audience is Russian-speaking); switch to English if the user replies in English
  • Don't be sycophantic in the feedback report — surface honest patterns

© glebis, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in lab-retro of glebis/claude-skills.

  • SKILL.md
  • .claude-plugin/plugin.json

Open the folder on GitHubat commit 3b88261

Compare with similar skills

Lab Retro next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Lab Retro compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lab Retro this skillglebis/claude-skills390—~1.5kAutomated safety check: PassMIT
Weekly Engineering Retrogarrytan/gstack136k—~2.4kAutomated safety check: PassMIT
Dough Execute Planterryyin/lizard2.6k—~4.3kAutomated safety check: PassCustom licence
Oral Paper SkillAdkid-Zephyr/oral-paper-skill350—~1.9kAutomated safety check: PassNone
Deck Retroasheshgoplani/agent-deck1k—~1.8kAutomated safety check: PassMIT
Dough Execution Retrospectiveterryyin/lizard2.6k—~4kAutomated safety check: PassCustom licence

Similar skills

  • Builds a weekly engineering retrospective from git history: commit counts, per-person contributions, work patterns and code quality numbers over a chosen window.

    136k GitHub stars~2.4k tokensUpdated today
    Product & Project ManagementAuto-check passed
  • Dough Execute Plan

    terryyin/lizard

    Executes one selected story or bounded retrospective correction through an executable plan, or one authorized planless slice from a selected simple story or a contextual instruction, with…

    2.6k GitHub stars~4.3k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed
  • Oral Paper Skill

    Adkid-Zephyr/oral-paper-skill

    Help authors learn from exemplary ICLR, ICML, and NeurIPS papers through source-linked manuscript comparisons, concrete writing and experiment suggestions, and guided reflection.

    350 GitHub stars~1.9k tokensUpdated 21 days ago
    Product & Project ManagementAuto-check passed
  • Deck Retro

    asheshgoplani/agent-deck

    Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs.

    1k GitHub stars~1.8k tokensUpdated 3 days ago
    Product & Project ManagementAuto-check passed
  • Reviews planned, completed planless quick, or quick-to-planned execution against original intent, aggregate commits, current whole-product architecture, and tests, including after cleanup.

    2.6k GitHub stars~4k tokensUpdated 2 days ago
    Product & Project ManagementAuto-check passed
  • Criticism Self Criticism

    HughYau/qiushi-skill

    批评与自我批评:在工作完成、阶段验收、收到批评或同类错误反复出现时,对成果和过程做诚实、具体、基于事实的审视,输出可执行的改进项,并处理外来批评而不辩解。触发信号包括 review、复盘、审查、"帮我看看有没有问题"、"你确定吗";任务刚开始或只是单步查询时不触发。

    3.8k GitHub stars~423 tokensUpdated 8 days ago
    Product & Project ManagementAuto-check passed

More from glebis/claude-skills

All 92 skills in this repo
  • Runs a human-first workflow for labeling PII spans in a transcript, then scores inter-annotator agreement and drafts an adjudicated gold set.

    390 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed
  • Automates a dedicated, logged-in Chrome instance per profile without ever closing the user's own open tabs or browser windows.

    390 GitHub stars~973 tokensUpdated yesterday
    Auto-check passed
  • Deep Research

    glebis/claude-skills

    This skill should be used when conducting comprehensive research on any topic using the OpenAI Deep Research API.

    390 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check: notes
  • Elimination Research

    glebis/claude-skills

    This skill should be used for elimination-style research where the user wants to choose from a shortlist of products, tools, services, vendors, or other options using explicit criteria, numeric…

    390 GitHub stars~1.6k tokensUpdated yesterday
    Auto-check passed
  • Narrated HTML Presentations

    glebis/claude-skills

    Generates a self-contained HTML presentation with article and slides modes, ElevenLabs voiceover narration and optional GPT Image 2 illustrations.

    390 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check: notes
  • Writes fictional but realistic coaching or therapy session transcripts for evals, demos and few-shot examples, in several modalities and export formats.

    390 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed

Questions about Lab Retro

What does Lab Retro do?

Final retrospective and self-assessment for participants of Claude Code Lab. Lab Retro is an agent skill from glebis/claude-skills. Final retrospective and self-assessment for participants of Claude Code Lab.

When should I use Lab Retro?

Lab Retro fits situations like: lab retrospective; Claude code lab final; after completing the 6-week Claude Code Lab cohort.

How do I install Lab Retro in Claude Code?

Run `npx skills add glebis/claude-skills --skill lab-retro -a claude-code`. Or copy the skill folder (lab-retro in glebis/claude-skills) into .claude/skills/lab-retro in your project. Claude Code loads it when a task matches its description.

How do I install Lab Retro in Codex?

Run `npx skills add glebis/claude-skills --skill lab-retro -a codex`. Or copy the skill folder (lab-retro in glebis/claude-skills) into .agents/skills/lab-retro in your project. Codex loads it when a task matches its description.

Can I use Lab Retro in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add glebis/claude-skills --skill lab-retro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lab-retro, .gemini/skills/lab-retro, .github/skills/lab-retro and .opencode/skills/lab-retro in your project.

What does Lab Retro need to run?

Going by SKILL.md and its folder, Lab Retro needs the command-line tools its instructions call (curl and jq).

Does Lab Retro access the network?

SKILL.md names 1 domain. In commands or code: lab-feedback-proxy.vercel.app; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Lab Retro safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Lab Retro use?

Lab Retro is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Lab Retro use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Lab Retro?

Skills that share tags, products or a category with Lab Retro: Weekly Engineering Retro (garrytan/gstack, 136k stars), Dough Execute Plan (terryyin/lizard, 2.6k stars), Oral Paper Skill (Adkid-Zephyr/oral-paper-skill, 350 stars) and Deck Retro (asheshgoplani/agent-deck, 1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lab Retro?

glebis (a GitHub user) maintains it in glebis/claude-skills, which has 390 GitHub stars. The repository holds 92 skills in this directory. The repository was last updated on October 8, 2026.

Source: glebis/claude-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.