MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
A skill your agent uses when the user says "plan this", "decompose this task", "break this down", or wants the task file before any code changes.
Install Scope
$ npx skills add ccplugins/awesome-claude-code-plugins --skill scope -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins scope --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/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/hyperflow/skills/scope .claude/skills/scope && 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 "scope" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/hyperflow/skills/scope into .claude/skills/scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope", 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/ccplugins/awesome-claude-code-plugins/tree/main/plugins/hyperflow/skills/scopeType 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 ccplugins/awesome-claude-code-plugins --skill scope -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins scope --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/hyperflow/skills/scope .agents/skills/scope && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "scope" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/hyperflow/skills/scope into .agents/skills/scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope", 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 ccplugins/awesome-claude-code-plugins --skill scope -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins scope --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/hyperflow/skills/scope .cursor/skills/scope && 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 "scope" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/hyperflow/skills/scope into .cursor/skills/scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope", 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/ccplugins/awesome-claude-code-plugins.git --path plugins/hyperflow/skills/scope--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 ccplugins/awesome-claude-code-plugins --skill scope -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins scope --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/hyperflow/skills/scope .gemini/skills/scope && 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 "scope" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/hyperflow/skills/scope into .gemini/skills/scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope", 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 ccplugins/awesome-claude-code-plugins scopeInstalls 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 ccplugins/awesome-claude-code-plugins --skill scope -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/hyperflow/skills/scope .github/skills/scope && 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 "scope" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/hyperflow/skills/scope into .github/skills/scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope", 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 ccplugins/awesome-claude-code-plugins --skill scope -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ccplugins/awesome-claude-code-plugins scope --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ccplugins/awesome-claude-code-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/hyperflow/skills/scope .opencode/skills/scope && 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 "scope" agent skill from https://github.com/ccplugins/awesome-claude-code-plugins/tree/main/plugins/hyperflow/skills/scope into .opencode/skills/scope/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "scope", 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
scope- GitHub stars
- 967
- Token cost
- ~1.8k tokens
- SKILL.md length
- 723 words
- Files
- 1
- Skills in repo
- 68
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when the user says "plan this", "decompose this task", "break this down", or wants the task file before any code changes.
- Works in 8 steps: Choose chain mode (FIRST tool call ·… → Understand → Research (parallel) → …
- The user says plan this
- SKILL.md covers Per-Step Agent Map (DOCTRINE…, Approval Gates, Flow and Anti-patterns, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Scope is an agent skill from ccplugins/awesome-claude-code-plugins. Use when the user says "plan this", "decompose this task", "break this down", or wants the task file before any code changes. Writes .hyperflow/tasks/<slug.md with batched sub-tasks, then auto-chains into /hyperflow:dispatch — no manual gate.
Its SKILL.md is about 1.8k 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. The repository describes itself as: Awesome Claude Code plugins — a curated list of slash commands, subagents, MCP servers, and hooks for Claude Code. The licence is Apache-2.0.
When your agent uses it
- The user says plan this
- Decompose this task
- Break this down
- Wants the task file before any code changes
Example prompts
- “plan this”
- “decompose this task”
- “break this down”
- “/scope”
Workflow steps
8 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 5bd4f16. 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 (its code samples are markdown).
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 loads about 1.8k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 723 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
The full file from ccplugins/awesome-claude-code-plugins at commit 5bd4f16, republished under its Apache-2.0 licence (© ccplugins). 723 words, ~1,830 tokens.
Download SKILL.mdSave it as
.claude/skills/scope/SKILL.md (or your agent's skills folder).- name
- scope
- description
- Use when the user says "plan this", "decompose this task", "break this down", or wants the task file before any code changes. Writes `.hyperflow/tasks/<slug>.md` with batched sub-tasks, then **auto-chains into `/hyperflow:dispatch`** — no manual gate.
Scope
Decompose, don't build. Read-only with respect to source code. The only writes are to .hyperflow/tasks/, .hyperflow/memory/, and .hyperflow/specs/. When the task file is ready, hand off to dispatch (auto or with a gate, depending on chain mode).
This skill exercises Layer 0 (Project Analysis) for context, Layer 6 (Project Memory) for past-learning surfacing, and Layer 7 (Task Templates) for decomposition patterns. It also inherits the triage classification from /hyperflow:spec to size each batch correctly.
Per-Step Agent Map (DOCTRINE rule 12)
Every substantive step dispatches at least one Agent.
| Step | Worker tier | Thinking tier | Notes |
|---|---|---|---|
| 0 — Chain mode | — | — | AskUserQuestion only (exempt) |
| 1 — Understand | — | — | AskUserQuestion if ambiguous (exempt) |
| 2 — Research | Searcher × 2 (Sonnet) parallel | Reviewer (Opus) verifies coverage | Both tiers |
| 3 — Decompose | — | Planner (Opus) produces the batch graph | Pure thinking |
| 4 — Write task file | Writer (Sonnet) emits the markdown | Reviewer (Opus) verifies the plan vs the design | Both tiers |
| 5 — Output | — | — | Print only (exempt) |
| 6 — Memory | Writer (Sonnet) appends to memory files | Reviewer (Opus) checks for duplicates / contradictions | Both tiers |
| 7 — Hand off | — | — | Skill tool invocation (exempt) |
Approval Gates
| Gate | When | Format |
|---|---|---|
| Chain mode | Step 0, only if invoked directly | AskUserQuestion — auto / manual |
| Decomposition sanity | Step 4, after writing the task file | Print the batch summary; user reads it |
Phase advance (if manual mode) | Step 7, before invoking dispatch | AskUserQuestion — continue / stop |
Flow
Step 0 — Choose chain mode (FIRST tool call · STRUCTURAL GATE)
This is a structural gate per DOCTRINE rule 8. It MUST fire every time the skill is invoked directly. "No clarifying questions" / "auto-pilot" / "always-on" / any other autonomy directive does NOT skip it. Defaulting to auto without asking is a doctrine violation.
If invoked with a chain-mode=<auto|manual> arg (from /hyperflow:spec or a prior skill), skip this step — the previous chain-starter already asked.
Otherwise, before research, ask via AskUserQuestion. Per DOCTRINE rule 8, the recommended option goes first with (Recommended):
How should I advance through the chain after this phase?
Auto (Recommended) — chain forward through scope → dispatch with no gate.
Fewer interruptions, faster end-to-end.
Manual — pause between phases and ask before advancing.
More control, more confirmations.Wait for the user's answer. Do not proceed without it. Save the chosen mode and propagate via args: "chain-mode=<mode>" when invoking dispatch.
If the agent cannot present AskUserQuestion (e.g., headless mode), it should print an error and stop — never silently default.
Step 1 — Understand
- Ambiguous →
AskUserQuestion(max 3) - Pure design question → suggest
/hyperflow:specinstead and stop
Step 2 — Research (parallel)
Agents — Searcher × 2 (Sonnet) ⇒ Reviewer (Opus).
- Dispatch in a single message (parallel):
Searcher — mapping affected files and existing patternsSearcher — finding related tests and conventions
- Read
.hyperflow/profile.md,architecture.md,conventions.md, and.hyperflow/memory/index.mdto surface relevant past learnings. - Dispatch
**Reviewer** — verifying research coverageto confirm both Searchers hit the relevant subsystems. If gaps remain, redispatch a Searcher targeting the gap before moving on.
Show full SKILL.md (289 more words)Show less
Step 3 — Decompose
Agents — Planner (Opus, thinking-tier).
Dispatch **Planner** — producing batch graph with the research findings, triage classification, and applicable templates from task-templates.md (CRUD Feature, API Endpoint, UI Component, Database Migration, Refactor, Bug Fix — else bespoke).
The Planner produces, for each sub-task:
- Worker role — Implementer / Searcher / Writer
- Files to read / modify / create
- Dependencies — parallel vs sequential
- Complexity estimate (drives review level cap downstream)
Step 4 — Write Task File
Agents — Writer (Sonnet) ⇒ Reviewer (Opus).
- Dispatch
Writer — emitting task filewith the Planner's output. The Writer writes to.hyperflow/tasks/<task-slug>.mdusing the template below. - Dispatch
**Reviewer** — verifying task file vs designto confirm every design requirement maps to at least one sub-task and no orphan sub-tasks exist.
Task-file template —
# Task: <Name>
## Goal
<one-line>
## Context
<background, why this matters, research findings>
## Affected files
- Read: <list>
- Modify: <list>
- Create: <list>
## Batches
### Batch 1 (parallel)
- [ ] T1: [Role] <description>
- [ ] T2: [Role] <description>
### Batch 2 (sequential — depends on Batch 1)
- [ ] T3: [Role] <description>
### Batch 3
- [ ] T4: Final integration review
## Open questions
<anything needing user input before execution>
## Verification plan
<how to test end-to-end>
## Estimated cost
- Thinking: ~N agents, ~Xk tokens
- Worker: ~N agents, ~Yk tokens
## Status
Created: <date>Step 5 — Output
Print the task file path and batch summary table:
Plan ready — .hyperflow/tasks/<slug>.md (3 batches, 7 sub-tasks)Step 6 — Memory
Agents — Writer (Sonnet) ⇒ Reviewer (Opus).
- Dispatch
Writer — appending decisions to .hyperflow/memory/decisions.md. Skip trivial ones. For complex features (3+ files, multiple subsystems) the Writer also produces.hyperflow/specs/<feature-slug>.mdreferenced from the task file. - Dispatch
**Reviewer** — checking memory entriesto catch duplicates or contradictions with existing entries before they land in.hyperflow/memory/.
See task-tracking.md and worker-prompt.md.
Step 7 — Hand off to /hyperflow:dispatch
If chain-mode=auto — immediately invoke Skill with skill: execute and args: "chain-mode=auto <task-slug>". Print:
Auto-chaining to /hyperflow:dispatch…If chain-mode=manual — ask via AskUserQuestion: "Plan done. Continue to /hyperflow:dispatch?" → yes / no / stop. On yes, invoke Skill with skill: execute and args: "chain-mode=manual <task-slug>".
Anti-patterns
- Writing implementation code
- Modifying source files outside
.hyperflow/and.hyperflow/specs/ - Skipping the research step
- Single-batch plans for multi-file work
- Omitting the verification plan
- Pausing for "should I execute?" when
chain-mode=auto— that was already answered at Step 0 - Asking the chain-mode question again when a
chain-mode=<…>arg was passed in
References
- DOCTRINE.md — shared rules
- output-style.md — elegant label format
© ccplugins, Apache-2.0. 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 plugins/hyperflow/skills/scope of ccplugins/awesome-claude-code-plugins.
Open the folder on GitHubat commit 5bd4f16
Compare with similar skills
Scope 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 |
|---|---|---|---|---|---|---|
| Scope this skillccplugins/awesome-claude-code-plugins | 967 | — | ~1.8k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server Builderanthropics/skills | 180k | 62 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 37k | 11 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 34 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 37k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
More from ccplugins/awesome-claude-code-plugins
All 68 skills in this repoAI Meeting
ccplugins/awesome-claude-code-plugins
Run structured AI meetings for plans, product ideas, technical designs, business decisions, feature proposals, and strategy choices.
Fastapi App
ccplugins/awesome-claude-code-plugins
Bootstrap a new FastAPI backend with async SQLAlchemy 2.0, asyncpg, Alembic, Pydantic v2, and no deprecated APIs.
Flutter App
ccplugins/awesome-claude-code-plugins
Bootstrap a new Flutter mobile app with clean architecture, Riverpod, FVM-pinned SDK, current packages, and no deprecated APIs.
Nextjs App
ccplugins/awesome-claude-code-plugins
Bootstrap a new Next.js (App Router, TypeScript) web app with current packages and no deprecated APIs.
Dev Report
ccplugins/awesome-claude-code-plugins
Write up a coding session for a non-technical stakeholder — the context, what was built, and the engineering reasoning behind it — the way a senior engineer briefs a product manager who does not…
Difesa Attacchi
ccplugins/awesome-claude-code-plugins
Aggiunge a un sito/app un agente di difesa che rileva e blocca richieste malevole (SQL injection, XSS, path traversal, brute force, bot) con rate limiting, blocklist IP e modalità lockdown che…
Related
Categories
Questions about Scope
What does Scope do?
A skill your agent uses when the user says "plan this", "decompose this task", "break this down", or wants the task file before any code changes. Scope is an agent skill from ccplugins/awesome-claude-code-plugins. Use when the user says "plan this", "decompose this task", "break this down", or wants the task file before any code changes.
When should I use Scope?
Scope fits situations like: the user says plan this; decompose this task; break this down; wants the task file before any code changes.
How do I install Scope in Claude Code?
Run `npx skills add ccplugins/awesome-claude-code-plugins --skill scope -a claude-code`. Or copy the skill folder (plugins/hyperflow/skills/scope in ccplugins/awesome-claude-code-plugins) into .claude/skills/scope in your project. Claude Code loads it when a task matches its description.
How do I install Scope in Codex?
Run `npx skills add ccplugins/awesome-claude-code-plugins --skill scope -a codex`. Or copy the skill folder (plugins/hyperflow/skills/scope in ccplugins/awesome-claude-code-plugins) into .agents/skills/scope in your project. Codex loads it when a task matches its description.
Can I use Scope 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 ccplugins/awesome-claude-code-plugins --skill scope -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, .gemini/skills/scope, .github/skills/scope and .opencode/skills/scope in your project.
What does Scope need to run?
SKILL.md names no scripts, command-line tools or credentials: Scope is instructions for the agent only.
Does Scope 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 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 use?
Scope is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Scope use?
About 1.8k tokens (SKILL.md is roughly 7.3k 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?
Skills that share tags, products or a category with Scope: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Scope?
ccplugins (a GitHub organization) maintains it in ccplugins/awesome-claude-code-plugins, which has 967 GitHub stars. The repository holds 68 skills in this directory. The repository was last updated on August 12, 2026.
Source: ccplugins/awesome-claude-code-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.