squad-conventions

Core conventions and patterns used in the Squad codebase

1.27x

Quality

63%

Does it follow best practices?

Impact

93%

1.27x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.copilot/skills/squad-conventions/SKILL.md

Quality

Content

87%

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 tight, highly actionable conventions reference with executable examples and concrete names/commands, well-organized into clear sections. Its only gap is workflow clarity: it describes rules and patterns rather than a checkpointed multi-step workflow with validation feedback loops.

Dimension	Reasoning	Score
Conciseness	The body is lean imperative guidance with concrete specifics (function names, commands, constants, paths) and no padding explaining concepts Claude already knows; every section earns its tokens, matching the 'lean and efficient' anchor rather than the 'could be tightened' level 2 (the Anti-Patterns reinforce rather than restate basics).	3 / 3
Actionability	It gives executable JavaScript examples plus specific commands (`npm test`, `node --test test/`), named functions (`fatal(msg)`, `copyRecursive(src, target)`), and exact constants/paths, matching 'fully executable code/commands; copy-paste ready' rather than the pseudocode/incomplete level 2.	3 / 3
Workflow Clarity	This is a conventions reference, not a sequenced multi-step process; the init/upgrade behaviors are stated as rules without explicit validation checkpoints or feedback loops, so it sits at 'sequence present but checkpoints missing/implicit' rather than the checkpointed-workflow level 3.	2 / 3
Progressive Disclosure	The skill is self-contained (no references/, scripts/, or assets/ bundle exists) with well-organized sections (Context, Patterns, Examples, Anti-Patterns) and no nested references; per the simple-skill guidance this earns a 3 on clear organization alone, rather than the inline-bloat level 2.	3 / 3
	Total	11 / 12 Passed

Description

40%

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 identifies its domain (Squad codebase conventions) but is too topical and lacks concrete actions and any explicit use-when trigger guidance. It is distinct enough by project name yet reads more like a label than an activatable skill description.

Suggestions

Add concrete actions, e.g. 'Enforces zero-dependency, Node-built-in test runner, fatal() error handling, and path.join() conventions when modifying the Squad CLI source.'

Append an explicit trigger clause such as 'Use when modifying create-squad source code or reviewing Squad pull requests.'

Include natural trigger variations users would say (e.g. 'Squad CLI', 'create-squad', 'Squad patterns', 'Squad source') to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description 'Core conventions and patterns used in the Squad codebase' names a topic/domain but lists no concrete actions, matching the vague/abstract anchor ('Processes data', 'Helps with documents') rather than the action-listing level above.	1 / 3
Completeness	It weakly answers 'what' (conventions and patterns) but offers no 'when should Claude use it' guidance; per the rubric a missing 'Use when...' clause caps completeness at 2, and it is not weak enough on 'what' to fall to 1.	2 / 3
Trigger Term Quality	'Squad codebase' provides one relevant keyword a contributor might say, but there are no natural trigger variations or 'Use when' phrasing, fitting 'some relevant keywords but missing common variations' rather than the empty/generic level 1.	2 / 3
Distinctiveness Conflict Risk	Being scoped to the named 'Squad codebase' gives it a niche that limits conflicts, but with no explicit trigger language it could still overlap with generic codebase-conventions skills, matching 'somewhat specific but could still overlap' rather than the clear-distinct-trigger level 3.	2 / 3
	Total	7 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: bradygaster/squad
Path: .copilot/skills/squad-conventions/SKILL.md
Commit: e23dd92

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.