CtrlK
BlogDocsLog inGet started
Tessl Logo

pr

Creates a pull request for the current branch.

50

Quality

55%

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

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.

The skill body is a well-structured, highly actionable workflow with explicit validation checkpoints and a single clearly signaled external reference. It is concise and executable, with only minor padding and a few implicit error-recovery loops.

DimensionReasoningScore

Conciseness

The body is mostly efficient: concrete git/gh commands and tight subagent prompts without re-explaining git concepts Claude knows, with only minor padding such as the bolded 'MANDATORY — DO NOT SKIP' commentary that could be trimmed.

4 / 5

Actionability

It provides concrete, executable commands at nearly every step (git status, git merge-base, git diff, gh pr create, gh pr edit --add-label) plus specific per-subagent review prompts, covering the common cases copy-paste ready.

5 / 5

Workflow Clarity

The five-phase sequence is explicit with checkpoints (pre-flight stops, blocker triage with fix/proceed/abort, validation-gated review before creation); it falls just short of 5 because some error-recovery loops after triage are implicit rather than fully spelled out.

4 / 5

Progressive Disclosure

Content is well organized into clearly headed phases with one clearly signaled one-level reference to docs/contributing/updating-changelogs.md; no bundle files exist so bulk is appropriately inline, with only minor gaps in signaling deeper detail.

4 / 5

Total

17

/

20

Passed

Description

30%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 concise and unambiguous about its single purpose but fails to provide any usage triggers or expanded keyword coverage. It answers 'what' clearly while leaving 'when' entirely absent.

Suggestions

Add a 'Use when...' clause naming the natural triggers users say, e.g. 'Use when the user asks to open, create, or submit a PR / pull request.'

Include synonyms and trigger terms like 'PR', 'pull request', and 'open a PR' to improve trigger-term quality and conflict resistance.

Optionally note the stacked-PR and automated-review capabilities so the description reflects the skill's full scope, not just creation.

DimensionReasoningScore

Specificity

The phrase 'Creates a pull request for the current branch' names the domain and one concrete action (create PR) but offers no further detail; it is slightly above pure vagueness yet clearly below the multi-action anchors.

2 / 5

Completeness

It provides a clear 'what' but entirely omits any 'Use when...' / 'when' trigger guidance, which the guidelines cap at 3; combined with minimal action coverage it lands at 2.

2 / 5

Trigger Term Quality

It contains only the generic phrase 'pull request'; it lacks the natural trigger phrases users say ('PR', 'open a PR', 'make a pull request') and any synonyms, sitting between anchor 1 and anchor 3 but noticeably below the midpoint.

2 / 5

Distinctiveness Conflict Risk

'Creates a pull request for the current branch' is a fairly distinct niche with low conflict risk, though the brevity leaves minor overlap with general git-workflow skills.

4 / 5

Total

10

/

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
MetaMask/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.