Scope analysis
Trigger: scope analysis, target boundary discovery. Delimit class/package/module scope.From its SKILL.md
npx -y skills add andresnator/agents-orchestrator --skill scope-analysisAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its file declares
Copied from the file, not written here
The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
0.8 KB, 127 tokens by cl100k_base, as published. Nobody here has run it
Scope Analysis
Delimit whether the target is a class, package, or module, then keep the plan inside that boundary.
How to inspect
- Identify the primary target file(s).
- Find public methods, exported APIs, public constructors, endpoints, and events.
- Find callers/consumers with references, imports, routes, LSP, or a code-graph index (for example, CodeGraph MCP/CLI) when available.
- Find existing tests by naming, package, fixtures, integration suites, and build metadata.
- Separate in-scope files from neighboring context.
- Record out-of-scope work explicitly.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.