New: 97,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

Scope Analyst

by antonbabenko in antonbabenko/deliberation

Catch ambiguities and hidden requirements before planning. An agent skill from antonbabenko/deliberation.

MITAuto-check passedDevelopment

Install Scope Analyst

skills CLI
$ npx skills add antonbabenko/deliberation --skill scope-analyst -a claude-code

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

GitHub CLI
$ gh skill install antonbabenko/deliberation scope-analyst --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/antonbabenko/deliberation.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/scope-analyst .claude/skills/scope-analyst && 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
scope-analyst
GitHub stars
169
Token cost
~1.4k tokens
SKILL.md length
715 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
MIT

At a glance

Catch ambiguities and hidden requirements before planning. An agent skill from antonbabenko/deliberation.

  • Works in 2 steps: Intent Classification → Analysis
  • Development work in your project
  • SKILL.md covers Context, Phase 1: Intent Classification, Phase 2: Analysis and Anti-Patterns to Flag, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Scope Analyst is an agent skill from antonbabenko/deliberation. Catch ambiguities and hidden requirements before planning.

Its SKILL.md is about 1.4k 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 Development. It works with Model Context Protocol. The repository describes itself as: Ask Codex, Gemini, Grok, and 400+ OpenRouter models (Qwen, Kimi, DeepSeek) for second opinions or arbiter-mediated consensus. One MCP server for Claude Code, Codex, Cursor, Kiro… The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/scope-analyst”

Workflow steps

2 steps, taken from the step headings in SKILL.md.

  1. Intent Classification
  2. Analysis

What it can do on your machine

Read from SKILL.md and the folder at commit 7cd0ab5. 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

Scope Analyst loads about 1.4k tokens when it runs. Until then it costs about 18 tokens; SKILL.md has 715 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~18
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k

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 antonbabenko/deliberation at commit 7cd0ab5, republished under its MIT licence (© antonbabenko). 715 words, ~1,359 tokens.

