CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

upload-r2

Upload large Remotion repository assets to the Cloudflare R2 bucket behind remotion.media and replace local public/ assets with hosted URLs. Use when a file is too large for Git or when a PR should avoid committing media binaries by hosting them on remotion.media.

Quality

92%

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

93%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 lean, fully executable workflow: copy-paste commands, secret-handling discipline, idempotent upload, and verification before the destructive local deletion. The only gap is an explicit recovery step if the post-upload URL check fails.

Suggestions

Add one line for failure recovery, e.g., if the curl check fails, re-run the upload step and re-verify before replacing local usage.

Clarify the ordering nuance around deleting the local binary only after the hosted URL is confirmed and the change is committed.

DimensionReasoningScore

Conciseness

Every step is a command or a terse directive with zero padding — no explanation of Git worktrees, S3, or Remotion concepts Claude already knows. The dense inline bun script is the payload itself, so every token earns its place, matching anchor 5.

5 / 5

Actionability

Fully executable, copy-paste ready: "git worktree list --porcelain", the complete bun S3Client upload script with <local-file>/<remote-file-name> placeholders, "curl -I --fail https://remotion.media/<remote-file-name>", and a concrete <Video src="https://remotion.media/example.mp4" /> example. Specific examples cover the common case, matching anchor 5.

5 / 5

Workflow Clarity

Clear six-step sequence with real checkpoints: the upload script's exists/same-size check, explicit "Do not print secret values", and the curl --fail verification before local deletion — so the destructive-operation cap does not apply. However there is no explicit error-recovery loop (e.g., what to do if the curl verification fails), which keeps it below anchor 5 and at anchor 4's "most checkpoints present, minor validation gaps".

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and needs no external reference files; the body is a well-organized headed workflow with clearly ordered steps. Per the rubric's simple-skill guidance this matches the top anchor.

5 / 5

Total

19

/

20

Passed

Description

87%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 that clearly and explicitly states both what the skill does and when to use it, with concrete natural-language triggers and a distinct niche. Minor room to broaden trigger synonyms (video/mp4/large file) and surface one more capability such as verification.

Suggestions

Add a few natural trigger synonyms such as "video", "mp4", or "large file" to broaden the phrases users would naturally say.

Mention the verification step (checking the public remotion.media URL) as a third concrete capability to round out coverage.

DimensionReasoningScore

Specificity

"Upload large Remotion repository assets to the Cloudflare R2 bucket behind remotion.media" and "replace local public/ assets with hosted URLs" are two concrete, precisely targeted actions with infrastructure detail. Falls between anchor 3 (1-2 actions, not comprehensive) and anchor 4 (several specific actions, minor gaps) — the actions are specific but coverage omits verification/cleanup, so 4.

4 / 5

Completeness

Explicitly answers both: what ("Upload large Remotion repository assets to the Cloudflare R2 bucket... and replace local public/ assets with hosted URLs") and when ("Use when a file is too large for Git or when a PR should avoid committing media binaries"). Matches anchor 5's requirement for concrete trigger phrases; anchor 4 would require the 'when' to be less explicit.

5 / 5

Trigger Term Quality

"too large for Git" and "a PR should avoid committing media binaries" are natural phrases users would say in this situation. Good coverage but a few natural terms are missing (e.g., "video", "mp4", "large file", "binary"), matching anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The niche is unmistakable — Remotion repository media assets hosted on remotion.media via a specific R2 bucket — so it would not trigger for unrelated upload/hosting skills. Clear niche with distinct triggers, minimal conflict risk, matching anchor 5.

5 / 5

Total

18

/

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/upload-r2/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.