CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-review-canvas

Generate an interactive PR review walkthrough as an HTML page. Fetches PR data via gh API, categorizes files into core vs mechanical changes, adds reviewer annotations, and renders diffs with moved-code detection. Use when the user pastes a GitHub PR URL and asks for a review, walkthrough, or summary, or says "review this PR".

73

Quality

91%

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 strong, highly actionable skill body with concrete commands, a complete assembly script, and clear sequencing. The main gaps are minor: a few trimmable verbose passages, no explicit output-validation checkpoint, and three referenced companion files that are not shipped in the bundle.

Suggestions

Ship the referenced companion files (styles.css, renderer.js, template.html) in the skill directory, or note where they live — the body instructs Claude to read them, but they are absent from this bundle.

Add an explicit validation checkpoint after assembly (e.g. open the rendered HTML / confirm the server responded) and a brief feedback loop for common failures such as gh not being authenticated or the PR not being found.

Tighten the pseudocode pattern example and drop filler sentences like 'You have full creative freedom' and 'You're not limited to these' to improve token efficiency.

DimensionReasoningScore

Conciseness

Largely efficient and assumes Claude's competence (no explanations of what PRs/HTML/gh are), with nearly all content being actionable reference material; however the ~28-line pseudocode HTML example and a few encouraging transitional sentences ('You have full creative freedom', 'You're not limited to these') could be trimmed.

4 / 5

Actionability

Fully executable guidance throughout: copy-paste-ready 'gh api' commands with exact '--jq' filters, a complete Python assembly script, exact temp file paths, concrete CSS class and JS function tables, and a precise 'python3 -m http.server 8432 --bind 127.0.0.1' serve command.

5 / 5

Workflow Clarity

A clearly sequenced four-step workflow with sub-steps and useful failure-mode guards (the script-safe '</script>' embedding rule, port-fallback guidance), but it lacks an explicit validate-then-proceed checkpoint or feedback loop for cases like gh authentication failure or a non-rendering output.

4 / 5

Progressive Disclosure

Good structure with clearly-signaled one-level-deep references ([styles.css], [renderer.js], [template.html]) and the bulky CSS/JS toolkit appropriately externalized rather than inlined; however those three referenced companion files are not present in the skill bundle, so the navigation is partly dangling, and the long inline pseudocode example could be externalized.

4 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: third-person voice, comprehensive concrete actions, explicit what-and-when with multiple natural trigger phrases, and a distinctive niche. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Fetches PR data via gh API', 'categorizes files into core vs mechanical changes', 'adds reviewer annotations', 'renders diffs with moved-code detection', 'Generate an interactive PR review walkthrough as an HTML page' — giving comprehensive coverage of the workflow.

5 / 5

Completeness

Explicitly answers both what (generate interactive HTML PR review with the listed capabilities) and when ('Use when the user pastes a GitHub PR URL and asks for a review, walkthrough, or summary, or says "review this PR"') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural user terms including synonyms ('review', 'walkthrough', 'summary') and the literal utterance 'review this PR' tied to 'GitHub PR URL', matching how a user would actually request this skill.

5 / 5

Distinctiveness Conflict Risk

A clear niche — interactive HTML PR walkthrough via gh API triggered by a pasted GitHub PR URL — with distinct triggers and minimal overlap risk against generic code-review or git skills.

5 / 5

Total

20

/

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

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository
cursor/plugins
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.