pr-snapshot-release

Guide a Mastra maintainer through publishing an npm snapshot from a pull request or a specified repository branch. Use when asked to release, publish, or create a PR snapshot, branch snapshot, canary package build, or branch-specific npm tag. Performs source and branch preflight checks, requires confirmation before the irreversible publish, dispatches the existing Publish to npm workflow, monitors it, and reports installable package tags.

Quality

98%

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

96%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 tightly written, highly actionable procedural skill with excellent validation and feedback loops around an irreversible npm publish. The only soft spot is progressive disclosure, which is constrained by the skill being a single self-contained workflow with no bundle files rather than by poor organization.

Suggestions

If any per-package version-resolution detail or the npm-publish workflow's input contract grows, move it into a references/ file and link to it from step 6 to exercise true progressive disclosure.

Consider extracting the custom-tag derivation rules (kebab-case, examples, reserved tags) into a short reference so step 3 stays a pure pointer.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — it never explains concepts Claude already knows (gh, npm, git) and every sentence is a workflow-specific constraint or guardrail (e.g., 'the snapshot job does not honor' dry_run) that earns its place.	5 / 5
Actionability	Fully executable, copy-paste ready commands with real flags — 'gh workflow run npm-publish.yml ... -f publish_type=snapshot -f tag="$tag"' — and the final install example uses actual values ('pnpm add @mastra/core@agent-builder @mastra/server@agent-builder').	5 / 5
Workflow Clarity	Six clearly sequenced steps with explicit validation checkpoints and feedback loops for the irreversible publish: SHA assertions, 'Re-run this comparison immediately before dispatch', an explicit confirmation gate, run-URL verification, and 'Do not claim success... until the workflow and every included npm tag lookup succeed'.	5 / 5
Progressive Disclosure	Well organized into six numbered sections with no inlined reference material that belongs elsewhere, but it is a self-contained ~109-line workflow with no external references, so it does not meet the 5-anchor's emphasis on well-signaled one-level-deep references or content split across files.	4 / 5
	Total	19 / 20 Passed

Description

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

An excellent description: third-person voice, concrete actions, explicit 'Use when' trigger guidance with multiple natural synonyms, and a sharply defined niche that minimizes conflict risk. No vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Performs source and branch preflight checks', 'requires confirmation before the irreversible publish', 'dispatches the existing Publish to npm workflow', 'monitors it', 'reports installable package tags' — giving comprehensive coverage of the workflow rather than just 1-2 actions.	5 / 5
Completeness	Explicitly answers both 'what' (the publish/monitor/report workflow) and 'when' via a clear 'Use when asked to release, publish, or create a PR snapshot...' clause with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrasing is comprehensively covered with synonyms — 'release, publish, or create a PR snapshot, branch snapshot, canary package build, or branch-specific npm tag' — matching the anchor's emphasis on synonyms and natural terms.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche — a Mastra maintainer publishing npm snapshots from a PR or branch — with distinct triggers (canary package build, branch-specific npm tag) and minimal overlap risk with other skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: mastra-ai/mastra
Path: .mastracode/skills/pr-snapshot-release/SKILL.md
Commit: 3b0d190

Reviewed: 5 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.