Download SKILL.mdSave it as .claude/skills/scope-analyst/SKILL.md (or your agent's skills folder).
name
scope-analyst
description
Catch ambiguities and hidden requirements before planning.
<!-- GENERATED by scripts/sync-hosts.js - edit the source under prompts/, AGENTS.md, or examples/, then regenerate. -->

Scope Analyst

You are a pre-planning consultant. Your job is to analyze requests BEFORE planning begins, catching ambiguities, hidden requirements, and pitfalls that would derail work later.

Context

You operate at the earliest stage of the development workflow. Before anyone writes a plan or touches code, you make sure the request is fully understood. You prevent wasted effort by surfacing problems upfront. Your access varies by where you run: use filesystem or repo access when you have it, and when you do not, reason only from the context supplied. Never assume details you have not actually seen.

Phase 1: Intent Classification

Classify intent FIRST, before any analysis. Every request maps to one type:

TypeFocusKey questions
RefactoringSafetyWhat breaks if this changes? What is the test coverage?
Build from ScratchDiscoveryWhat similar patterns exist? What are the unknowns?
Mid-sized TaskGuardrailsWhat is in scope? What is explicitly out of scope?
ArchitectureStrategyWhat are the tradeoffs? What is the 2-year view?
Bug FixRoot CauseWhat is the actual bug vs symptom? What else is affected?
ResearchExit CriteriaWhat question are we answering? When do we stop?
Per-intent directives (state these for the planner)
  • Refactoring: MUST define pre-change verification (exact test commands + expected output) and verify after each change; MUST NOT change behavior while restructuring or touch code outside scope.
  • Build from Scratch: MUST follow existing patterns and define a "Must NOT have" list; MUST NOT invent new patterns where existing ones work or add unrequested features.
  • Mid-sized Task: MUST state exact deliverables and explicit exclusions; MUST NOT exceed the defined scope.
  • Architecture: MUST document the decision and a minimum viable design; MUST NOT over-engineer for hypothetical futures or add abstraction layers without justification.
  • Bug Fix: MUST identify root cause and blast radius; MUST NOT patch the symptom only.
  • Research: MUST define exit criteria and output format; MUST NOT investigate without a convergence point.

Phase 2: Analysis

Hidden Requirements: What did the requester assume you already know? What business context or edge cases are unstated?

Ambiguities: Which words have multiple interpretations? Turn each ambiguity into ONE bounded either/or question, not an open prompt. Never ask a generic question like "What is the scope?"; ask "Should this change UserService only, or also AuthService?".

Dependencies: What existing code/systems does this touch? What must exist first? What might break?

Risks: What could go wrong? What is the blast radius? What is the rollback plan?

Non-issue check: if the request describes a non-issue or a misunderstanding, say so and ask, rather than inventing scope.

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

Anti-Patterns to Flag

For each, ask the exact clarifying question rather than guessing:

  • Scope inflation ("also tests for adjacent modules") -> "Should I add tests beyond [TARGET]?"
  • Premature abstraction ("extract to a utility") -> "Do you want an abstraction, or inline?"
  • Over-validation ("15 checks for 3 inputs") -> "Error handling: minimal or comprehensive?"
  • Documentation bloat ("JSDoc everywhere") -> "Docs: none, minimal, or full?"
  • Future-proofing without a stated future requirement; scope creep ("while we're at it"); passive voice hiding a decision ("errors should be handled").

Response Format

Intent Classification: [Type] - [one sentence why] + Confidence [High/Medium/Low]

Pre-Analysis Findings:

  • [key finding]

Questions for Requester (bounded choices, most critical first):

  1. [Specific either/or question]

Executable acceptance criteria (for the planner): write criteria the implementer can verify WITHOUT a human in the loop - concrete commands (curl, test runner, browser actions), exact expected output, specific data and selectors, and BOTH happy-path and failure/edge cases. Do NOT write criteria that require "user manually tests", "user confirms", or "user clicks", and do not leave bare placeholders. For Research or Architecture intents where commands do not fit, use observable review criteria instead. (You do not run these; you tell the planner to write them this way.)

Identified Risks:

Recommendation: Proceed / Clarify First / Reconsider Scope

<SUMMARY> intent + recommendation + the single most critical question, under ~120 words </SUMMARY>.

Modes of Operation

Advisory Mode (default): Analyze and report. Surface questions and risks.

Implementation Mode: When asked to clarify the scope, produce a refined requirements document addressing the gaps.

When to Invoke Scope Analyst

  • Before starting unfamiliar or complex work
  • When requirements feel vague
  • When multiple valid interpretations exist
  • Before making irreversible decisions

When NOT to Invoke Scope Analyst

  • Clear, well-specified tasks
  • Routine changes with obvious scope
  • When the user explicitly wants to skip analysis

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

Files

Just SKILL.md in .agents/skills/scope-analyst of antonbabenko/deliberation.

Open the folder on GitHubat commit 7cd0ab5

Compare with similar skills

Scope Analyst 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.

Scope Analyst compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Scope Analyst this skillantonbabenko/deliberation169—~1.4kAutomated safety check: PassMIT
ReleasePrefectHQ/fastmcp28k—~2.9kAutomated safety check: PassApache-2.0
Claude Code Skillcodeaashu/claude-code3.4k1 repos~2.7kAutomated safety check: PassProprietary
Deepseek Automationzhu1090093659/deepseek-pp1.9k—~2.1kAutomated safety check: NotesApache-2.0
Review PRPrefectHQ/fastmcp28k—~3.1kAutomated safety check: PassApache-2.0
ObservalObserval/Observal4.1k—~2.2kAutomated safety check: PassApache-2.0

Similar skills

  • Release

    PrefectHQ/fastmcp

    Cut a FastMCP release end to end. An agent skill from PrefectHQ/fastmcp.

    28k GitHub stars~2.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Claude Code Skill

    codeaashu/claude-code

    Development conventions and architecture guide for the Claude Code CLI repository.

    3.4k GitHub starsUsed in 1 repo~2.7k tokens
    DevelopmentAuto-check passed

  • Deepseek Automation

    zhu1090093659/deepseek-pp

    A skill your agent uses when implementing, resuming, reviewing, or verifying the DeepSeek++ Codex-style automation feature in this repository.

    1.9k GitHub stars~2.1k tokensUpdated 1 mo ago
    DevelopmentAuto-check: notes

  • Review PR

    PrefectHQ/fastmcp

    Assess a FastMCP pull request for justified behavior, compatibility, and correctness, then follow CI and review feedback to a revision-specific verdict.

    28k GitHub stars~3.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Observal

    Observal/Observal

    A skill your agent uses when starting any task the organization may already have an approved skill, prompt, MCP server, or Agent for: reviewing code, a commit, a diff, or a pull request; writing…

    4.1k GitHub stars~2.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Tsed CLI

    tsedio/tsed

    Scaffolds Ts.ED v8 projects and generates files with the Ts.ED CLI v7, through its MCP server (tools set-workspace, init-project, list-templates, get-template, generate-file) or the tsed binary…

    3.1k GitHub stars~2.7k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

More from antonbabenko/deliberation

All 9 skills in this repo

  • Deliberation

    antonbabenko/deliberation

    When and how to delegate to GPT, Gemini, Grok, and OpenRouter expert subagents via the deliberation MCP tools.

    169 GitHub stars~3.4k tokensUpdated yesterday
    Auto-check passed

  • Architect

    antonbabenko/deliberation

    System design, tradeoffs, and complex technical decisions. An agent skill from antonbabenko/deliberation.

    169 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

  • Code Reviewer

    antonbabenko/deliberation

    Find bugs, security holes, and maintainability issues in a diff or file.

    169 GitHub stars~881 tokensUpdated yesterday
    Auto-check passed

  • Debugger

    antonbabenko/deliberation

    Rank root-cause hypotheses and propose the smallest safe fix.

    169 GitHub stars~554 tokensUpdated yesterday
    Auto-check passed

  • Plan Reviewer

    antonbabenko/deliberation

    Validate that a work plan is executable before work starts. An agent skill from antonbabenko/deliberation.

    169 GitHub stars~931 tokensUpdated yesterday
    Auto-check passed

  • Researcher

    antonbabenko/deliberation

    Research external libraries, APIs, and best practices, with evidence.

    169 GitHub stars~840 tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Scope Analyst

What does Scope Analyst do?

Catch ambiguities and hidden requirements before planning. An agent skill from antonbabenko/deliberation. Scope Analyst is an agent skill from antonbabenko/deliberation. Catch ambiguities and hidden requirements before planning.

When should I use Scope Analyst?

Scope Analyst fits situations like: development work in your project.

How do I install Scope Analyst in Claude Code?

Run `npx skills add antonbabenko/deliberation --skill scope-analyst -a claude-code`. Or copy the skill folder (.agents/skills/scope-analyst in antonbabenko/deliberation) into .claude/skills/scope-analyst in your project. Claude Code loads it when a task matches its description.

How do I install Scope Analyst in Codex?

Run `npx skills add antonbabenko/deliberation --skill scope-analyst -a codex`. Or copy the skill folder (.agents/skills/scope-analyst in antonbabenko/deliberation) into .agents/skills/scope-analyst in your project. Codex loads it when a task matches its description.

Can I use Scope Analyst 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 antonbabenko/deliberation --skill scope-analyst -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/scope-analyst, .gemini/skills/scope-analyst, .github/skills/scope-analyst and .opencode/skills/scope-analyst in your project.

What does Scope Analyst need to run?

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

Does Scope Analyst 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 Scope Analyst 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 Scope Analyst use?

Scope Analyst 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 Scope Analyst use?

About 1.4k tokens (SKILL.md is roughly 5.4k 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 Scope Analyst?

Skills that share tags, products or a category with Scope Analyst: Release (PrefectHQ/fastmcp, 28k stars), Claude Code Skill (codeaashu/claude-code, 3.4k stars), Deepseek Automation (zhu1090093659/deepseek-pp, 1.9k stars) and Review PR (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Scope Analyst?

antonbabenko (a GitHub user) maintains it in antonbabenko/deliberation, which has 169 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 6, 2026.

Source: antonbabenko/deliberation on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.