CtrlK
BlogDocsLog inGet started
Tessl Logo

scope-guardian-reviewer

Reviews planning documents for scope alignment and unjustified complexity -- challenges unnecessary abstractions, premature frameworks, and scope that exceeds stated goals. Spawned by the document-review skill.

63

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/scope-guardian-reviewer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

93%Weight 40%Scale 1-5

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

The body is an exemplary instruction-only skill: lean, concrete, and well-sequenced, with actionable thresholds and a calibrated confidence protocol rather than vague review platitudes. The only meaningful gap is the absence of an explicit output/reporting format for findings.

DimensionReasoningScore

Conciseness

The body is lean and dense — no concept explanations Claude already knows, no padding; every line (e.g., "the cost gap between shortcuts and complete solutions is 10-100x smaller") adds non-obvious guidance, matching the 'every token earns its place' anchor.

5 / 5

Actionability

For an instruction-only skill the guidance is fully concrete and executable: hard thresholds (">8 files or >2 new abstractions", "80% of items at P0"), specific actions ("quote the item, ask which goal it serves"), and numeric confidence bands (0.80+, 0.60-0.79, below 0.50) — per the rubric's scoring notes, absence of code is not penalized when the guidance is this actionable.

5 / 5

Workflow Clarity

A clear five-step numbered protocol with explicit sequencing ("always first") plus a confidence-calibration checkpoint and a suppression rule fits anchor 4; it falls short of 5 only because there is no explicit output/reporting format for findings.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external references — per the rubric guideline, well-organized sections alone warrant a 5, and the section structure (analysis protocol, confidence calibration, exclusions) is clean and easy to navigate with no bundle files to place.

5 / 5

Total

19

/

20

Passed

Description

58%Weight 40%Scale 1-5

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 communicates a distinct, concrete capability with strong specificity, but it lacks any 'Use when...' trigger clause and misses natural user phrasings like "over-engineered" or "scope creep". As a spawned sub-skill the orchestration note partially compensates, but explicit trigger guidance would materially improve it.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when reviewing plans for over-engineering, scope creep, or unjustified complexity') so the skill can trigger without the parent skill.

Include natural user-facing trigger terms and synonyms such as 'over-engineered', 'scope creep', 'right-sized', and 'premature abstraction'.

Trim the provenance note ('Spawned by the document-review skill') or move it after the trigger guidance so the description leads with what and when.

DimensionReasoningScore

Specificity

"Reviews planning documents", "challenges unnecessary abstractions, premature frameworks, and scope that exceeds stated goals" lists several specific concrete actions with only minor coverage gaps, matching anchor 4 rather than the comprehensive coverage of anchor 5 or the 1-2-action scope of anchor 3.

4 / 5

Completeness

The 'what' is clear and specific, but there is no 'Use when...' clause or equivalent user-facing trigger guidance — "Spawned by the document-review skill" describes orchestration rather than when to invoke the skill, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Relevant keywords exist ("planning documents", "scope alignment", "complexity", "abstractions") but common natural variations users would say are missing ("over-engineered", "scope creep", "review this plan"), fitting the 'some relevant keywords but missing variations' anchor rather than anchor 4's good coverage.

3 / 5

Distinctiveness Conflict Risk

A clear niche (scope/complexity review of planning documents) with explicit separation from product-lens, coherence-reviewer, and other review skills; only minor overlap risk with generic code/plan review, so anchor 4 fits better than 5.

4 / 5

Total

14

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

13

/

16

Passed

Repository
udecode/plate
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.