CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-review-canvas

Render a PR diff review as a Cursor Canvas that groups changes by reviewer importance, separates boilerplate from core logic, and highlights tricky or unexpected code. Use when reviewing a pull request, summarizing a diff for review, or when the user asks for a PR review canvas, diff walkthrough, or change-set overview.

68

Quality

82%

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

68%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-organized, mostly lean body with concrete commands and clear topical sections, but the workflow is presented as guidance sections rather than an explicitly numbered sequence with validation checkpoints. Progressive disclosure is handled via clearly signaled external references rather than in-bundle files.

Suggestions

Number the core workflow as an explicit ordered sequence (read prereqs → gather diff → group → distill → trace → callouts → render) so the steps and their ordering are unambiguous.

Add a validation/self-check step for the finished canvas (e.g. confirm every changed file appears in exactly one section, and that callouts are reserved for genuinely tricky items) to create a feedback loop on the output.

Illustrate the pseudocode-distillation and example-trace techniques with one short worked example each, so the guidance is copy-paste actionable rather than described in the abstract.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, avoiding explanations of concepts Claude already knows, though a few prose passages (e.g. the 'Be creative' section) could be trimmed slightly without losing signal.

4 / 5

Actionability

Provides concrete guidance including the executable `gh pr diff <pr>` command and specific file paths to read, but the pseudocode/example-trace techniques are described rather than shown with a worked example.

4 / 5

Workflow Clarity

Sections imply a sequence (prereqs → gather → group → distill → trace → callouts) and include one good checkpoint ('If the user didn't provide a PR link, stop and ask'), but steps are not crisply numbered and there is no validation/feedback loop on the produced canvas.

3 / 5

Progressive Disclosure

The SKILL.md acts as a lean overview and clearly signals one-level-deep references to the canvas SKILL.md and SDK .d.ts files for detail; no bundle files exist in ./references, ./scripts, or ./assets to verify, and the referenced paths live outside this skill's bundle.

4 / 5

Total

15

/

20

Passed

Description

96%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 with clear concrete actions and comprehensive natural trigger phrases covering both what and when. The only weak spot is a slightly broad 'summarizing a diff for review' trigger that could overlap with general code-review skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Render a PR diff review as a Cursor Canvas', 'groups changes by reviewer importance', 'separates boilerplate from core logic', 'highlights tricky or unexpected code' — giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what (render/group/separate/highlight) and when ('Use when reviewing a pull request, summarizing a diff for review, or when the user asks for a PR review canvas, diff walkthrough, or change-set overview') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Covers natural trigger phrases and synonyms users would actually say — 'reviewing a pull request', 'PR review canvas', 'diff walkthrough', 'change-set overview', 'summarizing a diff' — with good variation.

5 / 5

Distinctiveness Conflict Risk

The canvas-rendering niche and 'PR review canvas'/'diff walkthrough' triggers are distinct, but 'summarizing a diff for review' is broad enough to risk minor overlap with a generic code-review or PR-summarization skill.

4 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.