Name: pr-readiness
Rating: 72 (1 reviews)
Author: microsoft

pr-readiness

Verify that a pull request into microsoft/vscode-cmake-tools meets contribution requirements. Use when preparing, reviewing, or finalizing a PR to check for a descriptive title, a meaningful description, a properly formatted CHANGELOG entry, code correctness, regression risks, adherence to existing patterns, and whether documentation updates are needed.

Quality

89%

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

86%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 review checklist with concrete file paths, helpers, and formats throughout. The main improvement room is minor conciseness redundancy and adding explicit validation checkpoints to the review workflow.

Suggestions

Tighten redundancy between the eight detailed checklist sections and the 'Applying This Skill' summary, which largely restate the same eight checks.

Add an explicit 'verify before finalizing' checkpoint in the Applying This Skill workflow (e.g., re-confirm CHANGELOG entry and test coverage are complete before marking the PR ready) to strengthen validation feedback.

Consider folding the cross-cutting 'test coverage' guidance so it lives in one place rather than being referenced from both section 5 and section 7.

Dimension	Reasoning	Score
Conciseness	The body is dense and actionable with minimal concept explanation, but the eight checklist sections plus the 'Applying This Skill' restatement carry some redundancy that could be trimmed.	4 / 5
Actionability	It provides concrete, executable guidance throughout — exact file paths (src/expand.ts, CHANGELOG.md), helper names (rollbar.invokeAsync, logging.createLogger), commands (yarn backendTests), and copy-paste-ready CHANGELOG entry formats with real link templates.	5 / 5
Workflow Clarity	The 'Applying This Skill' section gives a clear eight-step sequenced checklist, and section 7 details test-review guidance; however, the workflow is a review pass rather than a destructive/batch operation, so it lacks explicit validation-feedback checkpoints that would lift it to a 5.	4 / 5
Progressive Disclosure	Content is organized into well-signaled sections with external detail pointers (docs/cmake-settings.md, .github/copilot-instructions.md, EXTENSIBILITY.md) kept one level deep; no bundle files exist, and the single-file structure is appropriate for the scope.	5 / 5
	Total	18 / 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 answers both 'what' and 'when' and is tightly scoped to a concrete repo workflow. Trigger-term coverage is the only slight gap, missing a few natural synonyms a user might say.

Dimension	Reasoning	Score
Specificity	The description enumerates multiple concrete review actions — 'descriptive title', 'meaningful description', 'properly formatted CHANGELOG entry', 'code correctness', 'regression risks', 'adherence to existing patterns', and 'documentation updates' — giving comprehensive coverage rather than vague language.	5 / 5
Completeness	It explicitly states both what the skill does ('Verify that a pull request ... meets contribution requirements') and when to use it ('Use when preparing, reviewing, or finalizing a PR') with concrete trigger context.	5 / 5
Trigger Term Quality	Natural trigger phrases like 'preparing, reviewing, or finalizing a PR' map well to what a user would say, but coverage lacks common synonyms such as 'pull request checklist' or 'CHANGELOG review', leaving a few natural terms missing.	4 / 5
Distinctiveness Conflict Risk	The scope is tightly bound to a single repository's contribution process (microsoft/vscode-cmake-tools PR requirements), giving it a clear niche with minimal overlap risk against general skills.	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 missing	Warning

	Total	15 / 16 Passed

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