release-lanes

Maintain Plate's latest and beta release lanes end-to-end with an autogoal plan: promote next to main, sync main directly back into next, repair release metadata conflicts, re-enter beta, and verify npm/GitHub release state.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, highly actionable runbook with explicit dry-run/verify checkpoints and a clear lane sequence, weakened only by its monolithic single-file structure with no progressive disclosure into reference files.

Suggestions

Split the detailed 'The script must:' sync contract and per-mode command specifics into a reference file (e.g. references/sync-contract.md) linked from a concise overview to enable one-level-deep progressive disclosure.

Consider extracting the Lanes rules and Hard Stops criteria into a short reference so the top-level SKILL.md reads as an overview pointing to detail.

Dimension	Reasoning	Score
Conciseness	Lean and command-dense throughout — it assumes Claude knows git/changesets/npm/gh and never explains those concepts, with prose limited to justified operational rationale (the merge-commit 'Core Take', Hard Stops).	3 / 3
Actionability	Every mode gives copy-paste-ready executable commands (git fetch, gh pr list, gh workflow run, node tooling/scripts/release-branch-prs.mjs --push, pnpm changeset pre enter beta) with concrete flags and JSON fields to record.	3 / 3
Workflow Clarity	Clear sequenced modes (Status → Sync → Re-enter beta → Promote → Verify) with explicit validation checkpoints ('Dry run first', 'verify the merge commit with verify-main-to-next-sync', 'Do this only after direct sync and verification pass') and a Hard Stops error-recovery boundary.	3 / 3
Progressive Disclosure	Well-sectioned and navigable, but it is a monolithic ~232-line single file with no one-level-deep references, and the detailed sync-script contract and per-mode specifics could be split out rather than kept inline.	2 / 3
	Total	11 / 12 Passed

Description

82%

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 highly specific, niche-scoped description that names concrete lane-maintenance actions and uses natural trigger terms, but it omits an explicit 'Use when' trigger clause so completeness is capped.

Suggestions

Add an explicit 'Use when...' clause stating the trigger conditions (e.g. 'Use when maintaining Plate latest/beta lanes, promoting beta to stable, or syncing main into next') to lift completeness to 3.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'promote next to main', 'sync main directly back into next', 'repair release metadata conflicts', 're-enter beta', and 'verify npm/GitHub release state' — matching the multi-action anchor rather than the single-domain score-2 example.	3 / 3
Completeness	It thoroughly answers 'what' but has no explicit 'Use when...' or equivalent trigger clause, so per the guidelines completeness is capped at 2 even though the 'what' is strong.	2 / 3
Trigger Term Quality	Uses natural maintainer phrasing a user would actually say ('promote', 'sync main ... into next', 're-enter beta', 'verify npm/GitHub release state', 'beta'), giving good coverage rather than just jargon.	3 / 3
Distinctiveness Conflict Risk	It targets a narrow niche (Plate latest/beta lane maintenance with autogoal) with distinct triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	11 / 12 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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: udecode/plate
Path: .agents/skills/release-lanes/SKILL.md
Commit: 45116fd

Reviewed: about 14 hours 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.