CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

release

Release a new Remotion version

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/release/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.

This is an exceptional operational runbook: fully executable commands, explicit gating and rollback logic, and hard-won environment-specific knowledge throughout. Its only real weaknesses are mild repetition and the lack of any sectioning or file split — the changelog and token-provisioning procedures in particular would be cleaner as separate reference files.

Suggestions

Split the changelog-generation procedure into a references/changelog.md file and the npm token provisioning into its own section or file, keeping SKILL.md as the sequenced overview.

Add a few section headers (e.g. "Preconditions", "Publish", "Promote", "Changelog & GitHub release") so the 55-line flat checklist is scannable mid-release.

State the `op item get "Npmjs" --otp --account remotiondev.1password.com` command once and reference it thereafter instead of repeating it three times.

DimensionReasoningScore

Conciseness

The body is densely packed with project-specific operational knowledge Claude could not know (EOTP token-passing workaround, rbenv PATH issue, zsh $PIPESTATUS caveat, npm dist-tag rollback), so nearly every token earns its place. It is not a 5 because of minor padding: the `op item get "Npmjs" --otp` command is repeated three times and a few rationales could be trimmed.

4 / 5

Actionability

Every step is copy-paste ready with exact commands and flags: `env "npm_config_//registry.npmjs.org/:_authToken=$TOKEN" npm dist-tag add ...`, `grep -oE 'npm_[A-Za-z0-9]{20,}'`, the manifest-generation script, and the npm lifecycle status API endpoint with URL-encoding guidance for scoped packages. Fully executable with common cases (failed publish resume, OTP rollover retry) covered.

5 / 5

Workflow Clarity

The sequence is explicitly gated ("Only after all public `latest` tags are verified", "Once all packages are installable") with validation checkpoints (per-package `npm view` AND `npm pack` before promotion), abort conditions, rollback of recorded previous tags, and retry logic for OTP rollover — full feedback loops for a batch publish operation. Not below 5 because every checkpoint an anchor-5 example requires is present.

5 / 5

Progressive Disclosure

There are no bundle files and no section headers across ~55 dense lines; self-contained chunks that would benefit from being separate files (npm token setup, changelog generation) are fully inlined. This matches 'Some structure but could be better organized; content that should be separate is inline' — the flat checklist is still navigable, so it is above the anchor-2 'minimal structure' case, but the missing headers and inlined changelog sub-procedure keep it below 4.

3 / 5

Total

17

/

20

Passed

Description

53%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 short, unambiguous, and correctly scoped to a distinct niche, but it is barebones: it states only the headline action with no trigger guidance, no synonyms, and no enumeration of the release's concrete steps. It functions but wastes the description's routing and capability-signaling potential.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to release, publish, or ship a new Remotion version."

Enumerate the concrete actions so the scope is visible: publishing npm packages under a temporary dist-tag, promoting latest, publishing Lambda artifacts, and creating the GitHub release/changelog.

Include natural synonyms such as "publish" and "ship" so the description matches how users actually phrase the request.

DimensionReasoningScore

Specificity

"Release a new Remotion version" names the domain and one concrete action but does not enumerate what the release involves (npm publishing, dist-tag promotion, Lambda artifacts, changelog). It matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive'; a 4 would require several specific actions listed.

3 / 5

Completeness

The 'what' is clear (release a new Remotion version) but there is no 'when' guidance at all — no 'Use when...' clause or equivalent trigger phrasing, which per the judging guidelines caps completeness at 3. It is not a 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

"Release" and "version" are natural terms, but common synonyms users would say — "publish", "ship", "cut a release" — are absent. This matches 'Some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor 4.

3 / 5

Distinctiveness Conflict Risk

"Remotion" pins a clear niche with minimal conflict risk for on-topic requests, but the description provides no distinct trigger phrasing, so a bare request like "release it" inside a generic project could overlap with other release/versioning skills. Mostly distinct with minor overlap risk — anchor 4, not 5.

4 / 5

Total

13

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

remotion-dev/remotion

Path

.agents/skills/release/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.