CtrlK
BlogDocsLog inGet started
Tessl Logo

squad-conventions

Core conventions and patterns used in the Squad codebase

68

1.27x
Quality

53%

Does it follow best practices?

Impact

93%

1.27x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is squad-conventions in bradygaster/squad

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 well-structured, concise, and actionable — concrete functions, constants, commands, and runnable examples back every pattern, and anti-patterns reinforce them. It would benefit only slightly from trimming a few obvious-restating sentences and, if relevant, adding a brief validation note for the init/upgrade overwrite distinction.

Suggestions

Trim mildly redundant clauses like "This is a hard constraint, not a preference" and "Squad must work on Windows, macOS, and Linux" to tighten conciseness toward a 5.

Consider a short, explicit validation/checklist step distinguishing which operations are safe (init skip-if-exists) vs. destructive (upgrade overwrites Squad-owned files), which would lift workflow clarity.

If deeper detail exists elsewhere (e.g. full template inventory), signal it as a one-level reference rather than relying on the inlined file-structure list.

DimensionReasoningScore

Conciseness

The body is lean and assumes programming competence, with only minor restatements of the obvious (e.g. "This is a hard constraint, not a preference") that could be trimmed.

4 / 5

Actionability

It gives concrete, executable guidance — named functions (fatal(), copyRecursive()), constants (GREEN, RED), the test command (node --test test/), and runnable code — with only minor gaps in full signatures.

4 / 5

Workflow Clarity

As a conventions/reference skill with no destructive batch process, the destructive-cap does not apply; the clear Context → Patterns → Examples → Anti-Patterns structure is coherent, though it presents patterns rather than a sequenced multi-step workflow with checkpoints.

4 / 5

Progressive Disclosure

The skill is compact (~60 lines) with no bundle files needed and is cleanly sectioned (Context, Patterns, Examples, Anti-Patterns) with no nested references, matching the well-organized-sections anchor for small skills.

5 / 5

Total

17

/

20

Passed

Description

28%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 third-person and names a specific project, but it is otherwise a vague, trigger-light sentence with no concrete actions and no "Use when..." guidance. It would be hard for a user to invoke this skill from the description alone.

Suggestions

Add concrete actions to the description, e.g. "Documents the zero-dependency, node:test, fatal()-error-handling, and path.join() Windows-compatibility conventions for the create-squad CLI."

Add a "Use when..." clause naming natural trigger phrases, e.g. "Use when modifying Squad source code, adding CLI features, or writing Squad-compatible tests."

Include user-natural keywords and file extensions (e.g. "create-squad", "package.json", "node:test") to improve trigger-term matching and distinctiveness.

DimensionReasoningScore

Specificity

The description names a domain ("Core conventions and patterns used in the Squad codebase") but lists no concrete actions, leaving it at the generic "names domain, actions minimal" anchor.

2 / 5

Completeness

It offers only a vague "what" (conventions and patterns) and entirely omits any "when to use" guidance, matching the "vague what and no when" anchor rather than the score-3 clear-what anchor.

2 / 5

Trigger Term Quality

"conventions and patterns" is generic jargon a user would not naturally utter when requesting this skill, and no natural phrases or synonyms are included.

2 / 5

Distinctiveness Conflict Risk

Naming the "Squad codebase" provides a project-specific niche, but "core conventions and patterns" is broad enough to overlap with other squad-related skills, so it sits at the "somewhat specific but could overlap" anchor.

3 / 5

Total

9

/

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
microsoft/waza
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.