CtrlK
BlogDocsLog inGet started
Tessl Logo

pr

Creates a pull request for the current branch.

56

Quality

65%

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 ./.claude/skills/pr/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

The content is a strong, fully executable multi-phase workflow with concrete commands, explicit validation checkpoints, and genuine feedback loops for destructive and batch operations. Its only weaknesses are minor: a little bold-emphasis padding and inline subagent prompts that could be externalized into bundle files.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence — it gives commands rather than explaining git/gh — with only minor padding (e.g. the bold MANDATORY emphases and repeated subagent-launch rules could be trimmed), placing it above midpoint but not fully lean.

4 / 5

Actionability

It provides fully executable, copy-paste-ready commands throughout ('git status', 'git diff main...HEAD', 'gh pr create', 'gh pr edit <number> --add-label no-changelog') plus concrete subagent prompts covering the common cases, matching the score-5 anchor.

5 / 5

Workflow Clarity

Five clearly sequenced phases with explicit validation checkpoints and feedback loops — pre-flight error stops, a re-review-after-fix loop for blockers, and the prose-pass/re-diff retry in Phase 1 — which matches the score-5 anchor with explicit validation and error-recovery feedback loops.

5 / 5

Progressive Disclosure

The body is well-structured into clearly signaled phase sections with one external reference (updating-changelogs.md) one level deep; the bulk of subagent-prompt detail is inline rather than split out, which is a minor organization gap keeping it just below a 5.

4 / 5

Total

18

/

20

Passed

Description

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

The description is clear and appropriately third-person but undersells the skill by naming only the final step (PR creation) and omitting the review, stacked-PR, and changelog work it performs. It lacks any 'Use when...' trigger guidance, which caps its completeness at 3.

Suggestions

Expand the description to reflect the skill's full scope, e.g. 'Reviews a branch's diff with parallel subagents and creates a pull request, handling stacked PRs and changelog updates.'

Add an explicit trigger clause: 'Use when the user asks to open a PR, create a pull request, or review a branch before merging.'

Include natural synonyms users say — 'PR', 'pull request', 'gh pr create' — to improve trigger term coverage.

DimensionReasoningScore

Specificity

The phrase 'Creates a pull request for the current branch' names the domain and one concrete action, but lists no companion actions (no mention of review, changelogs, stacked PRs) that the skill actually performs — it reads like the score-2 anchor 'Processes PDF files' transposed to PRs.

2 / 5

Completeness

There is a clear 'what' ('Creates a pull request for the current branch') but no 'when'/'Use when' clause; the guidelines explicitly cap completeness at 3 for a missing explicit trigger guidance.

3 / 5

Trigger Term Quality

It surfaces the natural phrase 'pull request' but offers no synonyms or variations a user would actually say ('PR', 'gh pr', 'open a PR'), matching the score-2 anchor of one or two generic keywords missing common variations.

2 / 5

Distinctiveness Conflict Risk

'Creates a pull request for the current branch' carves a clear niche that is unlikely to fire for unrelated skills; minor overlap risk only with adjacent git/commit skills, matching the mostly-distinct score-4 anchor.

4 / 5

Total

11

/

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.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 1 suspicious

Warning

Total

14

/

16

Passed

Repository
Consensys-Incorporated/ocap-kernel
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.