Debrief
Use at the END of a piece of work for a deck, slides, or a presentation of what changed and why. Triggers on: 'make a deck about this', 'slides for the demo', 'presentation of what we did', 'build me a readout', 'deck for the sprint review', 'I need to present these changes', 'use debrief', 'debrief and writeup', 'overview deck of this project', 'explain this platform to managers'. Fits a demo, standup, sprint review, stakeholder update, retro, or a plain overview of what a project is and who it is for. Reads the git diff and the task brief so the deck reports facts, not flattery, then builds the PDF rather than explaining how to. Offer it unprompted after a large multi-file change lands. …
Works with: Claude Code (native) · Cursor, Codex CLI (manual)
native: this artifact type is that client's own format
Install (Claude Code):
cp -r debrief ~/.claude/skills/- tashan score: 53.0
- Adoption: 3 repos
- Upkeep: 99.0
- Freshness: 98.0
- Evidence coverage: 84% of the inputs this score can use — the rest are unknown, and the score is discounted for it
- Health: active
- Contributors: 3
- License: MIT
Security audit
Not scanned yet. We audit npm-published capabilities for known advisories, install-time scripts and permission surface; this one has no npm package we can resolve, or has not reached the queue.
Its own instructions
Its SKILL.md says when not to, shows worked examples and states a limitation.
Read from the capability’s own SKILL.md. This is not a grade and does not compare to the instruction-depth verdict on an MCP server — a skill has no tools to document, so that rubric does not apply to it.
You searched for one. Check the rest of your stack:
npx tashan-cli doctorReads the config already on your machine and names what is dead, deprecated or running code at install time. No account, nothing uploaded.
Debrief scores 53 today. Pro keeps the series, so you can see whether that is a project getting better or one on its way down.
- Every score since we started measuring, for any capability
- The named replacement when something you run is dying — not just that it is
tashan doctorover the config you already have, on your machine
Start a 7-day trial › Everything measured on this page stays free.
Show your score
source ↗ · skill:LucianoAdonis/debrief
Everything on this page is public evidence and free. What it cannot know is whether you run this — check your whole config, free, in the browser. tashan Pro adds the series behind each row and names a replacement for anything dying.
Already running this? Check your whole config — free, in your browser, nothing installed. Or npx tashan-cli doctor locally, which sends nothing at all.
Measured 2026-09-12 · scorer s5 · how · something wrong here?