CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

88%

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.

A tight, executable, single-purpose skill with concrete commands, a verification step gating a destructive delete, and no padding. The only gap is the lack of an explicit failure-retry feedback loop around the verification step.

Suggestions

Add an explicit retry loop after the curl verification (e.g., 'If the HEAD request fails, re-run the upload in step 3 before deleting the local file') to turn the verification into a full feedback loop and lift workflow_clarity to 5.

Note that curl -I --fail only confirms the object exists, not that its size matches the source; consider verifying content-length against the uploaded size before deleting the local binary.

Flag that the hard-coded path /Users/jonathanburger/remotion is machine-specific; consider documenting how to derive it from `git worktree list` so the skill is portable.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding about what R2 or S3 is; every step (worktree lookup, credential loading, upload, verify, replace, lint) earns its place and assumes Claude's competence.

5 / 5

Actionability

Fully executable, copy-paste-ready bash including the env-file path, R2 endpoint, bucket name, and a size-check short-circuit; placeholders like <local-file> are clearly marked and the common case is covered end to end.

5 / 5

Workflow Clarity

Six clearly sequenced steps with a real validation checkpoint (curl -I --fail verifies the public URL before the destructive delete in step 5, and an exists/same-size check guards the write), but no explicit retry/feedback loop if the verification fails, so it sits below the top anchor.

4 / 5

Progressive Disclosure

A single, well-organized SKILL.md under 50 lines for a single-purpose task with no need for external references, qualifying for the simple-skill exception that allows a 5 without separate bundle files.

5 / 5

Total

19

/

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 precise, third-person description with an explicit 'Use when' trigger and a well-scoped niche. Its only weakness is specificity, where it lists just two concrete actions rather than a comprehensive set.

DimensionReasoningScore

Specificity

Names the domain ('Cloudflare R2 bucket behind remotion.media') and two concrete actions ('Upload large Remotion repository assets' and 'replace local public/ assets with hosted URLs'), fitting the '1-2 concrete actions' anchor rather than 'several' needed for a 4.

3 / 5

Completeness

Explicitly answers both 'what' (upload to the 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'), with concrete trigger phrases matching the top anchor.

5 / 5

Trigger Term Quality

Natural trigger phrases users would say are present ('Use when a file is too large for Git or when a PR should avoid committing media binaries'), but file extensions (e.g. .mp4) and common synonyms like 'binary'/'media asset' are missing, leaving a few natural terms out.

4 / 5

Distinctiveness Conflict Risk

A clear niche scoped to 'Remotion repository assets', 'Cloudflare R2 bucket', and 'remotion.media' with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

17

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
remotion-dev/remotion
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.