CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

update-ffmpeg

Update the monorepo FFmpeg archives, regenerate bindings, rebuild compositor binaries, and validate a single Remotion pull request. Use after the seven-platform FFmpeg build completes.

Quality

82%

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

SKILL.md
Quality
Evals
Security

Quality

Content

80%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 operational runbook with excellent token efficiency and clean delegation to repo docs and sibling skills. Its one structural weakness is the absence of error-recovery guidance for a seven-target batch rebuild, which both caps workflow clarity and leaves the sole non-executable step (the R2 upload) without a fallback path.

Suggestions

Add feedback loops for failure cases: state what to do when a build target fails, when checksum verification fails, or when objdump shows ucrtbase.dll instead of msvcrt.dll (e.g., reinstall the MSVCRT-targeting mingw toolchain and re-run bun run build-all).

Make the R2 upload step executable by naming the workflow file or command (e.g., the .github/workflows path or wrangler/R2 command) instead of "using the repository's R2 upload workflow".

Specify the recovery path when CI for the intended SHA has not succeeded or is partial — the skill forbids combining runs but does not say whether to re-trigger the pipeline or stop.

DimensionReasoningScore

Conciseness

The body is lean and operational — commands, requirements, and prohibitions ("Never overwrite an existing release directory", "Do not hand-edit bindings") with no explanation of concepts Claude already knows. The one explanatory aside (the `pipeline.trigger.type == "api"` rationale) is repo-specific knowledge that prevents a wrong action, not padding, so anchor 5 fits over anchor 4.

5 / 5

Actionability

Nearly every step is copy-paste ready ("node packages/compositor/ffmpeg/collect-artifacts.mjs --sha <full-source-sha>", "bun install-toolchain.ts", "objdump -p packages/compositor-win32-x64-msvc/remotion.exe", and the exact PR title). It is not 5 because "Upload the verified archives to a new immutable directory on remotion.media using the repository's R2 upload workflow" provides no command or workflow path — a gap on a critical-path step.

4 / 5

Workflow Clarity

The collect → verify → upload → import → rebuild → validate → PR sequence is clear and dense with explicit checkpoints (CI success for the same SHA, checksum verification, the objdump msvcrt check, "bun run stylecheck", "git diff --check"). However, this is a batch operation (seven archives, seven bindings, seven rebuilt compositor packages) with no error-recovery feedback loops — nothing says what to do when a target fails or objdump shows ucrtbase.dll — which caps workflow clarity at 3 per the rubric's batch-operation rule.

3 / 5

Progressive Disclosure

The skill is under 50 lines and well-organized into "Collect and import" / "Rebuild and validate", delegating detail one level deep via clearly signaled links (the repo README for CI trigger instructions, "../pr/SKILL.md" for PR mechanics) rather than inlining it. No organization gaps are visible, so anchor 5 fits over anchor 4.

5 / 5

Total

17

/

20

Passed

Description

78%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 names four concrete actions in third person and gives an explicit temporal trigger tied to the FFmpeg build completing. The main improvement space is broadening the "when" clause beyond the single CI-event condition to include user-intent triggers.

DimensionReasoningScore

Specificity

Lists four concrete actions — "Update the monorepo FFmpeg archives", "regenerate bindings", "rebuild compositor binaries", "validate a single Remotion pull request" — matching the "several specific actions; minor gaps" anchor. It falls short of 5 because the collect-artifacts and R2-upload steps of the workflow are not covered.

4 / 5

Completeness

It has a clear "what" (four concrete actions) and an explicit trigger clause ("Use after the seven-platform FFmpeg build completes"), so the missing-trigger cap of 3 does not apply. It is not 5 because the "when" is a single CI-event condition with no user-intent trigger phrases.

4 / 5

Trigger Term Quality

"FFmpeg", "Remotion", "compositor", "rebuild", and "pull request" are natural terms a user would say when needing this skill, giving good keyword coverage. It is not 5 because common variations such as "upgrade" or "bump FFmpeg version" are absent.

4 / 5

Distinctiveness Conflict Risk

"monorepo FFmpeg archives", "Remotion pull request", and "seven-platform FFmpeg build" define a clear niche with distinct triggers and minimal conflict risk. This matches the anchor-5 example; anchor 4 still admits overlap with closely related skills, which does not apply here.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 4 suspicious

Warning

Total

15

/

16

Passed

Repository

remotion-dev/remotion

Path

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