SkillAgentSearch skills...

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

Install / Use

npx skills add huytieu/COG-second-brain --skill review-cockpit

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

82/100

Supported Platforms

Universal

Our assessment of review-cockpit

review-cockpit scores 82/100 on our quality scale, 974th of 1,153 Content & Media skills we index.

Its SKILL.md is 5.6 KB long, well organised into 9 sections and no code examples: a solid amount of guidance for an agent.

With 1,216 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so review-cockpit is actively maintained.
  • Our last check on 2026-11-07 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-03. Automated pattern scan on 2026-10-03. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

review-cockpit compared with similar skills

All 4 of these similar skills score higher than review-cockpit; compare them before choosing.

SkillScoreStarsUpdatedFormat
review-cockpit (this skill)by huytieu821.2k59d agoSKILL.md
siyuanby siyuan-note10047.3ktodayMCP Server
x402by browser-use100121.0k3d agoSKILL.md
algorithmic-artby anthropics100177.9k55d agoSKILL.md
pptxby anthropics100177.9k55d agoSKILL.md

Frequently asked questions

How do I install review-cockpit?
Run npx skills add huytieu/COG-second-brain --skill review-cockpit. The install tabs above show the steps for each supported agent.
Which AI agents does review-cockpit work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is review-cockpit safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is review-cockpit still maintained?
The repository was last updated about 2 months ago, so review-cockpit is actively maintained.

name: review-cockpit description: 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. Use whenever a session has multiple deliverables you need to review/approve (meeting-processing + planning, multi-ticket work, briefs with several drafts, any "do X, then plan/draft Y and Z"). The doc is the interaction surface: you edit it (or reply in chat) to approve/change; the agent keeps it live as work progresses.

review-cockpit

Purpose

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).

When to use

  • Any session with ≥2 things you need to review or approve (the default for "process X then plan/draft Y, Z").
  • Meeting-processing + pod planning, multi-ticket runs, briefs with several drafts, spec + plan + drafts.
  • NOT for a single trivial deliverable (one file, no approval loop) — a plain file is fine there.

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.

The one rule

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.

Structure

Copy references/session-review-template.md. Save the working copy in the relevant project folder as YYYY-MM-DD-<slug>-review.md (or -plan.md).

Cockpit (top):

  1. Status line — one line: how many items await review + last-updated timestamp.
  2. 🧭 Progress — a checklist, one row per item, each with a status glyph; a text progress bar + "X/N done · A awaiting review · B pending". Make each item a clickable anchor to its review card — [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.
  3. 📁 Working folder — table of every artifact produced this session with its ~/vault/... path or link (meeting note, this doc, evidence dir, external issues/PRs, posted messages).
  4. 🔌 Context — sources the work is grounded in (recordings, Slack threads, issues), tools/connectors used, related tickets.

Review items (below): one card per item:

  • Status — glyph + word (see vocabulary).
  • Action — what was done or is proposed.
  • Deliverable — link/path, or an inline draft placed directly under the card so you review it in place (messages to send, doc bodies).
  • Checklist — the item's acceptance criteria as checkboxes.
  • 🗒 Your call — the approval slot you edit (approve / your requested changes).
  • Decision log — append-only record of what happened / what you decided.

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

Update protocol (keep it live)

  • After every meaningful step, refresh: the Progress checklist + bar, the affected item's Status, the Working folder (add new artifacts), and the item's Decision log. Bump the updated: frontmatter + status line.
  • Prefer targeted Edits over full rewrites so your inline edits/approvals are never clobbered. Before editing, re-read the file — you may have typed approvals or change requests into 🗒 Your call or ticked boxes.
  • When you approve an item, execute it, move it to ✅, and log the outcome (with the external link — issue/PR/message URL) in the Decision log.
  • When you request changes, set the item to ✏️ changes requested, apply them, re-draft in place, then return it to 📝 needs review.

Interaction contract

The doc is the shared surface; you drive it two ways, both valid:

  • In the doc / side panel: you edit 🗒 Your call or tick checkboxes. Re-read and act.
  • In chat: "3 is ok", "approve 2 and 4", "change the tone on the requirement comms". Map to item numbers and act.

Distinguish draft items (agent proposes, waits — e.g. a Slack message you own sending) from auto items (agent may execute directly — e.g. filing a GitHub issue you explicitly asked for). Draft items stay 📝 until approved; auto items go straight to ✅ with the artifact linked. When unsure whether an item is draft or auto, leave it 📝.

Post-condition

Read-only for the doc itself, but the items it tracks often mutate external state — obey each item's own post-condition (fetch back the issue, confirm the Slack message landed, etc.) and record the verified link in the Decision log. Never mark ✅ from a mutation call alone.

Optional: rendered view

The markdown doc is primary (you edit it to approve). If you want a richer at-a-glance view, additionally render an HTML Artifact of the cockpit (Progress + Working folder + Context + item statuses) — but the markdown stays the source of truth and the editable surface.

Related Skills

View on GitHub
GitHub Stars1.2k
CategoryContent
Updated1mo ago
Forks144

Languages

HTML

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions