CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-explainer

Use when creating an approachable, self-contained HTML review aid for a pull request; explaining what changed, why it matters, how it works, and how it fits into the broader system; turning PR diffs, commits, tests, and architecture context into a local `.pr-review/` HTML page for reviewers; or helping reviewers understand complex code changes without dumping the full diff.

73

Quality

90%

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

85%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, actionable skill body with concrete git commands, a usable HTML snippet, explicit verification, and a final checklist as a validation checkpoint. Slight verbosity in the checklist and absence of a full HTML template keep it just short of perfect.

Suggestions

Tighten the 'Final checklist' so it does not restate every earlier section, or move it to a one-level-deep reference file to reduce token cost.

Provide a minimal complete self-contained HTML scaffold (with the .diff/.add/.del CSS) so the output is copy-paste ready rather than implied.

Add a brief validation step in the HTML-output workflow (e.g. open the file / confirm it is self-contained) as an explicit feedback loop alongside the verification section.

DimensionReasoningScore

Conciseness

The body is mostly efficient with well-organized sections and minimal over-explanation, though the checklist repeats earlier section guidance and a few lines (e.g. 'Add diagrams when they reduce cognitive load') could be trimmed, keeping it just below the lean-5 anchor.

4 / 5

Actionability

It provides concrete, executable git commands ('git diff <base>...HEAD --stat', 'git log --oneline -n 10'), a copy-paste HTML diff snippet, and exact verification commands, with only minor gaps (no full HTML scaffolding) versus the fully-copy-paste 5 anchor.

4 / 5

Workflow Clarity

The 'Required workflow' gives a clear sequenced four-step process, the 'Final checklist' serves as an explicit validation checkpoint, and verification is framed with a feedback loop ('if verification was not run, say so clearly and list the recommended commands'), matching the clear-sequence-with-validation anchor.

5 / 5

Progressive Disclosure

Content is well structured with clear section headers and a single self-contained HTML-output focus; no bundle files exist so references are not used, and the inlined HTML snippet and structure are appropriately placed, with only minor organization gaps versus a fully split-reference 5.

4 / 5

Total

17

/

20

Passed

Description

95%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 concrete actions, natural trigger terms, and explicit 'Use when...' guidance covering both what and when. The '.pr-review/ HTML' framing makes it distinct from generic review skills.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'creating an approachable, self-contained HTML review aid', 'explaining what changed, why it matters, how it works', 'turning PR diffs, commits, tests, and architecture context into a local .pr-review/ HTML page' — with only minor gaps in coverage, matching the 'several specific actions; minor gaps' anchor.

4 / 5

Completeness

It explicitly answers both 'what' (create a self-contained HTML review aid from PR diffs/commits/tests) and 'when' via the repeated 'Use when...' clauses with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

It covers natural user phrasing comprehensively, including synonyms ('pull request', 'PR', 'PR diffs', 'commits', 'tests') and concrete artifact terms ('.pr-review/ HTML page', 'reviewers', 'code changes'), aligning with the comprehensive coverage anchor.

5 / 5

Distinctiveness Conflict Risk

The niche — generating a local .pr-review/ HTML explainer page for reviewers — is distinct with specialized triggers (PR diffs, reviewer comprehension) and minimal overlap with general code-review skills.

5 / 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
mastra-ai/mastra
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.