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

81%

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

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.

The content is lean, highly actionable, and sequences each lane operation with explicit validation and feedback loops; the only gap is that all detail lives inline with no external references to offload per-mode specifics.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — e.g. 'CI owns publishing. This skill owns lane maintenance.' — with no padding or explanations of concepts Claude already knows; every section earns its tokens.	5 / 5
Actionability	Fully executable, copy-paste-ready commands with specific flags and arguments throughout (e.g. 'gh workflow run promote.yml --ref next -f dry_run=false', 'npm view platejs dist-tags --json'), covering the common cases for each mode.	5 / 5
Workflow Clarity	Each mode is a clear sequence with explicit validation checkpoints and feedback loops — dry-run-first, 'verify the merge commit with verify-main-to-next-sync', a Hard Stops list, and post-sync verification — exactly matching the destructive/batch validation bar.	5 / 5
Progressive Disclosure	Well-organized with clear section headers (Lanes, Modes, Hard Stops, Handoff) and no nested references, but all content is inlined with no bundle files or one-level-deep references to split out the per-mode detail, leaving minor organization headroom.	4 / 5
	Total	19 / 20 Passed

Description

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

The description is highly specific and distinctive, listing concrete lane-maintenance actions, but it lacks an explicit 'Use when...' trigger clause and leans on technical jargon over natural user phrasing.

Suggestions

Add an explicit trigger clause, e.g. 'Use when maintaining Plate's latest and beta release lanes, promoting beta to stable, syncing main into next, or verifying npm dist-tags.'

Soften jargon like 'autogoal plan' and 're-enter beta' into phrasings users would naturally say, and include common synonyms (e.g. 'prerelease' alongside 'beta').

Keep the strong concrete action list but split the single long sentence so the 'what' and 'when' are visually distinct.

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' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	The 'what' is clearly and concretely stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Relevant domain keywords like 'release lanes', 'latest', 'beta', 'npm', and 'GitHub' appear, but the phrasing is technical jargon (e.g., 'autogoal plan', 're-enter beta') rather than natural terms a user would say, and synonyms are missing.	3 / 5
Distinctiveness Conflict Risk	Targets a clear niche — Plate's latest/beta release lane maintenance — with distinct triggers (npm dist-tags, changeset pre mode, promote.yml) and minimal conflict risk with other skills.	5 / 5
	Total	16 / 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
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: 8f65d77

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.