CtrlK
BlogDocsLog inGet started
Tessl Logo

content-scope

Keep Squad documentation focused on shipped behavior and clearly bounded integrations

57

Quality

66%

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 ./.copilot/skills/content-scope/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 a concise, well-structured decision framework with concrete rules, a worked example, and explicit anti-patterns, appropriately scoped for a simple instruction-only skill. It performs well on conciseness, actionability, and organization, with only minor room to make the decision workflow more explicit.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence without explaining what documentation or integrations are, with only minor phrasing that could be tightened, fitting the 'efficient; minor instances that could be trimmed' anchor rather than the perfectly lean 5.

4 / 5

Actionability

Concrete decision rules ('Apply the Squad ships it test', 'identify it as a platform integration rather than implying Squad implements'), plus a worked example and explicit anti-patterns, give mostly actionable guidance; it stops short of a fully copy-paste-ready 5 because the decisions remain judgment-based.

4 / 5

Workflow Clarity

The single decision task is unambiguous and supported by patterns, a positive example, and anti-patterns, but it is a decision framework rather than an explicitly sequenced workflow with checkpoints, so it fits the 'clear sequence with most checkpoints' band rather than a 5.

4 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references and is organized into clearly labeled sections (Context, Patterns, Examples, Anti-Patterns), which the simple-skill exception says can score 5.

5 / 5

Total

17

/

20

Passed

Description

53%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 states a clear, domain-specific purpose but omits any explicit trigger guidance for when to invoke the skill, which caps completeness at the midpoint. It is concise and distinct but would benefit from a 'Use when...' clause.

Suggestions

Add a 'Use when...' clause naming concrete triggering situations, e.g. 'Use when deciding what belongs in Squad documentation or reviewing integration docs for scope.'

Include natural synonyms a user might say ('doc scope', 'what to document', 'integration boundaries') to improve trigger-term coverage.

Optionally enumerate one or two more concrete actions to lift specificity above the single-framing-action level.

DimensionReasoningScore

Specificity

Names the domain ('Squad documentation') and one-to-two concrete framing actions ('focused on shipped behavior and clearly bounded integrations'), matching the anchor for naming a domain with limited concrete actions rather than the comprehensive multi-action list of a 4 or 5.

3 / 5

Completeness

It gives a clear 'what' ('Keep Squad documentation focused on shipped behavior and clearly bounded integrations') but no 'when'/'Use when...' clause, so per the missing-trigger-guidance cap it cannot exceed 3.

3 / 5

Trigger Term Quality

Terms like 'Squad documentation', 'shipped behavior', and 'bounded integrations' are relevant to the niche but lack common synonyms or variations a user might naturally say, fitting the 'some relevant keywords but missing variations' anchor.

3 / 5

Distinctiveness Conflict Risk

'Squad documentation' carves a clear niche with minimal conflict risk against generic skills, though it could still overlap slightly with closely related documentation-scope skills, fitting the 'mostly distinct; minor overlap risk' anchor rather than the fully distinct 5.

4 / 5

Total

13

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
bradygaster/squad
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.