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.

80

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%

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

A well-structured, actionable skill body: a clearly sequenced multi-step workflow with a verification checkpoint, concrete recommendation and report-structure guidance, and clean progressive disclosure via two real bundle references. No basic-concept padding or dead reference chains.

DimensionReasoningScore

Conciseness

The body is lean and directive throughout, assuming Claude's competence; it adds specialized review methodology (objection typing, comparison questions, heuristics) rather than explaining concepts Claude already knows.

3 / 3

Actionability

Concrete, specific guidance throughout — enumerated recommendation buckets ("merge as-is", "merge after specific redesign", "salvage specific pieces"), a 7-item report structure, comparison questions, a verification checklist, and a pointer to the real starter asset.

3 / 3

Workflow Clarity

Eight clearly sequenced workflow steps with an explicit validation checkpoint in Step 8 ("Check: artifact path exists… findings still match… forbidden strings are absent… if tests were not run, say so").

3 / 3

Progressive Disclosure

The body is an overview that signals two real one-level-deep bundle files (references/style-guide.md and assets/html-report-starter.html, both verified present), with style and HTML-starter content appropriately split out rather than inlined.

3 / 3

Total

12

/

12

Passed

Description

100%

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 that states the deliverable and output formats, gives explicit "Use when" triggers with natural phrasing, and occupies a distinct niche. Third-person imperative voice is used throughout, with no over-claims or fluff.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Produce a maintainer-grade PR or contribution report as HTML or Markdown" plus review, explain, compare, and prepare a merge recommendation — rather than vague language.

3 / 3

Completeness

Explicitly answers what ("Produce a maintainer-grade PR or contribution report as HTML or Markdown") and when (explicit "Use when…" triggers), so it is not capped at 2.

3 / 3

Trigger Term Quality

The "Use when asked to deeply review a PR, explain a design, compare systems, or prepare a merge recommendation" clause surfaces natural terms users would actually say.

3 / 3

Distinctiveness Conflict Risk

The PR/contribution-report niche with merge-recommendation triggers is a clear, distinct scope unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.