CtrlK
BlogDocsLog inGet started
Tessl Logo

pr

Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.

62

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, well-structured instruction skill: every line carries skill-specific guidance, the output shape is unambiguous, and the sections map cleanly onto the template. The only notable gap is the absence of a worked example showing a filled-in PR body.

DimensionReasoningScore

Conciseness

The ~50-line body is lean throughout: it assumes Claude's competence, never explains what a PR or library is, and every section (template, visual-form mapping, evidence rules, ADR test, triggers, output) carries only novel, skill-specific instruction.

5 / 5

Actionability

Concrete instruction-only guidance throughout — a copyable template, explicit evidence rules ('the exact check that failed before and passes after, quoted from the output itself'), and a three-question ADR decision rule with explicit outcomes. Minor gaps: placeholders like '<output / failing check>' are never filled with a worked example PR body.

4 / 5

Workflow Clarity

The Template fixes the sequence (Summary → Evidence → Reversibility) and the Sections elaborate each in order, with the ADR test acting as an explicit decision checkpoint. Not a 5 because assembly order is implied by section arrangement rather than stated, and there is no explicit feedback loop.

4 / 5

Progressive Disclosure

No bundle files exist and the body is under 50 lines with well-organized sections (Template, Sections, Triggers, Output), satisfying the simple-skill exception for a top score. References to CONTEXT.md and ADRs point to the project's paper trail, not nested skill files.

5 / 5

Total

18

/

20

Passed

Description

63%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 highly specific, buzzword-free description that says exactly what the skill produces, but it omits any trigger guidance and leans on a single keyword ('PR body') without synonyms. Adding an explicit 'Use when...' clause covering PR creation and material updates would raise completeness and trigger quality substantially.

Suggestions

Add an explicit trigger clause, e.g. 'Use when opening or materially updating a PR, or when the platform reviews changes through PRs.'

Include natural keyword variants such as 'pull request', 'PR description', and 'open/update a PR' alongside 'PR body'.

Consider stating the when inline in the frontmatter description rather than only in the body's Triggers section, so the description is self-contained for skill selection.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions covering the whole task — 'Draft a PR body', 'the smallest visual that proves the change', 'evidence consumed from the verify protocol', 'reversibility from the ADR test on the diff', 'glossary language throughout' — with no vague filler, matching the comprehensive-coverage anchor.

5 / 5

Completeness

The 'what' is clear and concrete (drafts a PR body with specified sections), but the description contains no 'Use when...' clause or any equivalent trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

'PR body' is a natural term users would say, but common variations are absent — no 'pull request', 'PR description', 'open a PR', or 'update a PR' — matching 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

PR-body drafting is a mostly distinct niche anchored by ecosystem-specific terms ('OMC's paper trail', 'verify protocol', 'ADR test'), but the generic 'PR' keyword carries minor overlap risk with PR-review or general description-writing skills.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
Yeachan-Heo/oh-my-claudecode
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.