Lab Retro logo

Lab Retro

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

Overview

Publisherglebis
Repositoryclaude-skills
Skill namelab-retro
Stars
379
Forks
56
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by glebis on GitHub. Read the source before you install it.

Installation

Install the Lab Retro AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/glebis/claude-skills.git /tmp/claude-skills
mkdir -p .claude/skills
cp -r /tmp/claude-skills/lab-retro .claude/skills/lab-retro
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Lab Retro in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Lab Retro on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Lab Retro is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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)

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

Frequently asked questions

What does the Lab Retro AI skill do?

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.

Why use Lab Retro on TypingMind?

Because you install it once and use it with any model. Lab Retro is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Lab Retro in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/glebis/claude-skills/tree/main/lab-retro. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Lab Retro?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Lab Retro?

As many as you like. As long as a model supports skills, you can use Lab Retro with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Lab Retro AI skill free?

Yes. It is published on GitHub by glebis under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