CtrlK
BlogDocsLog inGet started
Tessl Logo

protected-files

Zero-dependency bootstrap files that must never import npm packages or SDK code

55

Quality

62%

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/protected-files/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 content is a well-structured, concise guard skill with concrete file paths, explicit rules, and a usable workflow for adding new protected utilities. Its main weakness is that the broader sweeping-refactor workflow relies on a checklist rather than an explicit validation gate.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, stating the failure mode and rules without padding; only minor instances (the repeated boundary note and the 'prevention is better than detection' tagline) could be trimmed.

4 / 5

Actionability

Concrete, executable guidance dominates: exact file paths in a table, specific import statements to forbid, and a worked example of the forbidden import line. It is instruction-oriented rather than code-based, but the guidance is specific and actionable.

4 / 5

Workflow Clarity

The 'Adding New Bootstrap Utilities' section gives a clear 3-step sequence with a verification checkpoint (step 2: write a matching zero-dependency regression test), so the batch/refactor context is not left without validation; only the broader refactor workflow lacks an explicit validate-then-proceed loop.

4 / 5

Progressive Disclosure

A compact single-purpose skill (~45 lines, no bundle files needed) with well-organized sections (Context, Protected File List, Rules, Boundary, Anti-Patterns, Adding Utilities) and a single one-level reference to a repo test file for the pattern; navigation is clear.

5 / 5

Total

17

/

20

Passed

Description

46%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 is specific and distinct but reads as a constraint statement rather than a usage-oriented skill description. It lacks natural trigger terms and any explicit "when to use" guidance, which together cap its completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when editing files in packages/squad-cli/src/cli/core/ or running sweeping refactors that touch fs/StorageProvider calls.'

Rewrite the description in capability form ('Guards zero-dependency bootstrap files from...') so it describes what the skill does, not just what the files must avoid.

Add user-natural synonyms beyond jargon, such as 'startup files', 'CLI init code', or 'early-load utilities'.

DimensionReasoningScore

Specificity

Names a concrete domain ("Zero-dependency bootstrap files") and a specific constraint ("must never import npm packages or SDK code"), but states a single protective concept rather than listing multiple concrete actions the skill performs.

3 / 5

Completeness

Provides a clear "what" (zero-dependency bootstrap files under an import constraint) but lacks any "Use when..." or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Relies on technical jargon ("bootstrap files", "SDK code", "npm packages") rather than natural phrases a user would say when needing this skill; no common synonyms or varied trigger terms are present.

2 / 5

Distinctiveness Conflict Risk

The narrow niche (zero-dependency CLI bootstrap files vs. SDK imports) is clearly distinguishable with minimal overlap risk against other skills, though it is not framed with explicit distinct trigger phrases.

4 / 5

Total

12

/

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.

Validation15 / 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.