CtrlK
BlogDocsLog inGet started
Tessl Logo

pr

Creates a pull request following Storybook conventions. Use when creating PRs, opening pull requests, or submitting changes for review.

66

Quality

80%

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.

A well-structured, highly actionable reference for creating Storybook PRs with concrete commands, labels, and templates. Its main gap is presenting the work as an implicit rather than explicitly sequenced workflow.

Suggestions

Add an explicit numbered workflow (1. read template → 2. fill sections → 3. choose labels → 4. verify steps locally → 5. run gh pr create --draft) so the sequence and checkpoints are unambiguous.

Tighten the canary-label paragraph to the essential rule, moving the fork-publishing detail to a one-line note.

Make the validation checkpoint more prominent by calling out the "Verify your own steps first" step as a mandatory gate before running the create command.

DimensionReasoningScore

Conciseness

The body is efficient and limited to Storybook-specific conventions Claude would not already know (labels, QA heuristics, Chromatic URLs); only minor stretches like the lengthy canary explanation could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready guidance: a concrete `gh pr create --draft` command, exact label names, a title format with worked examples, and filled Chromatic URL templates covering the common cases.

5 / 5

Workflow Clarity

The flow (title → labels → body from template → draft command) is clear and includes a "Verify your own steps first" checkpoint, but it is presented as a reference rather than an explicit numbered sequence with full validation loops.

4 / 5

Progressive Disclosure

Content is well organized under clear section headers with only a single one-level reference to the repo's `.github/PULL_REQUEST_TEMPLATE.md`; it is over 50 lines so the simple-skill 5 does not apply, but structure is good.

4 / 5

Total

17

/

20

Passed

Description

78%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 clear, third-person description that answers both what and when with concrete, natural trigger phrases. It is slightly narrow on capability specificity and has minor overlap risk with general review skills.

DimensionReasoningScore

Specificity

"Creates a pull request following Storybook conventions" names the domain and one concrete action, but offers only that single action with no broader coverage of the PR workflow.

3 / 5

Completeness

It explicitly states what ("Creates a pull request following Storybook conventions") and when ("Use when creating PRs, opening pull requests, or submitting changes for review") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"creating PRs, opening pull requests, or submitting changes for review" gives good natural keyword coverage with the PR/pull-request synonym pair, though a couple of common phrasings (e.g. "open a PR") are not present.

4 / 5

Distinctiveness Conflict Risk

The Storybook-convention framing gives it a clear niche with mostly distinct triggers, though "submitting changes for review" has minor overlap with general code-review skills.

4 / 5

Total

16

/

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.