PremiumEmail Triage Automation
- Read full threads
- Sort into 3 buckets
- Draft in your voice
- Approve & send
← All skills · Automation · Retro Compiler

Premium
Premium
Free
PremiumAn example of what this Skill produces. Sample content, shown for illustration.
Retrospective — sample
Good: 3 | Problems: 3 | Actions: 3 | Gaps: 0 | Errors: 0 | Warnings: 0
Ranked: 1. Deploy was blocked twice — the pipeline was down for two hours — 3 signals ('blocked', 'down', 'twice'); 2. Checkout failed for old accounts after the deploy — 1 signal ('failed'); 3. We waited a day for the API key — 1 signal ('waited').
Actions: Add a deploy smoke test — Mei, due 2026-11-20; Backfill old-account test data — Chen, due 2026-11-22; Put API keys in the shared vault — Lin, due 2026-11-18.
What this report is not: a retro is a record of what the team said, not a verdict — the ranking counts impact-signal words, not severity.
Sprint 24 just ended — turn our retro notes into a document that ends in owned actions.Read https://skillu.dev/install/agent.md, then install the Retro Compiler skill (retro-compiler)./retro-compiler, and describe what you want in plain words.No. It means that problem matched the most impact-signal words in the notes — it is the most worth discussing first, not necessarily the most severe. A quiet problem with no signal words can still be the one that matters. The ranking is a sorting aid, not a severity verdict.
It stays in the report as Unassigned, and the warnings name it. The report never assigns work to someone who did not agree to it — if an action has no owner, the retro has an open question, not a finished plan.