CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-review

Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode and microsoft/vscode-copilot-chat. Use when reviewing a docs PR for factual correctness — setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.

71

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

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 review workflow with concrete commands, source locations, and a report template. It is concise and clearly sequenced; the main opportunities are minor tightening and slightly richer validation/checkpoint framing.

Suggestions

Add an explicit verification checkpoint near step 3 — e.g., a short checklist confirming each claim was matched to a source line before categorizing — to strengthen workflow_clarity toward 5.

Trim the dual claims/source-location tables in step 2 and 3 by merging overlapping rows, reducing token load without losing coverage.

Consider extracting the report template (step 5) into a short bundled reference file so the main body reads as an overview, improving progressive_disclosure.

DimensionReasoningScore

Conciseness

Lean and table-driven with no basic-concept padding; it assumes Claude's competence. A few enumeration-heavy sections (e.g., the claims and source-location tables) could be tightened slightly.

4 / 5

Actionability

Provides copy-paste-ready commands (gh pr view/diff, gh search code, gh api with concrete endpoints), exact source-file locations, and a full Markdown report template covering common cases.

5 / 5

Workflow Clarity

A clearly sequenced six-step procedure with explicit decision points (skip cosmetic changes, mark Unverified rather than fail). This is a review task rather than a destructive/batch operation, so the validation cap does not apply; minor checkpoint gaps keep it below 5.

4 / 5

Progressive Disclosure

No bundle files exist; the skill is a single self-contained file organized into clear sections (When to Use, Repos to Check, Procedure, Notes). Structure is good and content is appropriately placed, though it exceeds the simple-skill line-count threshold for a top score.

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 both capability and trigger conditions with concrete examples of verifiable claims. Only minor weakness is slightly limited natural-synonym coverage in the trigger phrasing.

DimensionReasoningScore

Specificity

Lists multiple concrete verification actions — "setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior" — giving comprehensive coverage of what the skill checks.

5 / 5

Completeness

Explicitly answers both what ("Verify the technical accuracy of a vscode-docs pull request against the VS Code source code") and when ("Use when reviewing a docs PR for factual correctness") with concrete trigger phrasing.

5 / 5

Trigger Term Quality

"Use when reviewing a docs PR for factual correctness" plus the enumerated claim categories give good keyword coverage, but common natural synonyms like "fact-check" or "validate" are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

Scoped to a narrow niche — vscode-docs PRs verified against microsoft/vscode and microsoft/vscode-copilot-chat source — with triggers unlikely to fire for unrelated skills.

5 / 5

Total

19

/

20

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
microsoft/vscode-docs
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.