cli-wiring

Checklist and patterns for wiring new CLI commands into cli-entry.ts

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.copilot/skills/cli-wiring/SKILL.md

Quality

Content

92%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 lean, well-structured, and actionable, with a clear checklist that includes an explicit verification step keyed to the recurring bug. The only minor gap is that code examples use template placeholders rather than fully concrete copy-paste snippets.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: a tight checklist, a compact wiring-pattern table, a single import snippet, and a brief history note, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	It provides concrete, mostly-executable code templates for the routing block, help text, and import pattern, plus a table mapping command types to wiring approaches; the use of placeholders like <name> and run<Name> keeps it just short of copy-paste-ready, fitting 'mostly executable guidance with minor gaps'.	4 / 5
Workflow Clarity	A clear 4-step checklist with an explicit validation checkpoint ('Verify both exist — the recurring bug is doing step 1 but missing steps 2-3'); as a simple single-purpose skill under 50 lines, it qualifies for the top anchor.	5 / 5
Progressive Disclosure	Under 50 lines with well-organized sections (checklist, patterns table, import pattern, history) and no need for external references, satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	19 / 20 Passed

Description

57%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 clearly distinct with minimal conflict risk, but it lacks any explicit 'when to use' trigger guidance and only lightly enumerates actions. Adding a 'Use when...' clause with natural trigger phrases would raise completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when adding a new CLI command to squad-cli or when a command exists in commands/ but is not reachable from cli-entry.ts.'

Include natural trigger synonyms users might say, such as 'register a CLI command', 'route a command', or 'wire up a command'.

Optionally list one or two concrete actions (e.g. 'add a routing block and help text') to lift specificity from 3 toward 4.

Dimension	Reasoning	Score
Specificity	The description names the domain and a couple of concrete elements ('Checklist and patterns for wiring new CLI commands into cli-entry.ts'), but does not enumerate multiple specific actions, matching the 'names domain and 1-2 concrete actions' anchor rather than the more comprehensive level 4.	3 / 5
Completeness	It clearly states what the skill is (a checklist and patterns for wiring CLI commands), but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	It includes relevant terms like 'CLI commands', 'wiring', and the specific file 'cli-entry.ts', but offers no common synonyms or variations a user might naturally say, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The description targets a highly specific niche — wiring commands into a named file (cli-entry.ts) — giving it distinct triggers and minimal overlap risk with other skills, matching the 'clear niche with distinct triggers' anchor.	5 / 5
	Total	14 / 20 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/cli-wiring/SKILL.md
Commit: 26d8950

Reviewed: 2 days 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.