cloudflare-r2

Guide for implementing Cloudflare R2 - S3-compatible object storage with zero egress fees. Use when implementing file storage, uploads/downloads, data migration to/from R2, configuring buckets, integrating with Workers, or working with R2 APIs and SDKs.

Quality

84%

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

76%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 highly actionable, well-structured R2 reference with strong executable examples and clearly signaled reference files. Its main weaknesses are missing validation checkpoints for batch/destructive operations (capping workflow clarity) and some inline content that overlaps with existing reference files.

Suggestions

Add explicit validation/verification steps to batch and destructive workflows: after Super Slurper migration, verify object counts against the source; after applying lifecycle rules, confirm the rule parsed correctly; after deletes, confirm via `head`/list that the object is gone.

Trim the 'When to Use This Skill' section (it duplicates the frontmatter description) and the marketing opener to reduce token redundancy, or replace them with a one-line pointer to the description.

Move the per-language SDK quick snippets (AWS SDK v3, Boto3) and the multipart/lifecycle/event-details into the existing references, keeping SKILL.md to the overview + Workers binding + one representative example per access method.

Dimension	Reasoning	Score
Conciseness	The body is dense and code-heavy with little concept explanation, but the marketing-style opener ('Built on Cloudflare's global network for high durability (11 nines) and strong consistency') and the 'When to Use This Skill' list (which duplicates the frontmatter description) add minor padding. It is not a 5 because of this redundancy, and not a 3 because the bulk is genuinely lean, executable content.	4 / 5
Actionability	Copy-paste-ready commands and code span wrangler CLI, Workers API, AWS CLI, AWS SDK v3, Boto3, and Rclone, covering the common cases with specific endpoints and parameters. This matches the fully-executable anchor; it is not a 4 because the examples are complete and runnable rather than having gaps.	5 / 5
Workflow Clarity	The Quick Start is numbered (create bucket, upload, download) and troubleshooting is provided, but batch/destructive operations (Super Slurper bulk migration, lifecycle auto-delete rules, object deletes) lack explicit validation or verification checkpoints. Per the rubric cap, batch operations without validation cap workflow clarity at 3; it is not a 4 because no validate-fix-retry feedback loops are present for these risky operations.	3 / 5
Progressive Disclosure	Clear section structure with a 'Reference Files' block pointing to four verified one-level-deep files (api-reference.md, sdk-examples.md, workers-patterns.md, pricing-guide.md), each described. It is not a 5 because the body itself is heavy (~460 lines) and inlines per-language SDK snippets and full multipart/lifecycle/event sections whose bulk already lives in the reference files, leaving a minor organization gap.	4 / 5
	Total	16 / 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, third-person description that crisply states the capability and gives an explicit, multi-trigger 'Use when' clause. It is specific, distinct, and complete; the only minor gap is a few missing natural synonyms in the trigger list.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions ('implementing file storage, uploads/downloads, data migration to/from R2, configuring buckets, integrating with Workers, or working with R2 APIs and SDKs'), matching the comprehensive-coverage anchor. It is not a 4 because coverage spans the full action surface with no meaningful gaps.	5 / 5
Completeness	It explicitly answers 'what' ('S3-compatible object storage with zero egress fees') and 'when' with a concrete 'Use when implementing...' clause enumerating trigger scenarios. This matches the anchor requiring both what and when with concrete trigger phrases; it is not a 4 because the 'when' is fully explicit rather than only approximate.	5 / 5
Trigger Term Quality	Natural trigger terms are present ('file storage', 'uploads/downloads', 'data migration', 'buckets', 'Workers', 'R2 APIs and SDKs', 'S3-compatible'), but a few common variations users might say (presigned URLs, CORS, object storage as a trigger phrase) are absent. It is not a 5 because the synonym/variation coverage is not exhaustive, and not a 3 because the included terms are clearly natural rather than generic.	4 / 5
Distinctiveness Conflict Risk	'Cloudflare R2' names a clear niche with distinct triggers (R2, Workers, S3-compatible migration) and minimal overlap risk with other skills. It is not a 4 because the triggers are tightly scoped to R2 specifically rather than a broad storage category.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: einverne/dotfiles
Path: claude/skills/cloudflare-r2/SKILL.md
Commit: 651d4ea

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.