CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

prep-pr

Use when preparing the current branch for a pull request — resolving the base branch, checking changesets, running builds and reviews, fixing what they find on this branch or in a follow-up pull request rather than filing it, committing the session-metrics card through retro before the push, and opening the PR with the mandatory six-section body, impact first, that the write-pr skill writes.

Quality

86%

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

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

An exceptionally actionable, well-sequenced operational skill: every step carries executable commands, explicit validation, and failure-mode handling. Its one real weakness is token weight — anecdote-laden rationale and thrice-repeated rules inflate a body that already leans on a references/ bundle for the long material.

Suggestions

Trim the historical case studies in Step 5 (the 66-line and +85/-40 anecdotes) to one-line rationale, or move them to a reference file — the operative rules (use $DIFF_BASE, not a gate) stand without them.

State the PR-body skeleton rule once and cross-reference it from Steps 8–9 instead of repeating the 'never rewritten / lost skeleton' warning three times across the opening section.

Move the Step 6 fix-policy bullets and the Step 9 draft-decision tree into references/ alongside workflow-steps.md, leaving the step itself with its dispatch rules and decision table.

DimensionReasoningScore

Conciseness

Every instruction is repo-specific operational detail rather than concepts Claude already knows, but there is genuine padding: historical anecdotes ("added 66 comment lines net while reporting itself as a cleanup", "a reported +85 for a branch actually running -40"), rhetorical flourishes ("an attack map with a timer on it"), and the skeleton-preservation rule stated three separate times. It fits "mostly efficient but could be tightened" rather than the 2 anchor, since no section teaches generic material.

3 / 5

Actionability

Fully executable throughout: copy-paste heredoc blocks for both artefacts, exact git/gh/bun commands with flags and refspecs, verdict-to-agent tables, and exact grep validation patterns — copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Steps 0–9 are explicitly ordered ("Run the steps in order") with explicit validation checkpoints (both grep counts "must print 6"; "the push waits until it prints nothing"; merge-tree exit-code semantics) and feedback loops (fix findings, re-run touched gates, re-check before reporting), including for the failure and no-network paths.

5 / 5

Progressive Disclosure

Clear step structure with one-level-deep references signaled by exact path (workflow-steps, wikilink-check, auditing-defect-classes, issue-filing-example), but the ~750-line body inlines detail that could live in references (Step 6 fix policy, the draft-decision tree) and one chain nests two levels (SKILL.md → workflow-steps.md → registering-a-stack.md). Above the 3 anchor, below the 5 anchor's clean split.

4 / 5

Total

17

/

20

Passed

Description

88%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: it states an explicit trigger, enumerates the workflow's concrete actions end to end, and carves out a distinct orchestration niche. The only weaknesses are a few missing natural synonyms and slight overlap with the adjacent write-pr/review skills it delegates to.

DimensionReasoningScore

Specificity

Enumerates the full pipeline concretely — "resolving the base branch, checking changesets, running builds and reviews, fixing what they find... committing the session-metrics card through retro before the push, and opening the PR with the mandatory six-section body" — with comprehensive coverage rather than the minor gaps of the 4 anchor.

5 / 5

Completeness

An explicit "Use when" trigger plus a concrete, enumerated "what" clearly answers both questions; the 4 anchor's caveat (a "when" that could be more explicit) does not apply.

5 / 5

Trigger Term Quality

Natural phrases a user would say are present ("preparing the current branch for a pull request", "changesets", "reviews", "push", "PR"), but common synonyms such as "open/create a PR" or "ready for review" are missing, so it stops short of the 5 anchor's synonym-level coverage.

4 / 5

Distinctiveness Conflict Risk

The niche — end-to-end branch-to-PR preparation — is distinct and trigger terms are specific, but "running builds and reviews" and the PR-body work overlap the closely related write-pr and review skills it names, which is exactly the 4 anchor's minor overlap risk.

4 / 5

Total

18

/

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

skill_md_line_count

SKILL.md is long (756 lines); consider splitting into references/ and linking

Warning

referenced_paths_exist

Referenced path issues: 7 possibly missing (scripts/changeset-required.sh, scripts/comment-delta.ts, scripts/guard-lint-warnings.sh, scripts/queue-sim.sh, scripts/review-scope.ts, +2 more), 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

englishstreetventures/osn

Path

.claude/skills/prep-pr/SKILL.md

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.