Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →huytieu/review-cockpit
Produce and continuously maintain ONE living review document for a multi-item session — a cockpit header (Progress checklist, Working folder, Context) plus per-item review cards that you approve or request changes on directly in the doc or side panel.
Passed 15 of 21 test cases with the skill, and 3 of 21 without it.
and 25 more in the full report
14 fixed2 passed either way5 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
We have a review card for a Slack notification message that needs user approval before sending. Where should the draft text be placed within the review card structure?
| Checked | Without skill | With skill |
|---|---|---|
| Place the draft text directly under the Deliverable section of the review card | Missed | Passed |
| Include an acceptance criteria Checklist with checkboxes on the card | Missed | Passed |
The instructions your model reads when the skill loads.
A single, living review document that doubles as the control surface for a session. Instead of scattering a meeting note here, a ticket there, two drafts in chat, everything lands in one file you can open in the Obsidian side panel (or Claude side panel) and drive: see progress at a glance, review each item in place, approve or request changes inline, and watch the doc update as the agent works. Mirrors a "co-work" cockpit (Progress / Working folder / Context).
Pairs with closed-loop (verification), harvest (learnings), and the V-model checkpoints. This skill governs how the deliverable is presented and driven, not the verification pipeline.
One doc per session. It opens with a cockpit, then one review card per item. Every artifact the session produces is linked from the Working folder table (fan-out to sub-files mid-run is fine; the cockpit is the single front door). Never hand the user "see files A, B, C" — hand them the cockpit.
Copy 04-projects/harness/templates/session-review.md. Save the working copy in the relevant project folder as YYYY-MM-DD-<slug>-review.md (or -plan.md).
Cockpit (top):
[N. Title](#n-title) using GitHub-slug rules (lowercase, spaces→-, drop punctuation/emoji). Keep item headings free of + # ← → ( ) so slugs stay clean single-hyphen and the links resolve in Obsidian + the Claude side panel.~/vault/... path or link (meeting note, this doc, evidence dir, external issues/PRs, posted messages).Review items (below): one card per item:
approve / your requested changes).Footer: "How to drive this doc" (approve/change mechanics + status vocabulary), so the doc is self-explaining.
Status vocabulary: ⏳ pending · 🔄 in progress · 📝 needs review · ✏️ changes requested · ✅ done · ⛔ blocked
test cases passed, vs 3 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.