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

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%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 lean, highly executable wrapper skill with an explicitly gated workflow (dry-run, verify, exit-status watch, readback) and disciplined delegation to the owning release-lanes rule. The only gap is that a couple of peripheral steps (stale-PR close, run-id resolution) lack concrete commands.

Dimension	Reasoning	Score
Conciseness	The body is pure commands, constraints, and stop conditions — 'node tooling/scripts/release-branch-prs.mjs sync-main-to-next --dry-run', 'Do not run autoreview', 'stop only for: dirty checkout... real source conflicts...' — with no concept explanation or padding; every line earns its place.	5 / 5
Actionability	The core workflow is copy-paste ready with full flags and JSON field lists ('gh run list --branch next --limit 10 --json databaseId,name,workflowName...'), but two steps have minor gaps: 'Close stale sync/main-to-next PRs' has no closing command, and '<release-run-id>' placeholders must be filled from earlier output.	4 / 5
Workflow Clarity	The sequence is explicit with validation at every stage: dry-run gate, push, 'verify-main-to-next-sync', 'gh run watch ... --exit-status', npm/GitHub readback, and stale-PR cleanup only after verification passes — plus a dedicated Hard Stops section covering failures and repair limits.	5 / 5
Progressive Disclosure	With no bundle files, the skill is a compact, well-sectioned wrapper (Default Mode, Keep It Fast, Hard Stops, Handoff) that delegates architecture to a single one-level reference: 'loading .agents/rules/release-lanes.mdc' and 'release-lanes owns the release architecture, script contract, hard stops, and handoff shape'.	5 / 5
	Total	19 / 20 Passed

Description

82%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 with explicit what/when structure, natural trigger phrases, and clear differentiation from sibling release skills. Its only weakness is thin action enumeration — it conveys one operation plus exclusions rather than a fuller list of concrete capabilities.

Suggestions

Enumerate the concrete operations the shortcut performs (e.g. dry-run check, direct push, verify, CI watch, npm readback, stale PR cleanup) in the 'what' clause to lift specificity from one action to several.

Add one or two common synonyms for the trigger, such as 'update the beta branch from main' or 'catch up next', to broaden natural-phrase coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and one core concrete action — 'syncing origin/main directly into origin/next through release-lanes' — but the remaining clauses ('without promotion or broad release-lane ceremony') describe what the skill avoids rather than additional actions, so it does not reach the 'several specific actions' anchor.	3 / 5
Completeness	It explicitly answers both 'what' ('One-command shortcut for syncing origin/main directly into origin/next through release-lanes') and 'when' with an explicit 'Use when...' clause listing multiple concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	It covers good natural trigger phrasing — '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' — including both the command form and plain-English variants, but a few plausible synonyms (e.g. 'update next from main', 'catch up the beta branch') are missing.	4 / 5
Distinctiveness Conflict Risk	It carves out a clear niche (main-to-next sync only) and explicitly distinguishes it from adjacent skills ('without promotion', 'not next -> main', 'not broad release-lane ceremony'), giving minimal conflict risk.	5 / 5
	Total	17 / 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/sync-main-to-next/SKILL.md
Commit: babb3c2

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