review-sessions SKILL.md skillA
This file is byte-identical to the first copy the registry indexed, one of 4 indexed copies. Same content hash, so the same checks give both the same grade.
review-sessions from phmatray/tagout is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add phmatray/tagout/review-sessions@git:20261028.00b3111Pins git:20261028.00b3111 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- phmatray/tagout
- Path
plugins/tagout/skills/review-sessions/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261028.00b3111, committed Oct 28, 2026
- First version recorded
- Sep 15, 2026
- Size
- 15,895 bytes
- Repository stars
- 4
- License
- MIT
Read the transcripts of PREVIOUS sessions and pull out the failures the kit itself caused — errors on kit scripts, gate denials, workers that died waiting, red kit suites — then cluster them by root cause, drop what main already fixed, and file what earns an issue through create-issue. Use when the user asks what went wrong in past runs: "review my previous sessions", "what went wrong in my last runs", "learn from the transcripts", « analyse mes sessions précédentes », « qu'est-ce qui a foiré…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Review the sessions — the kit's own failures, out of the transcripts ## What this does Every session Claude Code runs leaves a transcript under `~/.claude/projects/<encoded-cwd>/`, and the kit's failures are written into it in fixed shapes: a `tool_result` flagged `is_error` on a kit script, a hook's deny reason, a worker's final `STATUS: BLOCKED` line, an assistant turn that ends on *"I'll pause here and wait for"*, the harness's *no visible output* nudge. Until this skill, a human read those by hand — every defect the kit fixed in 2026-08 was found that way, days after the evidence had been on disk. This skill reads them mechanically and judges them deliberately: 1. **Harvest** — [`scripts/harvest.py`](scripts/harvest.py) walks the transcripts (top-level sessions and every sub-agent layout) and emits one record per signal, attributed to the kit skill active at that point. Deterministic, read-only, pinned by `tests/review-sessions/test.sh`. 2. **Cluster** — records become clusters by root cause, each tagged with a category from [`../auto-dev/references/retro-taxonomy.md`](../auto-dev/references/retro-taxonomy.md). …
Read the whole file at its exact version.
How to install
mdr add phmatray/tagout/review-sessions@sha256:c3d88af73c740861The line at the top of this page pins the label git:20261028.00b3111, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_eznlp5rymszt7wnq)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Sep 15, 2026 and Oct 28, 2026, about one every 11 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261028.00b3111 latest | 2026-10-28 | 00b3111 | 15,895 B | A | view · diff |
| git:20261028.7589fac | 2026-10-28 | 7589fac | 15,396 B | A | view · diff |
| git:20261028.b4e7f54 | 2026-10-28 | b4e7f54 | 15,202 B | A | view · diff |
| git:20261010.9485205 | 2026-10-10 | 9485205 | 14,258 B | A | view · diff |
| git:20260915.96b4731 | 2026-09-15 | 96b4731 | 14,266 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (15895 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
phmatray/tagout · 4 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_eznlp5rymszt7wnq GET https://markdownregistry.com/api/v1/resolve?ref=phmatray/tagout/review-sessions GET https://markdownregistry.com/api/v1/blob/c3d88af73c740861af3db1914a141ecc7dd3415cecc68f112bc7d68a13fd8a94
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.