A lean, highly actionable workflow document: concrete commands, a real bundle script, and explicit user-interaction steps, all with minimal token overhead. The only weaknesses are a small sequencing wrinkle in the context-gathering step and no error-recovery guidance for the PR-creation step itself.

Dimension	Reasoning	Score
Conciseness	Every section carries project-specific facts Claude cannot infer (labels, template path, base-detection order, conventions); there is no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Fully executable guidance: complete `gh pr create` command with heredoc, concrete git commands, a real script path that exists in the bundle, an explicit label table, and named AskQuestion prompts with options.	5 / 5
Workflow Clarity	A clear six-step sequence with feedback checkpoints ("Tell the user the result", "Verify the available labels with the PR template", documented fallback to `next`). Docked one point for the step-1 "(after step 2)" cross-dependency and the absence of any failure handling for the `gh pr create` step.	4 / 5
Progressive Disclosure	Well-organized sections in a single page with one-level-deep references only: a real `scripts/detect-base-branch.sh` file and clearly signaled cross-skill pointers (`pr`, `canary`). The inline label table is appropriately verified against the PR template rather than spun off prematurely.	5 / 5
	Total	19 / 20 Passed

Description

87%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 concise, third-person description that clearly states a single concrete capability and provides explicit, natural trigger phrases including the slash command. It fully answers both what and when with only minor gaps in trigger-term synonyms.

Dimension	Reasoning	Score
Specificity	"Opens a pull request from the current branch using the PR template" gives one concrete action with two specific qualifiers (source branch, template) — above anchor 3's minimal coverage but not a multi-action comprehensive list like anchor 5.	4 / 5
Completeness	Explicitly answers both what ("Opens a pull request from the current branch using the PR template") and when ("Use when the user asks to open a PR, create a pull request, or invokes /open-pr") with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	"open a PR, create a pull request, or invokes /open-pr" covers the natural phrasings plus the slash command, but misses common variants such as "submit a PR" — good coverage with a few gaps.	4 / 5
Distinctiveness Conflict Risk	PR creation is a clear niche with distinct, unambiguous triggers; the description is unlikely to fire for unrelated skills.	5 / 5
	Total	18 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	13 / 16 Passed

Repository: storybookjs/storybook
Path: .agents/skills/open-pr/SKILL.md
Commit: dc9b30e

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.