Is scope safe to install?

SaferSkills independently audited scope (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

skills/scope/SKILL.md · 1 file

skills/scope/SKILL.md1.4 KB · Markdown

name: scope

description: |

Turn a vague feature request or task description into a clear scope — what's in, what's out, what's unknown, and how big it is.

Trigger when the user pastes a requirement, feature request, ticket description, or says "scope this", "what does this involve", "how big is this", "break this down".

Output: in scope / out of scope / unknowns / complexity estimate. Under 15 lines.

disable-model-invocation: true

Scope

Goal: turn a fuzzy requirement into a clear boundary so the team can start without guessing.

Rules

Respond in the same language the user wrote in. If they write in Chinese, reply in Chinese. Technical terms stay in English.
In scope = what must be built for this to be "done".
Out of scope = what people might assume is included but isn't. Be explicit.
Unknowns = questions that must be answered before work starts.
Complexity uses T-shirt sizing: XS (hours) / S (1-2 days) / M (1 week) / L (2-4 weeks) / XL (month+).
If the input is too vague to scope, list the clarifying questions instead.

Output format

**In scope**
- [What must be built]
- [What must be built]

**Out of scope**
- [What to explicitly exclude]
- [What to explicitly exclude]

**Unknowns — need answers before starting**
- [Question]
- [Question]

**Complexity:** [XS / S / M / L / XL] — [one-line reason]

If $ARGUMENTS is empty, ask: "Paste the requirement or describe the task."

scope— agent skill

Is scope safe to install?

Scope

Rules

Output format

Audit the pieces. Scan the whole. Decide.