add-command

Use when adding a new cmake.* command to CMake Tools. Touches package.json (contributes.commands), package.nls.json, src/extension.ts (funs array), and CHANGELOG.md. Triggers: "add command", "register command", "new command palette entry".

Quality

87%

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

Quality

Content

82%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.

A well-structured, highly actionable recipe with concrete code for each step and a solid verification checklist. It could tighten a few explanatory asides and add an explicit error-recovery loop for the compile check.

Suggestions

Add an explicit feedback loop after the verification checklist (e.g., 'If yarn compile fails, fix the reported errors and re-run until it succeeds') to strengthen workflow validation.

Trim minor over-explanatory prose such as the manual-registerCommand blockquote and the Command Palette prefix aside, keeping only the actionable rule.

Consider moving the common `when`-clause patterns table or the handler-pattern catalog into a referenced file to better separate overview from detail.

Dimension	Reasoning	Score
Conciseness	Mostly lean with code-first examples and tables; assumes Claude's competence. A few explanatory asides (e.g. "this prefixes the title in the Command Palette as CMake: <title>", the manual-registerCommand blockquote) could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready code for every step — jsonc for package.json, json for package.nls.json, and three TypeScript handler patterns — covering the common cases with specific file locations.	5 / 5
Workflow Clarity	Five clearly sequenced steps plus a verification checklist (including "yarn compile succeeds" and "No files under i18n/ were modified") provide good checkpoints, but an explicit validate-fix-retry feedback loop for compile failure is not spelled out.	4 / 5
Progressive Disclosure	Well-organized with an overview table, stepped sections, and a single one-level-deep reference (copilot-instructions.md); content is all inline rather than split into referenced files, but the structure keeps navigation easy.	4 / 5
	Total	17 / 20 Passed

Description

92%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.

A strong, specific description that clearly states what it does and when to use it, with concrete file touchpoints and natural trigger phrases. Minor room only for broader trigger-term synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain (adding a cmake.* command) and comprehensively lists the concrete touchpoints — "package.json (contributes.commands), package.nls.json, src/extension.ts (funs array), and CHANGELOG.md" — covering the full scope with no gaps.	5 / 5
Completeness	Explicitly answers both what ("adding a new cmake.* command to CMake Tools" plus the files touched) and when ("Use when adding..." with a concrete Triggers list), matching the anchor for clear what-and-when with trigger phrases.	5 / 5
Trigger Term Quality	Provides natural trigger phrases users would say — "add command", "register command", "new command palette entry" — with synonym variation, though a few natural variants (e.g. "create command") are absent.	4 / 5
Distinctiveness Conflict Risk	Targets a clear, narrow niche (CMake Tools cmake.* commands) with distinct triggers, making conflict with unrelated skills minimal.	5 / 5
	Total	19 / 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
relative_links	Relative link issues: 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: microsoft/vscode-cmake-tools
Path: .github/skills/add-command/SKILL.md
Commit: 916baba

Reviewed: 4 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.