New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Review Cockpit

by huytieu in huytieu/COG-second-brain

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…

MITAuto-check passed

Install Review Cockpit

skills CLI
$ npx skills add huytieu/COG-second-brain --skill review-cockpit -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install huytieu/COG-second-brain review-cockpit --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/huytieu/COG-second-brain.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/review-cockpit .claude/skills/review-cockpit && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
review-cockpit
GitHub stars
1.3k
Token cost
~1.4k tokens
SKILL.md length
753 words
Files
2 (incl. references)
Skills in repo
37
Repo updated
First seen
Licence
MIT

At a glance

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…

  • Works in 4 steps: Status line — one line: how many items… → 🧭 Progress — a checklist, one row per… → 📁 Working folder — table of every… → …
  • A session has multiple deliverables you need to review/approve (meeting-processing + planning
  • SKILL.md covers Purpose, When to use, The one rule and Structure, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Review Cockpit is an agent skill from huytieu/COG-second-brain. 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…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including reference files (for example `references/session-review-template.md`).

The repository describes itself as: Self-evolving second brain with 35 AI skills, 10 agents, and people CRM. Closed-loop harness: a V-model verification lifecycle where the worker never grades its own homework… The licence is MIT.

When your agent uses it

  • A session has multiple deliverables you need to review/approve (meeting-processing + planning
  • Multi-ticket work
  • Briefs with several drafts
  • Then plan/draft Y and Z)

Example prompts

  • “do X, then plan/draft Y and Z”
  • “/review-cockpit”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  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"…
  3. 📁 Working folder — table of every artifact produced this session with its ~/vault/... path or link (meeting note, this doc, evidence dir…
  4. 🔌 Context — sources the work is grounded in (recordings, Slack threads, issues), tools/connectors used, related tickets.

What it can do on your machine

Read from SKILL.md and the folder at commit 36ac9d7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Review Cockpit loads about 1.4k tokens when it runs, and up to ~1.6k if it reads all its reference files. Until then it costs about 147 tokens; SKILL.md has 753 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~147
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from huytieu/COG-second-brain at commit 36ac9d7, republished under its MIT licence (© huytieu). 753 words, ~1,431 tokens.

Download SKILL.mdSave it as .claude/skills/review-cockpit/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
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

Show full SKILL.md (310 more words)Show less

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.

© huytieu, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in skills/review-cockpit of huytieu/COG-second-brain.

  • SKILL.md
  • references/session-review-template.md

Open the folder on GitHubat commit 36ac9d7

Compare with similar skills

Review Cockpit next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Review Cockpit compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Review Cockpit this skillhuytieu/COG-second-brain1.3k—~1.4kAutomated safety check: PassMIT
Continuetelegramdesktop/tdesktop33k2 repos~9.4kAutomated safety check: PassGPL-3.0
Openclaw Live Updateropenclaw/openclaw392k—~3.7kAutomated safety check: PassMIT
Wiki Maintaineropenclaw/openclaw392k1 repos~462Automated safety check: PassMIT
Continuous Learningaffaan-m/ECC276k—~1.1kAutomated safety check: PassMIT
Continuous Learningaffaan-m/ECC276k—~1.2kAutomated safety check: PassMIT

Similar skills

  • Continue

    telegramdesktop/tdesktop

    Continue autonomous Telegram Desktop development from the shared ai-tdesktop repository.

    33k GitHub starsUsed in 2 repos~9.4k tokens
    Productivity & AutomationAuto-check passed

  • Openclaw Live Updater

    openclaw/openclaw

    Maintain the canonical live OpenClaw main checkout, macOS LaunchAgent-managed Gateway, local macOS app, exact-head main CI, and recurring full release validation.

    392k GitHub stars~3.7k tokensUpdated today
    DevOps & CloudAuto-check passed

  • Wiki Maintainer

    openclaw/openclaw

    Maintain the OpenClaw memory wiki vault with deterministic pages, managed blocks, and source-backed updates.

    392k GitHub starsUsed in 1 repo~462 tokens
    Knowledge ManagementAuto-check passed

  • Continuous Learning

    affaan-m/ECC

    [DEPRECATED - use continuous-learning-v2] Legacy v1 stop-hook skill extractor.

    276k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed

  • Continuous Learning

    affaan-m/ECC

    [OBSOLETO - usar continuous-learning-v2] Extractor de skill por hook Stop v1 heredado.

    276k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed

  • Live Dashboard

    NousResearch/hermes-agent

    Build self-updating dashboards from live sources. An agent skill from NousResearch/hermes-agent.

    252k GitHub stars~2.1k tokensUpdated yesterday
    Auto-check passed

More from huytieu/COG-second-brain

All 37 skills in this repo

  • Voice Baseline

    huytieu/COG-second-brain

    Measure your own writing corpus for the words and sentence shapes you over-use, so an agent writing in your voice stops amplifying your tics into a style.

    1.3k GitHub stars~957 tokensUpdated 9 days ago
    Auto-check passed

  • Daily Journal

    huytieu/COG-second-brain

    A passive daily work journal that Claude keeps FOR you so you never have to write it yourself.

    1.3k GitHub stars~1.3k tokensUpdated 9 days ago
    Auto-check passed

  • Editorial Illustrations

    huytieu/COG-second-brain

    Generate meaning-carrying editorial data-illustrations in the monotykamary / Linear aesthetic (near-black grayscale, Inter display + mono labels, hairline framed figures) with a single coral accent.

    1.3k GitHub stars~2.4k tokensUpdated 9 days ago
    Auto-check passed

  • Loop Engineering

    huytieu/COG-second-brain

    Shared loop-engineering reference for COG skills - the agent loop, deterministic verifiers, termination conditions, in-loop context management, and named patterns.

    1.3k GitHub stars~1.5k tokensUpdated 9 days ago
    Auto-check passed

  • Release Video

    huytieu/COG-second-brain

    Turn a product release (the list of shipped items plus real screen recordings) into a motion recap video and one explained demo per feature, with sound effects tied to on-screen motion and a…

    1.3k GitHub stars~1.7k tokensUpdated 9 days ago
    Auto-check passed

  • Onboarding

    huytieu/COG-second-brain

    Personalize COG for your workflow - creates profile, interests, and watchlist files with guided setup (run this first!)

    1.3k GitHub starsUsed in 1 repo~3.1k tokens
    Auto-check passed

Questions about Review Cockpit

What does Review Cockpit do?

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…. Review Cockpit is an agent skill from huytieu/COG-second-brain. 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.

When should I use Review Cockpit?

Review Cockpit fits situations like: A session has multiple deliverables you need to review/approve (meeting-processing + planning; multi-ticket work; briefs with several drafts; then plan/draft Y and Z).

How do I install Review Cockpit in Claude Code?

Run `npx skills add huytieu/COG-second-brain --skill review-cockpit -a claude-code`. Or copy the skill folder (skills/review-cockpit in huytieu/COG-second-brain) into .claude/skills/review-cockpit in your project. Claude Code loads it when a task matches its description.

How do I install Review Cockpit in Codex?

Run `npx skills add huytieu/COG-second-brain --skill review-cockpit -a codex`. Or copy the skill folder (skills/review-cockpit in huytieu/COG-second-brain) into .agents/skills/review-cockpit in your project. Codex loads it when a task matches its description.

Can I use Review Cockpit in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add huytieu/COG-second-brain --skill review-cockpit -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/review-cockpit, .gemini/skills/review-cockpit, .github/skills/review-cockpit and .opencode/skills/review-cockpit in your project.

What does Review Cockpit need to run?

SKILL.md names no scripts, command-line tools or credentials: Review Cockpit is instructions for the agent only.

Does Review Cockpit access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Review Cockpit safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Review Cockpit use?

Review Cockpit is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Review Cockpit use?

About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 168 tokens, read only when the agent opens those files.

What are the alternatives to Review Cockpit?

Skills that share tags, products or a category with Review Cockpit: Continue (telegramdesktop/tdesktop, 33k stars), Openclaw Live Updater (openclaw/openclaw, 392k stars), Wiki Maintainer (openclaw/openclaw, 392k stars) and Continuous Learning (affaan-m/ECC, 276k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Review Cockpit?

huytieu (a GitHub user) maintains it in huytieu/COG-second-brain, which has 1,268 GitHub stars. The repository holds 37 skills in this directory. The repository was last updated on October 2, 2026.

Source: huytieu/COG-second-brain on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.