TeamRetroHQ/teamretro-skills / skills/ai-session-retro
ai-session-retro
VerifiedUse when a working session with an AI is wrapping up and should be reviewed and logged — "run a retro on this session", "AI session retro", "debrief this session", "log this session" — or when asked to retro a past session from a transcript. Offer it proactively at the natural end of a large or multi-step session. Do NOT use this to create or facilitate a retrospective in a retrospective product (TeamRetro or similar) — this skill reviews AI working sessions only.
| File | Kind | Size |
|---|---|---|
| SETUP.md | markdown | 3.4 KB |
| SKILL.md | skill md | 11.8 KB |
| evals/evals.json | config | 2.9 KB |
| evals/fixtures/existing-entries/docs/ai-retros/entries/2026-07-06-support-ticket-theme-analysis.md | markdown | 790 B |
| evals/fixtures/existing-entries/docs/ai-retros/entries/2026-07-09-onboarding-email-sequence.md | markdown | 594 B |
| evals/fixtures/existing-entries/transcript-2.md | markdown | 1.1 KB |
| evals/fixtures/transcript-1.md | markdown | 1.6 KB |
evals/fixtures/existing-entries/transcript-2.md
View on GitHub# Session transcript (simulated) — 2026-07-13
[Turn 1] USER: I need a webinar follow-up email sequence. 3 emails: day 0 (recording link), day 2 (case study), day 5 (trial CTA). CTA should go to the trial signup page. Tone like our onboarding emails.
[Turn 2] AGENT: Clear brief — 3 emails, cadence and CTA target specified. Drafting now.
(Agent drafts all three emails.)
[Turn 5] AGENT: All three drafted, matched to the onboarding email tone.
[Turn 6] USER: These are good. But use the attendee's first name merge tag — we're on Customer.io, the tag format is {{customer.first_name}}, not the {FirstName} you used.
[Turn 7] AGENT: Fixed — I guessed a generic merge-tag format since the email platform wasn't mentioned. All three updated.
[Turn 8] USER: Also can you check what subject lines performed best in our last webinar sequence? Should be in Customer.io.
[Turn 9] AGENT: I don't have a Customer.io connector available, so I can't pull past campaign stats. I've written two subject-line options per email instead, based on general best practice.
[Turn 10] USER: Fine. Ship it. Done for today — run a retro on this session and log it please.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Unverified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |