update-remotion-rust-ffmpeg

Update Remotion's ffmpeg-next Git revision to a published rust-ffmpeg commit, refresh Cargo.lock, rebuild all supported compositor binaries, validate the monorepo, and open a draft pull request. Use for the final step of the rust-ffmpeg binary update chain.

Quality

82%

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

88%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, highly actionable workflow with strong validation checkpoints and feedback loops appropriate to a destructive/batch binary-rebuild task. Structure is clean and references are one level deep; the only minor gap is a few guardrail sentences that could be trimmed.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — concrete commands with no padding or concept explanations — though a few guardrail sentences ('Do not rebase, reset, or overwrite unrelated work', 'Do not substitute a native-only build') could be slightly tightened.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout — 'cargo update -p ffmpeg-next', 'bun install --frozen-lockfile', 'bun run build-all', 'git diff --check', 'objdump -p packages/compositor-win32-x64-msvc/remotion.exe', 'gh pr create --draft --body-file' — covering the common cases concretely.	5 / 5
Workflow Clarity	A clearly sequenced multi-step process (prepare worktree → update Cargo/rebuild → commit/push/PR → finish) with explicit validation checkpoints and stop conditions — 'Stop on any pre-existing change', 'Verify in Cargo.lock that...', 'Stop if unrelated tracked files changed', 'require msvcrt.dll and reject api-ms-win-crt-*', 'If the push is rejected, stop and report it'.	5 / 5
Progressive Disclosure	Well-organized into clear section headers with one-level-deep external references to sibling skills ([../pr/SKILL.md], [../pr-name/SKILL.md]); no bundle files exist so content is appropriately self-contained, with only minor organization gaps.	4 / 5
	Total	18 / 20 Passed

Description

76%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 specific, action-rich description with a clear niche and explicit (if narrow) trigger guidance. The main weakness is trigger phrasing tied to internal chain terminology rather than natural user keywords.

Suggestions

Broaden the 'Use for...' clause with natural trigger phrasings users might actually say (e.g. 'when updating Remotion's ffmpeg/compositor binaries' or mentioning rust-ffmpeg version bumps).

Consider listing the key file/tool tokens (Cargo.toml, Cargo.lock, compositor) as searchable trigger terms so the skill surfaces on natural queries.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Update Remotion's ffmpeg-next Git revision', 'refresh Cargo.lock', 'rebuild all supported compositor binaries', 'validate the monorepo', 'open a draft pull request' — giving comprehensive coverage of the task.	5 / 5
Completeness	Both 'what' (the enumerated update/rebuild/validate/PR actions) and 'when' ('Use for the final step of the rust-ffmpeg binary update chain') are present and explicit, though the 'when' is narrow and could surface more trigger variations.	4 / 5
Trigger Term Quality	The trigger clause 'Use for the final step of the rust-ffmpeg binary update chain' names relevant domain terms, but relies on internal chain jargon rather than natural user phrasings or synonyms a user would spontaneously say.	3 / 5
Distinctiveness Conflict Risk	The Remotion ffmpeg-next / rust-ffmpeg compositor rebuild niche with a 'final step of the chain' trigger is highly specific with minimal overlap risk against other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: remotion-dev/remotion
Path: .agents/skills/update-remotion-rust-ffmpeg/SKILL.md
Commit: 77354de

Reviewed: about 20 hours 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.