CtrlK
BlogDocsLog inGet started
Tessl Logo

open-pr

Opens a pull request from the current branch using the PR template. Use when the user asks to open a PR, create a pull request, or invokes /open-pr.

68

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 body is an executable, well-sequenced PR-creation workflow with concrete commands and appropriately signaled one-level references to related skills and a bundled script. It could improve by adding an explicit failure-recovery loop and trimming the inlined label table.

Suggestions

Add a brief feedback loop for the `gh pr create` step (e.g., what to do on authentication or base-branch errors) to raise workflow_clarity.

Replace or shorten the inlined label-options table by pointing Claude to read the exact options from `.github/PULL_REQUEST_TEMPLATE.md`, reducing duplication.

Trim the detect-base-branch tie-break prose to the essentials, since the script already encodes the behavior.

DimensionReasoningScore

Conciseness

The body is lean with numbered steps, code blocks, and a compact label table, avoiding explanations of concepts Claude already knows; only minor passages like the tie-break detail could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready commands throughout (git status/diff, the detect-base-branch script, a full `gh pr create` invocation with flags, AskQuestion prompts, and a concrete label-options table) covering the common cases.

5 / 5

Workflow Clarity

Six clearly sequenced steps with checkpoints ("Verify the available labels", "Tell the user the result", "Push first if needed") give a clear sequence, but there is no explicit error-recovery feedback loop for command failures.

4 / 5

Progressive Disclosure

Content is well-organized into workflow steps and Notes with one-level-deep, clearly signaled references (the `pr` and `canary` skills, the PR template, and the real detect-base-branch.sh script), though the label table is inlined rather than derived from the referenced template.

4 / 5

Total

17

/

20

Passed

Description

82%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, third-person, and cleanly answers both what and when with concrete, natural trigger phrases including a slash-command invocation. It is slightly light on breadth of concrete actions, naming essentially one operation rather than a list.

DimensionReasoningScore

Specificity

"Opens a pull request from the current branch using the PR template" names the domain and one concrete action with a detail, but does not list several distinct actions, matching the 1-2 concrete actions anchor.

3 / 5

Completeness

It explicitly states what it does ("Opens a pull request from the current branch using the PR template") and when to use it ("Use when the user asks to open a PR, create a pull request, or invokes /open-pr") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"open a PR", "create a pull request", and "/open-pr" give good natural keyword coverage users would actually say, though a few synonymous phrasings are absent.

4 / 5

Distinctiveness Conflict Risk

The narrow PR-creation niche plus the explicit "/open-pr" invocation trigger make it clearly distinct with minimal conflict risk against other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
storybookjs/storybook
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.