promote-beta

Compatibility entrypoint for beta promotion. Prefer release-lanes for end-to-end latest/beta lane maintenance.

Quality

58%

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

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/promote-beta/SKILL.md

Quality

Content

72%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 body is a well-structured, concise routing shim with executable quick commands and clear navigation to the owning release-lanes skill. Its main weakness is the lack of validation/verification checkpoints around the destructive push and workflow-run operations.

Suggestions

Add an explicit validation step before the destructive 'sync-main-to-next --push' and 'gh workflow run promote.yml' commands (e.g. run the --dry-run variant first and confirm output).

Trim or relocate the 'old split was too manual' history paragraph so the routing instruction stays front and center.

Clarify the fallback behavior when the referenced .agents/rules/release-lanes.mdc file is absent, so the redirect is robust.

Dimension	Reasoning	Score
Conciseness	The body is lean with sectioned route guidance and copy-paste commands; the only over-explanation is the 'The old split was too manual…' history paragraph, which could be trimmed, placing it at efficient-with-minor-padding rather than fully lean.	4 / 5
Actionability	Concrete executable commands are provided (node create-goal-scratchpad.mjs, gh workflow run promote.yml, sync-main-to-next --dry-run/--push), but the primary instruction 'load .agents/rules/release-lanes.mdc and follow that skill' is a redirect rather than executable code, leaving minor gaps.	4 / 5
Workflow Clarity	A rough sequence exists (route or run quick commands), but the destructive/batch operations (sync-main-to-next --push, gh workflow run promote.yml) have no validation or verification checkpoint before execution, so per the rubric cap workflow_clarity cannot exceed 3.	3 / 5
Progressive Disclosure	The skill is under 50 lines with well-organized sections (# Promote Beta, ## Route, ## Quick Commands) and a clearly signaled one-level-deep reference to release-lanes.mdc, matching the simple-skill exception for a top score with no bundle files needed.	5 / 5
	Total	16 / 20 Passed

Description

45%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 clearly states the skill's purpose as a compatibility shim and redirects to release-lanes, but it lacks an explicit trigger clause and relies on internal jargon. It is adequate for routing but not exemplary as a standalone description.

Suggestions

Add an explicit 'Use when older prompts say promote-beta or when asked to promote to beta' trigger clause so the 'when' is concrete.

Replace some internal jargon ('autogoal-backed lane', 'latest/beta lane maintenance') with natural user-facing phrasing or synonyms.

State the concrete action the skill takes (e.g. 'Routes promote-beta requests to the release-lanes skill') rather than only describing what it is.

Dimension	Reasoning	Score
Specificity	Quotes "Compatibility entrypoint for beta promotion" and "Prefer release-lanes for end-to-end latest/beta lane maintenance" — it names the domain (beta promotion, lane maintenance) but the only 'actions' are routing/preference, which are minimal and generic rather than concrete capabilities.	2 / 5
Completeness	The 'what' is clear (a compatibility entrypoint that defers to release-lanes) but there is no explicit 'Use when...' trigger clause, so per the guideline completeness is capped at 3 with 'when' only weakly implied.	3 / 5
Trigger Term Quality	"beta promotion" is a reasonably natural phrase a user might say, but the surrounding terms ("release-lanes", "latest/beta lane maintenance") are internal jargon with no synonyms or file extensions, so coverage is partial rather than comprehensive.	3 / 5
Distinctiveness Conflict Risk	The phrase "Prefer release-lanes" signals deliberate overlap with the closely related release-lanes skill, so while the beta-promotion niche is somewhat specific, conflict risk with its sibling skill remains material.	3 / 5
	Total	11 / 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/promote-beta/SKILL.md
Commit: cce36d3

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.