validation-project

Creates a validation project for testing a specific vscode-cmake-tools pull request. Use this skill when asked to create a validation project, test a PR, validate a pull request, or set up a PR validation environment. The skill creates a structured project directory with documentation, metadata, and checklists for systematically validating PR changes.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

73%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 thorough, well-sequenced instruction skill with strong validation checkpoints and copy-ready templates. Its chief weakness is verbosity in places where it explains rationale a competent reader would infer, and the absence of any reference bundle to offload the long inline skeletons.

Suggestions

Trim justifying rationale (e.g., the 'gold standard for validating a PR' explanation and repeated 'place files directly in the project root' restatements) to respect token budget.

Extract the full README.md and manual-checklist.md templates into a references/ file, leaving concise inline summaries so SKILL.md stays a lean overview.

Add at least one filled CMakeLists.txt / CMakePresets.json example pair to make the 'generate test project files' step fully copy-paste-ready.

Dimension	Reasoning	Score
Conciseness	Mostly efficient but carries padded explanatory passages (e.g., the gold-standard rationale for two-line expected results, and repeated restatements of 'place files directly in the project root') that a competent reader could infer, so it sits at the midpoint rather than lean.	3 / 5
Actionability	Provides concrete, copy-paste-ready templates for validation.json, README.md, and manual-checklist.md plus explicit naming conventions, with only minor gaps (e.g., CMakeLists.txt/CMakePresets.json show structure but not filled examples) keeping it below fully executable.	4 / 5
Workflow Clarity	Seven clearly sequenced steps with explicit validation checkpoints and a feedback-oriented manual checklist (PR-build vs baseline expected results, PASS/FAIL gate, Issues Found section) matching the gold-standard anchor.	5 / 5
Progressive Disclosure	Well-organized single-file skill with clear section hierarchy and inline templates; no bundle files exist to offload the longer templates, so content that could be separate (full README/checklist skeletons) stays inline, leaving a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

87%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, third-person description that pairs a concrete 'what' with an explicit 'Use when' trigger clause and niche-specific phrasing. Minor keyword-coverage gaps keep specificity and trigger quality just below the top anchor.

Dimension	Reasoning	Score
Specificity	Names concrete actions ('Creates a validation project', 'creates a structured project directory with documentation, metadata, and checklists') but stops short of enumerating every artifact, leaving minor coverage gaps relative to the level-5 anchor.	4 / 5
Completeness	Explicitly answers both 'what' (creates a structured project directory with documentation, metadata, and checklists for validating PR changes) and 'when' via a clear 'Use this skill when...' clause listing concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides several natural trigger phrases ('create a validation project', 'test a PR', 'validate a pull request', 'set up a PR validation environment') that users would plausibly say, though it omits common synonyms and shorthand variations.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to vscode-cmake-tools PR validation with niche-specific triggers, giving it a clear role unlikely to collide with other skills.	5 / 5
	Total	18 / 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: 2 missing	Warning

	Total	15 / 16 Passed

Repository: microsoft/vscode-cmake-tools
Path: .github/skills/validation-project/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.