CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release-lanes

Promote Plate beta releases, sync main back to next and verify published npm/GitHub state with release authority.

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/release-lanes/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 an unusually strong operational skill: fully executable commands, explicit dry-run and verification checkpoints, feedback loops, and a precise hard-stops section. Its weaknesses are moderate verbosity in the Plite Release Claims section and a monolithic single-file structure where a 220-line skill with a detailed script-behavior contract would benefit from one-level-deep reference files.

Suggestions

Split the sync-script behavior contract ("The script must:" bullet list) and the verify command sets into a reference file (e.g. references/sync-contract.md), keeping SKILL.md as the overview with clearly signaled links.

Tighten the Plite Release Claims section to a single sentence of requirements plus one sentence of prohibition, removing the repeated framing.

Trim meta-commentary in "Core Take" (e.g. "This fast mode is the whole direct sync recipe") to pure instruction.

DimensionReasoningScore

Conciseness

The body is dense with operational specifics (exact gh/git/npm commands, guards, hard stops) and explains nothing Claude already knows. Scored 4 not 5 because the "Plite Release Claims" section repeats its caution across multiple sentences and "Core Take" carries meta-commentary that could be trimmed; not 3 because the excess is minor, not systemic.

4 / 5

Actionability

Fully executable, copy-paste-ready commands throughout: "git worktree add --detach ../plate-sync origin/next", "gh workflow run promote.yml --ref next -f dry_run=true", "PSTACK_RELEASE=1 git push origin next", plus exact JSON field lists for gh run list. The remaining placeholders (<release-run-id>) are appropriately contextual.

5 / 5

Workflow Clarity

Clear sequencing via the mode table, dry-run-before-execute checkpoints in both sync and promote flows, "gh run watch --exit-status" feedback loops, post-publish dist-tag verification, an explicit Hard Stops list, and error-recovery guidance ("If the script stops on files outside known release metadata, do not guess"). Scored 5 not 4 because validation checkpoints are explicit and pervasive rather than minor.

5 / 5

Progressive Disclosure

Sections are well-organized and navigable, but this ~220-line skill is entirely inline with zero reference files; content that could live in separate references (the ~20-line sync-script behavior contract, the verify command sets) is inlined in SKILL.md. Scored 3 not 4 because no content is actually split out; not 2 because structure is good and nothing is buried.

3 / 5

Total

17

/

20

Passed

Description

70%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 specific, concrete, and highly distinctive within its niche, with good natural trigger keywords. Its main weakness is the complete absence of a "Use when..." clause or equivalent trigger guidance, which caps completeness, and the vague trailing phrase "with release authority" adds no informational value.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to promote a Plate beta to latest, sync main into next, or check npm dist-tags and GitHub releases."

Remove the vague "with release authority" phrase, which adds no capability or timing information.

Include common synonyms users might say, such as "publish", "prerelease", "dist-tags", and "latest", to broaden trigger coverage.

DimensionReasoningScore

Specificity

"Promote Plate beta releases", "sync main back to next", and "verify published npm/GitHub state" are several concrete, domain-specific actions. Scored 4 not 5 because coverage has gaps (status inspection, drift recovery, stale-PR cleanup from the body are absent), and not 3 because it clearly exceeds 1-2 actions.

4 / 5

Completeness

The "what" is clear (promote, sync, verify) but there is no "Use when..." clause or equivalent trigger guidance; "with release authority" conveys no usage timing. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

"promote", "beta", "release", "sync", "npm", "GitHub" are natural phrases users would say when needing this skill. Scored 4 not 5 because common synonyms like "publish", "prerelease", "dist-tag", and "latest" are missing; not 3 since keyword coverage is good rather than partial.

4 / 5

Distinctiveness Conflict Risk

"Plate", "beta", "main back to next", and "npm/GitHub state" carve a clear niche with distinct triggers and minimal conflict risk with other skills. Scored 5 not 4 because no realistic overlap exists — the domain is highly specific to this project's release lanes.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.