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

96%

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

100%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.

An exemplary operational runbook: fully executable commands, a clearly sequenced multi-step workflow with validation checkpoints and stop conditions at every risky point, and lean, well-sectioned content with one-level-deep references. No notable weaknesses found.

Dimension	Reasoning	Score
Conciseness	The body is lean and purely imperative ("Change only the ffmpeg-next.rev value", "Never force-push. If the push is rejected, stop and report it.") with no explanations of concepts Claude already knows and no padding — every token earns its place.	5 / 5
Actionability	Guidance is copy-paste executable throughout: `cargo update -p ffmpeg-next`, `bun install --frozen-lockfile`, `bun run build-all`, `git diff --check`, and `objdump -p packages/compositor-win32-x64-msvc/remotion.exe` with exact pass/fail criteria ("require `msvcrt.dll` and reject `api-ms-win-crt-*` or `ucrtbase.dll` imports").	5 / 5
Workflow Clarity	The four-phase sequence (prepare worktree → update Cargo and rebuild → validate → commit/push/PR) is clearly ordered and dense with explicit checkpoints and stop conditions for the batch rebuild ("Verify that the supplied full SHA is reachable", "Stop if unrelated tracked files changed", "check for an existing pull request... stop instead of duplicating").	5 / 5
Progressive Disclosure	The skill has no bundle directories, and the compact ~78-line runbook is organized into four well-labeled sections with its only file references (`../pr/SKILL.md`, `../pr-name/SKILL.md`) one level deep and clearly signaled ("Read ... before committing or opening the pull request"); nothing that belongs in a separate file is inlined.	5 / 5
	Total	20 / 20 Passed

Description

92%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 strong description: it enumerates concrete actions end-to-end and includes an explicit, domain-specific "use when" clause. The only minor weakness is that a few natural synonyms a user might say are absent.

Dimension	Reasoning	Score
Specificity	The description lists five concrete, non-overlapping 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 skill's capability set with no gaps, matching the anchor for multiple specific concrete actions.	5 / 5
Completeness	It explicitly answers both questions: the "what" is the enumerated action list, and the "when" is stated outright as "Use for the final step of the rust-ffmpeg binary update chain", which is a concrete trigger phrase rather than a weak implication.	5 / 5
Trigger Term Quality	Natural terms are well covered ("Remotion", "ffmpeg-next", "rust-ffmpeg", "Cargo.lock", "compositor binaries", "binary update chain") and would match how a user phrases this request, but a few natural variants are missing (e.g. "upgrade ffmpeg", "compositor", "rust-ffmpeg-sys"), so it falls just short of the comprehensive synonyms-and-extensions anchor.	4 / 5
Distinctiveness Conflict Risk	"Remotion's ffmpeg-next" and "final step of the rust-ffmpeg binary update chain" define a clear niche with distinct trigger terms, so the risk of firing for an unrelated skill is minimal.	5 / 5
	Total	19 / 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: 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.