Show Me Your Work Decision Log
cursor/plugins
Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.
A skill your agent uses when reviewing a conformance PR that adds or changes scenario .ts files for a SEP — before approving, before requesting changes, or as a self-check before opening one.
Install Review Scenario
$ npx skills add modelcontextprotocol/conformance --skill review-scenario -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install modelcontextprotocol/conformance review-scenario --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/modelcontextprotocol/conformance.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/review-scenario .claude/skills/review-scenario && rm -rf skills-srcUse ~/.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/
Install the "review-scenario" agent skill from https://github.com/modelcontextprotocol/conformance/tree/main/.claude/skills/review-scenario into .claude/skills/review-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-scenario", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/modelcontextprotocol/conformance/tree/main/.claude/skills/review-scenarioType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add modelcontextprotocol/conformance --skill review-scenario -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install modelcontextprotocol/conformance review-scenario --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modelcontextprotocol/conformance.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/review-scenario .agents/skills/review-scenario && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "review-scenario" agent skill from https://github.com/modelcontextprotocol/conformance/tree/main/.claude/skills/review-scenario into .agents/skills/review-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-scenario", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add modelcontextprotocol/conformance --skill review-scenario -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install modelcontextprotocol/conformance review-scenario --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modelcontextprotocol/conformance.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/review-scenario .cursor/skills/review-scenario && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "review-scenario" agent skill from https://github.com/modelcontextprotocol/conformance/tree/main/.claude/skills/review-scenario into .cursor/skills/review-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-scenario", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/modelcontextprotocol/conformance.git --path .claude/skills/review-scenario--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add modelcontextprotocol/conformance --skill review-scenario -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install modelcontextprotocol/conformance review-scenario --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modelcontextprotocol/conformance.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/review-scenario .gemini/skills/review-scenario && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "review-scenario" agent skill from https://github.com/modelcontextprotocol/conformance/tree/main/.claude/skills/review-scenario into .gemini/skills/review-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-scenario", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install modelcontextprotocol/conformance review-scenarioInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add modelcontextprotocol/conformance --skill review-scenario -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/modelcontextprotocol/conformance.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/review-scenario .github/skills/review-scenario && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "review-scenario" agent skill from https://github.com/modelcontextprotocol/conformance/tree/main/.claude/skills/review-scenario into .github/skills/review-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-scenario", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add modelcontextprotocol/conformance --skill review-scenario -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install modelcontextprotocol/conformance review-scenario --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/modelcontextprotocol/conformance.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/review-scenario .opencode/skills/review-scenario && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "review-scenario" agent skill from https://github.com/modelcontextprotocol/conformance/tree/main/.claude/skills/review-scenario into .opencode/skills/review-scenario/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "review-scenario", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
review-scenario- GitHub stars
- 129
- Token cost
- ~983 tokens
- SKILL.md length
- 474 words
- Files
- 1
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when reviewing a conformance PR that adds or changes scenario .ts files for a SEP — before approving, before requesting changes, or as a self-check before opening one.
- Reviewing a conformance PR that adds
- SKILL.md covers What to check and Output
- Calls gh and npx; reaches pkg.pr.new
- Changes scenario .ts files for a SEP — before approving
What it does
Review Scenario is an agent skill from modelcontextprotocol/conformance, published by the product's own GitHub organization. Use when reviewing a conformance PR that adds or changes scenario .ts files for a SEP — before approving, before requesting changes, or as a self-check before opening one.
Its SKILL.md is about 980 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Verification before completion. The repository describes itself as: Conformance Tests for MCP.
When your agent uses it
- Reviewing a conformance PR that adds
- Changes scenario .ts files for a SEP — before approving
- Before requesting changes
- As a self-check before opening one
Example prompts
- “/review-scenario”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit c37eec8. 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
Shell commands in SKILL.md call:
ghnpx
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
pkg.pr.new
Also links to:
modelcontextprotocol.io
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 Scenario loads about 983 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 474 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 474 words (~983 tokens).
“Spec diff is ground truth. Pull the SEP's actual spec changes and read the RFC-2119 sentences yourself — don't trust the PR description or SEP summary for keyword levels:”
- name
- review-scenario
Files
Just SKILL.md in .claude/skills/review-scenario of modelcontextprotocol/conformance.
Open the folder on GitHubat commit c37eec8
Compare with similar skills
Review Scenario 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Review Scenario this skillmodelcontextprotocol/conformance | 129 | — | ~983 | Automated safety check: Pass | Custom licence | |
| Show Me Your Work Decision Logcursor/plugins | 10k | 9 repos | ~1.6k | Automated safety check: Pass | None | |
| Verification Before Completionfarm-fe/farm | 5.6k | 45 repos | ~1k | Automated safety check: Pass | MIT | |
| Scope Creep Guardlennney/stop-that-shit | 2.5k | 1 repos | ~2k | Automated safety check: Pass | MIT | |
| PUA High-Agency Governancetanweai/pua | 20k | — | ~502 | Automated safety check: Pass | MIT | |
| Incremental Implementationaddyosmani/agent-skills | 102k | 1 repos | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Verification Before Completion
farm-fe/farm
A skill your agent uses when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any…
Scope Creep Guard
lennney/stop-that-shit
Keeps an agent focused on the requested work by applying a five-step ladder that checks for direct solutions, real gaps and speculative defenses before adding anything.
PUA High-Agency Governance
tanweai/pua
Pushes an agent to keep verifying and changing approach after repeated failures, using a diagnosis line, evidence-based completion and confirmation before risky edits.
Incremental Implementation
addyosmani/agent-skills
Delivers a change in thin vertical slices, each implemented, tested, verified and committed before the next, using vertical, contract-first or risk-first slicing.
PUA Loop
tanweai/pua
Runs an unattended iterate-until-verified loop in which a user-set verify command, not the agent's own claim, decides when the task is finished.
More from modelcontextprotocol/conformance
- Official
MCP SDK Tier Audit
modelcontextprotocol/conformance
Comprehensive tier assessment for an MCP SDK repository against SEP-1730.
- Official
New Sep
modelcontextprotocol/conformance
Scaffold a sep-NNNN.yaml requirement-traceability file for the MCP conformance repo from a SEP PR's spec diff.
Related
Categories
Questions about Review Scenario
What does Review Scenario do?
A skill your agent uses when reviewing a conformance PR that adds or changes scenario .ts files for a SEP — before approving, before requesting changes, or as a self-check before opening one. Review Scenario is an agent skill from modelcontextprotocol/conformance, published by the product's own GitHub organization.ts files for a SEP — before approving, before requesting changes, or as a self-check before opening one.
When should I use Review Scenario?
Review Scenario fits situations like: reviewing a conformance PR that adds; changes scenario .ts files for a SEP — before approving; before requesting changes; as a self-check before opening one.
How do I install Review Scenario in Claude Code?
Run `npx skills add modelcontextprotocol/conformance --skill review-scenario -a claude-code`. Or copy the skill folder (.claude/skills/review-scenario in modelcontextprotocol/conformance) into .claude/skills/review-scenario in your project. Claude Code loads it when a task matches its description.
How do I install Review Scenario in Codex?
Run `npx skills add modelcontextprotocol/conformance --skill review-scenario -a codex`. Or copy the skill folder (.claude/skills/review-scenario in modelcontextprotocol/conformance) into .agents/skills/review-scenario in your project. Codex loads it when a task matches its description.
Can I use Review Scenario 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 modelcontextprotocol/conformance --skill review-scenario -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-scenario, .gemini/skills/review-scenario, .github/skills/review-scenario and .opencode/skills/review-scenario in your project.
What does Review Scenario need to run?
Going by SKILL.md and its folder, Review Scenario needs the command-line tools its instructions call (gh and npx). Our summary lists: Node.js.
Does Review Scenario access the network?
SKILL.md names 2 domains. In commands or code: pkg.pr.new; the agent is likely to contact it when it follows the instructions. As links in the text: modelcontextprotocol.io. This is read from the text; nothing was executed.
Is Review Scenario 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 Scenario use?
Review Scenario has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Review Scenario use?
About 983 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Review Scenario?
Skills that share tags, products or a category with Review Scenario: Show Me Your Work Decision Log (cursor/plugins, 10k stars), Verification Before Completion (farm-fe/farm, 5.6k stars), Scope Creep Guard (lennney/stop-that-shit, 2.5k stars) and PUA High-Agency Governance (tanweai/pua, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Review Scenario?
modelcontextprotocol (a GitHub organization, an official publisher) maintains it in modelcontextprotocol/conformance, which has 129 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 5, 2026.
Source: modelcontextprotocol/conformance on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.