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.

79

Quality

100%

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

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a tightly written, highly actionable verification procedure with a clear sequenced workflow, explicit validation fallbacks, and clean organization. It assumes Claude's competence and adds only non-obvious operational detail. No changes needed.

DimensionReasoningScore

Conciseness

The body is lean and dense with operational content — tables, concrete gh commands, and a report template — without explaining concepts Claude already knows (what VS Code, a PR, or gh is). Every section earns its place.

3 / 3

Actionability

Provides copy-paste-ready commands ('gh pr view --json ...', 'gh search code --repo microsoft/vscode ...', 'gh api repos/.../contents/...'), exact search-string patterns, specific source file locations, and a complete output template — fully executable guidance.

3 / 3

Workflow Clarity

A clear numbered 6-step sequence (identify → extract claims → verify → categorize → report → summary) with the claim-category and severity tables acting as checklists, and the 'Unverified' fallback as an explicit validation/feedback loop for this batch verification operation.

3 / 3

Progressive Disclosure

No bundle files exist; the skill is self-contained and well-organized into clear sections (When to Use, Repos to Check, Procedure, Notes) with no nested or deep references, satisfying the well-organized-sections bar.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, trigger-rich, complete, and clearly scoped to a distinct niche. It uses third-person voice and avoids fluff or over-claims. No changes needed.

DimensionReasoningScore

Specificity

Lists multiple concrete verifiable actions — 'setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior' — rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

Explicitly answers both what ('Verify the technical accuracy... against the VS Code source code') and when ('Use when reviewing a docs PR for factual correctness'), satisfying the score-3 anchor.

3 / 3

Trigger Term Quality

Natural terms users would say appear — 'reviewing a docs PR', 'factual correctness', 'verify' — with good coverage and no reliance on opaque jargon.

3 / 3

Distinctiveness Conflict Risk

Targets a narrow, well-defined niche (vscode-docs PR accuracy against specific source repos) with distinct triggers, making conflict with other skills unlikely.

3 / 3

Total

12

/

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