canary

Finds or publishes a pkg.pr.new canary release for a Storybook branch. Use when the user wants the canary package specifier for a branch or needs to trigger the canary workflow manually.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

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

An excellent, fully executable runbook: a clear labeled-PR decision tree with validation checkpoints, failure feedback, and complete gh/curl commands. The only notable flaw is minor redundancy between the Requirements/Monitor progress sections and earlier content.

Suggestions

Remove the duplicated "The canary workflow is publish-canary.yml" line from Requirements — it is already stated in the intro.

Trim or merge the Monitor progress section, since its `gh run list` command duplicates the listing already shown in path B.

Consider stating explicitly in path A how to distinguish "Not run" from an in-progress follow-up (e.g., re-check after a wait), to make the recovery loop fully self-contained.

Dimension	Reasoning	Score
Conciseness	The body is lean and almost entirely repo-specific (label semantics, fork behavior, SHA extraction), assuming Claude's competence with no concept tutorials. Minor trimming is possible: "publish-canary.yml" is restated in Requirements, and the Monitor progress `gh run list` duplicates path B's listing, so it does not fully meet anchor 5's "every token earns its place".	4 / 5
Actionability	Every block is copy-paste-ready executable bash (`git rev-parse --short=7`, `curl -I`, full `gh pr list`/`gh workflow run`/`gh run watch` commands) with variables assigned in-block, and even the tricky RUN_SHA extraction is a real command. Anchor 4 is ruled out because there is no pseudocode or missing detail — edge cases are covered.	5 / 5
Workflow Clarity	The A/B/C decision flow gives an explicit if-then sequence with a pre-check validation (HTTP 200 = canary exists), a watch checkpoint (`gh run watch`), and post-run status interpretation (Released/Failed/Not run) whose failure branch links to the workflow run. Anchor 4 is ruled out because validation checkpoints and error-recovery feedback are both explicit, not implicit.	5 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ absent) and nothing in the body needs extraction to a separate file; sections are clearly headed and each is used by the decision flow. Per the no-external-references case, well-organized sections suffice for the top anchor.	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 strong description: third person, concise, with a clear what and an explicit Use-when clause containing concrete triggers. Its only weakness is slightly thin action coverage and a few missing natural synonyms relative to a maximally comprehensive trigger list.

Dimension	Reasoning	Score
Specificity	"Finds or publishes a pkg.pr.new canary release for a Storybook branch" names the domain (pkg.pr.new, Storybook canary) and two concrete actions (find, publish) that fully cover the skill's scope. It falls short of anchor 5 only because two verbs is thin relative to the multi-step finding/publishing/monitoring the body actually performs.	4 / 5
Completeness	It explicitly answers both what ("Finds or publishes a pkg.pr.new canary release for a Storybook branch") and when ("Use when the user wants the canary package specifier for a branch or needs to trigger the canary workflow manually") with concrete trigger phrases. Anchor 4 is ruled out because the when-clause is explicit and specific, not merely present.	5 / 5
Trigger Term Quality	"canary release", "pkg.pr.new", "canary package specifier", and "trigger the canary workflow manually" are the natural phrases a user would say for this need. Not anchor 5 because common variations like "install the canary", "pr.new", or "unreleased build" are absent.	4 / 5
Distinctiveness Conflict Risk	The pkg.pr.new/Storybook canary niche is highly specific with distinct triggers ("canary package specifier", "trigger the canary workflow"), so overlap with other skills is minimal. It is not a 4 because no closely-related-skill overlap is evident.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: storybookjs/storybook
Path: .agents/skills/canary/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.