CtrlK
BlogDocsLog inGet started
Tessl Logo

cli-wiring

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

65

Quality

78%

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/cli-wiring/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tight, actionable checklist with concrete code and paths, a clear sequenced workflow with a verification step, and clean section organization — strong across all dimensions.

DimensionReasoningScore

Conciseness

The body is lean and targeted — concrete paths, compact code blocks, and a typed table with no padding or explanation of concepts Claude already knows, matching the 'lean and efficient; every token earns its place' anchor.

3 / 3

Actionability

It gives concrete file paths and copy-paste-ready routing, help-text, and import code blocks plus a patterns-by-type table, matching the 'fully executable code/commands; copy-paste ready' anchor.

3 / 3

Workflow Clarity

A clear 4-step numbered checklist includes an explicit verification checkpoint ('Verify both exist — the recurring bug is doing step 1 but missing steps 2-3'), satisfying the 'clear sequence with explicit validation steps' anchor.

3 / 3

Progressive Disclosure

The skill is under 50 lines, needs no external references, and is well-organized into clear sections (Checklist, Wiring Patterns, Import Pattern, History), which per the simple-skills scoring note earns a 3.

3 / 3

Total

12

/

12

Passed

Description

57%

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 well-scoped to a concrete file, but it omits explicit 'when to use' trigger guidance and leans on internal jargon, leaving trigger-term quality and completeness at the mid level.

Suggestions

Add an explicit 'Use when ...' trigger clause, e.g. 'Use when adding or registering a new CLI command in the squad-cli package.'

Broaden trigger terms beyond the internal filename to natural phrasings a developer would say, such as 'add a CLI command', 'register a command', or 'route a command in cli-entry'.

List one or two concrete actions (e.g. 'add the routing block and help text') to lift specificity from naming the domain to enumerating actions.

DimensionReasoningScore

Specificity

Names the domain ('wiring new CLI commands into cli-entry.ts') and the artifact type ('Checklist and patterns'), but does not enumerate multiple concrete actions, matching the 'names domain and some actions' anchor rather than the multi-action level 3.

2 / 3

Completeness

It states what the skill provides but has no 'Use when...' or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

'CLI commands' and 'wiring' are natural developer terms, but 'cli-entry.ts' is internal jargon and common phrasings like 'add a CLI command' or 'register a command' are absent, fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

The description is scoped to a specific file (cli-entry.ts) in a specific codebase, giving it a clear niche that is unlikely to trigger for the wrong skill.

3 / 3

Total

9

/

12

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.