Automated summary

Walks the full queue of pending unconfirmed memories or pending revisions in the Origin plugin one item at a time, letting you accept, edit, or reject each.

Strengths

Covers every item with no cap, unlike /brief which only shows the top 3
Offers three clear actions per item: accept, edit (via supersedes then forget), or reject
Makes no LLM calls and stays read-only until you confirm, so it is cheap
Two explicit scopes: /review captures and /review revisions

Limitations

Depends on the Origin plugin and its dedicated MCP tools to work
A bare /review invocation only prints help and does not start any walk
Overlaps with /brief for daily work, which can confuse regular users

When to use it

Use it after a bulk import (ChatGPT, Obsidian dump) or when you need to clear a revision queue larger than the 3 items /brief surfaces.

When not to use it

Avoid it for daily session work or a specific factual lookup, where /brief and /recall are the better fit.

Security analysis

Safe

Quality score82/100

The skill only orchestrates Origin's own MCP memory tools (list, capture, confirm, forget, accept/dismiss revision). There are no shell invocations, network fetches, credential handling, or obfuscated payloads. Destructive-looking operations (forget) are scoped to explicit user-driven review of pending items and are described transparently, so execution risk is minimal.

No concerns found

How this analysis is made

Examples

Audit after bulk import

/review captures — I just imported a big Obsidian dump, walk me through every unconfirmed memory one by one so I can accept or reject each.

Clear the revision queue

/review revisions — /brief says there are more than 3 pending revisions, let's walk the whole queue.

name: review description: > Power-user audit of Origin's pending surfaces. Most users want `/brief` for revisions. That handles the daily flow. Use `/review` only for explicit deep-walk audits after bulk imports, or when you want to walk the full queue rather than the top 3 shown in /brief. Invoked as `/review captures` or `/review revisions`. argument-hint: "captures | revisions" allowed-tools: ["mcp__plugin_origin_origin__list_pending", "mcp__plugin_origin_origin__list_pending_revisions", "mcp__plugin_origin_origin__confirm_memory", "mcp__plugin_origin_originforget", "mcpplugin_origin_origincapture", "mcpplugin_origin_origin__accept_revision", "mcp__plugin_origin_origin__dismiss_revision"]

/review

Name: Deep Audit of Pending Items
Author: Skills Guide Bot

Power-user audit lever. Most users do not need /review in daily flow:

Pending revisions surface in /brief automatically (top 3 with inline accept/dismiss).
Pending captures from this session surface in /handoff's preview block (top 3, informational). Use /review captures for the deep walk.
Orphan wikilinks surface in /distill's topic-suggestion block.

Use /review only when you want the deep walk those skills intentionally do not force.

Scoped invocation

/review captures: walk every unconfirmed memory (list_pending, unfiltered by session). Per item: accept (confirm_memory), edit (capture with supersedes=<old_id> then forget(old_id)), or reject (forget).
/review revisions: walk every pending revision (list_pending_revisions, no cap). Per item: accept (accept_revision), dismiss (dismiss_revision), or skip.

Bare /review (no arg) prints this help block and exits. Does not auto-walk.

When to use

After a bulk import (ChatGPT, Obsidian dump) when you want to audit every auto-classification before sealing.
When /brief shows ">3 pending revisions" and you want to clear the full queue, not just the top 3.

When NOT to use

Daily session work. /brief handles the surface that matters today.
Specific factual lookup: use /recall.
Searching for facts: use /recall.

Cost

Read-only until the user confirms or rejects. No LLM calls. Cheap.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/deep-audit-of-pending-items-ms1aw4bn/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/deep-audit-of-pending-items-ms1aw4bn' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/deep-audit-of-pending-items-ms1aw4bn/download' --output '.skill-downloads/deep-audit-of-pending-items-ms1aw4bn/SKILL.md.part' && mv '.skill-downloads/deep-audit-of-pending-items-ms1aw4bn/SKILL.md.part' '.skill-downloads/deep-audit-of-pending-items-ms1aw4bn/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/deep-audit-of-pending-items-ms1aw4bn/SKILL.md' && test -s '.skill-downloads/deep-audit-of-pending-items-ms1aw4bn/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/review' && cp -R '.skill-downloads/deep-audit-of-pending-items-ms1aw4bn' '.claude/skills/review'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/deep-audit-of-pending-items-ms1aw4bn'

openskills read 'deep-audit-of-pending-items-ms1aw4bn'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/deep-audit-of-pending-items-ms1aw4bn/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.

Related skills

PDF Reader

Productivity

Read and extract text from PDF files, including documents, reports, contracts, and spreadsheets. Works with local files, URLs, and WhatsApp attachments. Use whenever PDF content is needed, even if not explicitly requested.

Claude CodeCursorCodexbeginnerSafe 20,122

Skills Guide Bot