CtrlK
BlogDocsLog inGet started
Tessl Logo

scope-check

Analyze a feature or sprint for scope creep by comparing current scope against the original plan. Flags additions, quantifies bloat, and recommends cuts. Use when user says 'any scope creep', 'scope review', 'are we staying in scope'.

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is an exemplary single-purpose workflow skill: lean, concrete, and well-sequenced with explicit validation and decision checkpoints. No bundle files are needed and none are referenced.

DimensionReasoningScore

Conciseness

The body is lean and action-oriented with no conceptual padding explaining what scope creep is, and the fill-in report template is functional scaffolding rather than verbosity, matching the score-3 anchor of every token earning its place.

3 / 3

Actionability

It gives concrete file paths (design/gdd/[feature].md, production/sprints/sprint-03.md), an executable git command, explicit verdict thresholds, and a copy-paste report template, matching the score-3 anchor of fully executable and specific guidance.

3 / 3

Workflow Clarity

The five phases are clearly sequenced with an explicit validation checkpoint in Phase 1 ('If the document is not found... stop') and a verdict-threshold table acting as a checklist, matching the score-3 anchor; the destructive-operation cap does not apply to this read-only skill.

3 / 3

Progressive Disclosure

No bundle files exist and the skill is a single coherent, well-sectioned workflow (Phase 1-5 plus Rules) with no nested references, so per the simple-skill scoring note well-organized inline content earns the score-3 anchor.

3 / 3

Total

12

/

12

Passed

Description

77%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is strong, clearly stating concrete capabilities and an explicit 'Use when' trigger. It is slightly weakened by a narrow set of trigger phrases and minor overlap risk with planning skills.

Suggestions

Broaden trigger terms to include common variations users might say, e.g. 'out of scope', 'scope bloat', or 'feature creep', to improve trigger_term_quality.

Sharpen distinctiveness by anchoring triggers more tightly to creep/over-scope detection (versus general planning) to reduce overlap with sprint-planning skills.

DimensionReasoningScore

Specificity

Quotes 'Analyze a feature or sprint for scope creep', 'comparing current scope against the original plan', and 'Flags additions, quantifies bloat, and recommends cuts' list multiple specific concrete actions, matching the score-3 anchor rather than the domain-plus-some-actions of score 2.

3 / 3

Completeness

It explicitly answers both what (analyze/compare/flag/quantify/recommend) and when via the 'Use when user says...' clause, matching the score-3 anchor and not the implied-only when of score 2.

3 / 3

Trigger Term Quality

The 'Use when user says' clause lists natural phrases ('any scope creep', 'scope review', 'are we staying in scope'), but coverage is narrow and misses common variations like 'out of scope' or 'scope bloat', fitting the score-2 anchor of some relevant keywords missing common variations.

2 / 3

Distinctiveness Conflict Risk

The scope-creep niche is reasonably specific, but 'scope review' could overlap with general sprint-planning skills, fitting the score-2 anchor of somewhat specific but potential overlap rather than the clearly-distinct niche of score 3.

2 / 3

Total

10

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
Donchitos/Claude-Code-Game-Studios
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.