upload-element-previews

Upload a Remotion Element's preview assets to remotion.media and replace local preview URLs. Use when given an Element slug, or when exactly one Element's preview assets are present in the current worktree.

Quality

85%

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

87%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 tight, executable single-purpose skill with a clear command and step sequence. Its main gap is the absence of a validation/verification step before destructive cleanup, which caps workflow clarity despite otherwise strong sequencing.

Suggestions

Add a validation checkpoint after upload (e.g., confirm the printed remotion.media URLs exist and that image/posterUrl/videoUrl were successfully replaced) before step 5 deletes local review assets.

Include a brief error-recovery loop: what to do if the upload command fails or prints no URLs (re-run, check source flag) before proceeding to URL replacement.

Make the destructive/commit boundary explicit by verifying the diff only touches the intended preview URL fields before committing and pushing.

Dimension	Reasoning	Score
Conciseness	Lean ~22-line body that assumes Claude's competence; the one explanatory line about random URL postfixes earns its place by clarifying non-obvious branch-isolation behavior rather than restating known concepts.	5 / 5
Actionability	Provides a copy-paste-ready executable command ('cd packages/docs; bun run upload-element-preview --element=... --source=...') plus concrete follow-up actions (replace image/posterUrl/videoUrl, delete assets, commit and push).	5 / 5
Workflow Clarity	Steps 1-6 are clearly sequenced, but this is a destructive/batch operation (deleting local review assets, then committing/pushing) with no validation checkpoint confirming the upload succeeded or URLs were replaced before local files are deleted — capping clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	A short, well-organized single-file skill under 50 lines with no external references needed; numbered steps and a code block provide clean structure, qualifying for the simple-skill exception at anchor 5.	5 / 5
	Total	18 / 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 focused, well-constructed description that clearly states what the skill does and gives explicit, concrete trigger conditions. It is slightly light on the breadth of actions described, which keeps specificity at the midpoint.

Dimension	Reasoning	Score
Specificity	Names the Remotion Element domain and two concrete actions ('Upload a Remotion Element's preview assets to remotion.media' and 'replace local preview URLs'), but the coverage is not comprehensive enough for anchor 4.	3 / 5
Completeness	Explicitly answers both what (upload previews to remotion.media, replace local URLs) and when ('Use when given an Element slug, or when exactly one Element's preview assets are present'), matching the concrete-trigger anchor 5.	5 / 5
Trigger Term Quality	Good natural-trigger coverage with concrete conditions ('given an Element slug', 'exactly one Element's preview assets are present in the current worktree'); a few common phrasings users might say are absent, so it sits below anchor 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Remotion Element previews on remotion.media) with distinct, domain-specific triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: remotion-dev/remotion
Path: .agents/skills/upload-element-previews/SKILL.md
Commit: 6f4e0d5

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