sync-main-to-next

One-command shortcut for syncing origin/main directly into origin/next through release-lanes. Use when the user says sync-main-to-next, asks to sync main into next, asks after a stable release what sync is needed, or wants the fastest safe beta lane catch-up without promotion or broad release-lane ceremony.

Quality

95%

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

100%

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

A tightly written, single-purpose wrapper skill that is copy-paste actionable, clearly sequenced with validation checkpoints, and appropriately defers detail to the release-lanes reference. It does not pad with concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: concrete bash commands, no concept explanations Claude already knows, and every section (Keep It Fast, Hard Stops, Handoff) earns its tokens; it explicitly defers the release architecture to release-lanes rather than restating it.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands (node release-branch-prs.mjs sync-main-to-next --dry-run/--push, gh run watch <id> --exit-status, npm view platejs ...); placeholders like <release-run-id> are reasonable and filled from prior output.	3 / 3
Workflow Clarity	Clear sequence (dry-run -> push -> verify -> watch workflows -> read back -> close stale PRs) with explicit validation checkpoints (verify-main-to-next-sync, gh run watch --exit-status, npm/GitHub readback mismatch) and a Hard Stops section giving error-recovery guidance for this semi-destructive push.	3 / 3
Progressive Disclosure	Well-organized into clear sections and appropriately delegates detail one level deep to .agents/rules/release-lanes.mdc ('release-lanes owns the release architecture'), avoiding duplication; no deeply nested references and no bundle files to mis-signal.	3 / 3
	Total	12 / 12 Passed

Description

90%

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, third-person description with explicit what-and-when triggers and distinct, natural-sounding invocation cues. Its only weakness is that it names a single concrete action rather than a list of several, which caps specificity.

Dimension	Reasoning	Score
Specificity	Names a concrete action ('syncing origin/main directly into origin/next through release-lanes') but describes a single action rather than multiple specific concrete actions, so it does not reach the 'lists multiple specific concrete actions' anchor.	2 / 3
Completeness	Clearly answers both what ('One-command shortcut for syncing origin/main directly into origin/next') and when (explicit 'Use when the user says sync-main-to-next, asks to sync main into next, ...') with explicit triggers.	3 / 3
Trigger Term Quality	Covers natural trigger phrases a user would say — 'sync-main-to-next', 'asks to sync main into next', 'what sync is needed' after a stable release, 'beta lane catch-up' — giving good coverage of natural terms.	3 / 3
Distinctiveness Conflict Risk	A clear niche (main-to-next sync via release-lanes) with distinct triggers and an explicit disambiguator ('without promotion', i.e. not next-to-main), making conflict with other skills unlikely.	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/sync-main-to-next/SKILL.md
Commit: 45116fd

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