Curate
Verify a session's or handoff's factual claims against ground truth before trusting them. Dispatches the read-only `curator` subagent to check claims against git, files, and read-only environment checks, plus the repo's invariants doc if any, and returns a confabulation report for human spot-check. Use at pass boundaries — resuming from a handoff, before a deploy, or whenever a prior session's summary looks suspiciously clean. Triggers on `/curate`, "curate this", "verify these claims", "check the handoff for confabulation", "is this actually done".
Install
npx skills add iamneilroberts/claude-skills --skill curategit clone --depth 1 https://github.com/iamneilroberts/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/skills/curate ~/.claude/skills/curatePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# /curate — confabulation check before you trust a claim
Runs the `curator` subagent (read-only) over a set of claims and returns a verdict report. This is
the in-loop guard against claims that sound done but aren't — fabricated tool results, "prod-ready"
work that only passed local smoke, stale audit claims treated as current.
> Requires the `curator` agent (`agents/curator.md` in this collection) installed to
> `~/.claude/agents/`. The out-of-tree journal lookup in step 1 is optional — it only applies if you
> also use the `branch` skill; otherwise that bullet is skipped.
## Steps
1. **Determine the target** (in priority order):
- An explicit argument — a file path, or a claim/list of claims the user pasted → use it.
- Else the newest `docs/summaries/pause-*.md` under the repo root (`git rev-parse --show-toplevel`).
- Else the `## Active` entry for this session in the shared out-of-tree journal at
`$(bash ~/.claude/coordination/resolve-coord-dir.sh)/journal.md` (the in-tree
`docs/worktree-journal.md` is a tombstone — do not read it).
- Else this session's own stated accomplishments since the last checkpoint.
If you can't find a target, ask the user what to curate — don't curate nothing.
2. **Dispatch the curator.** Call the Agent tool with `subagent_type: curator`, passing the target
(the file path, or the extracted claims verbatim). The curator reads the repo's invariants docDetails
- Skill name
curate- Repository
- iamneilroberts/claude-skills
- Path
skills/curate/SKILL.md- Repo updated
- 21 August 2026
FAQ
What does the Curate skill do?
Verify a session's or handoff's factual claims against ground truth before trusting them. Dispatches the read-only `curator` subagent to check claims against git, files, and read-only environment checks, plus the repo's invariants doc if any, and returns a confabulation report for human spot-check. Use at pass boundaries — resuming from a handoff, before a deploy, or whenever a prior session's summary looks suspiciously clean. Triggers on `/curate`, "curate this", "verify these claims", "check the handoff for confabulation", "is this actually done".
How do I install the Curate skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add iamneilroberts/claude-skills --skill curate. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Curate popular?
It lives in iamneilroberts/claude-skills, which has 37 GitHub stars and 7 forks.
Related skills
Brag
37iamneilroberts/claude-skills
Memorialize something you just built by generating a self-contained "showcase" page for it — a persuasive, good-looking deep dive: what it is, why it's impressive, how it works — with a screenshot if one can be found or captured, and links to related showcase pages. This is the sales/hype-leaning counterpart to /write-post (which drafts a neutral, no-BS technical post); reach for /brag when you want it to sell. Fast by design, like /idea: ask only what's needed, build the page, don't turn it into a project. Triggers on `/brag <subject>`, "brag about this", "make a showcase page for X", "write
Branch
37iamneilroberts/claude-skills
Create an isolated git worktree for a task and log it to a shared work journal, so multiple Claude Code sessions run in parallel without racing on HEAD, uncommitted edits, or the index. Subcommands: `list`, `done <slug>`, `update` (heartbeat), `coord <message>` / `coord clear <slug>` (cross-session constraints). Triggers on `/branch`, "start in a worktree", "isolate this work", "parallel session", "heartbeat the journal".
Claude Code Best Practices
37iamneilroberts/claude-skills
Use when asked about Claude Code workflow, prompt caching cost, session economics, CLAUDE.md hygiene, context-window management, plan mode, permission modes, hooks, skills, subagents, checkpointing/rewind, parallel sessions, worktrees, headless/CI usage, the Agent SDK, slash commands, MCP configuration, or "what's the right way to use Claude Code for X". Also use proactively BEFORE suggesting /model, /compact, fast-mode toggle, or editing CLAUDE.md mid-session, since those bust the system cache.
Fix Issue
37iamneilroberts/claude-skills
Take a GitHub issue and actually resolve it end to end — read the issue, reproduce it, fix it in an isolated branch with a test, verify, and open a PR that closes the issue. The counterpart to /idea (which files issues): /idea captures, /fix-issue clears. Works off `gh` in whatever repo you're in. Triggers on `/fix-issue <number|url>`, "fix issue #N", "resolve this github issue", "pick up and fix issue N".
Github Review
37iamneilroberts/claude-skills
Review a GitHub pull request — the PR-review behavior that used to live in the built-in `/review`, split out now that `/review` is the review orchestrator. Fetches the PR with `gh`, reviews the diff at an evidence-graded bar (only a fully-traced finding is blocking), and optionally posts inline PR comments. For your uncommitted working diff use `/review` instead; this command is specifically for a PR. Triggers on `/github-review`, `/github-review <pr>`, "review this pull request", "review PR #N".
Share Case
43NeuroAIHub/awesome_cognitive_and_neuroscience_skills
One-command community case sharing — capture research context from your session and submit to GitHub Discussions
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.