CtrlK
BlogDocsLog inGet started
Tessl Logo

pr-report

Produce a maintainer-grade PR or contribution report as HTML or Markdown. Use when asked to deeply review a PR, explain a design, compare systems, or prepare a merge recommendation.

69

Quality

83%

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

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

Well-structured, lean instruction skill with a clear sequenced workflow, concrete actionable buckets, and properly signaled one-level-deep bundle references. Solid across all dimensions with only minor tightening opportunities.

DimensionReasoningScore

Conciseness

Mostly lean imperative directives with no padding over concepts Claude already knows; minor redundancy between the "Default posture" / "When to Use" sections and the description keeps it from a 5.

4 / 5

Actionability

Concrete, specific guidance throughout — numbered report structure, explicit recommendation buckets, comparison questions, and a verify checklist — appropriate for an instruction-only skill; minor gaps in fully worked output examples.

4 / 5

Workflow Clarity

A clear 8-step sequence ending in an explicit "Verify before handoff" checkpoint; the verify step is a checklist rather than a validate→fix→retry feedback loop, which is appropriate for report generation but leaves a minor gap.

4 / 5

Progressive Disclosure

Overview stays in SKILL.md while presentation rules and HTML scaffolding are split into verified one-level-deep references (references/style-guide.md, assets/html-report-starter.html), both clearly signaled; the fairly long inline heuristics section keeps it just short of a 5.

4 / 5

Total

16

/

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 description: concrete actions, explicit "Use when" trigger guidance, and a distinct niche. Only minor trigger-term breadth keeps it from a perfect sweep.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Produce a ... report as HTML or Markdown", "deeply review a PR", "explain a design", "compare systems", "prepare a merge recommendation" — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both what ("Produce a maintainer-grade PR or contribution report as HTML or Markdown") and when ("Use when asked to deeply review a PR, explain a design, compare systems, or prepare a merge recommendation") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of natural phrases users say ("deeply review a PR", "explain a design", "compare systems", "merge recommendation"), though a few common variants like "should I merge this?" are not present.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (maintainer-grade PR/contribution reports) with distinct triggers, minimal overlap risk with other 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
paperclipai/paperclip
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.