Name: cloudflare-r2
Rating: 53.6 (1 reviews)
Author: membranedev

cloudflare-r2

Cloudflare R2 integration. Manage data, records, and automate workflows. Use when the user wants to interact with Cloudflare R2 data.

Quality

60%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/cloudflare-r2/SKILL.md

Quality

Content

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

The body is action-rich with executable CLI commands and a clear connection workflow, but it pads an unnecessary R2 overview, lacks validation checkpoints around destructive action/proxy calls, and keeps all reference-style content inline with no progressive disclosure to supporting files.

Suggestions

Add an explicit validation/confirmation checkpoint before destructive action runs or proxy DELETE/PUT requests (e.g., confirm the target bucket and object, verify state after the call).

Move the proxy flag table and the clientAction state reference into a separate reference file and link to it from SKILL.md to improve progressive disclosure.

Trim the opening paragraph that explains what Cloudflare R2 is, since Claude already knows this.

Dimension	Reasoning	Score
Conciseness	Mostly command-driven and efficient, but the opening paragraph explaining what Cloudflare R2 is ("a decentralized object storage service, similar to AWS S3...") and prose like "so you can focus on the integration logic rather than auth plumbing" restate concepts Claude already knows, fitting the 3 anchor.	3 / 5
Actionability	Provides concrete, copy-paste-ready commands throughout ("npm install -g @membranehq/cli@latest", "membrane connection ensure ... --json", "membrane action run <actionId> --connectionId=... --input '...'") with a clear proxy flag table, with only minor gaps such as placeholders that the agent must fill, matching the 4 anchor.	4 / 5
Workflow Clarity	The connection flow is well sequenced with state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but action execution and proxy requests support destructive operations (the proxy table lists DELETE) with no validation or verification steps, which caps workflow clarity at 3 per the destructive-operation rule.	3 / 5
Progressive Disclosure	At 141 lines with no bundle files, the single SKILL.md inlines reference-style material (the full proxy flag table, detailed clientAction state handling) that would fit separate files, and there are no one-level-deep references to deeper materials, fitting the 3 anchor rather than 4.	3 / 5
	Total	13 / 20 Passed

Description

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

The description covers both what and when and is anchored to a specific product, making it reasonably distinct and complete. Its main weakness is generic action language and limited trigger-term coverage that omits common synonyms.

Suggestions

Replace generic verbs ("Manage data, records, and automate workflows") with concrete R2 operations such as creating/listing buckets, uploading, downloading, and deleting objects.

Expand the trigger clause with natural variations users say, e.g. "Use when the user wants to work with Cloudflare R2 buckets, objects, or S3-compatible object storage."

Dimension	Reasoning	Score
Specificity	Names the domain ("Cloudflare R2 integration") and lists action categories ("Manage data, records, and automate workflows"), but those actions are generic rather than concrete R2 operations like listing buckets or uploading objects, so it sits at the 3 anchor rather than 4.	3 / 5
Completeness	It answers both what ("Manage data, records, and automate workflows") and when ("Use when the user wants to interact with Cloudflare R2 data"), but the when clause is somewhat generic rather than concrete, fitting the 4 anchor and falling short of the explicit, comprehensive triggers needed for 5.	4 / 5
Trigger Term Quality	"Use when the user wants to interact with Cloudflare R2 data" surfaces the natural term "Cloudflare R2", but common variations and synonyms (R2 bucket, object storage, S3-compatible) are missing, matching the 3 anchor.	3 / 5
Distinctiveness Conflict Risk	Naming a specific product ("Cloudflare R2") gives it a clear niche with minimal conflict risk, but the generic trigger phrasing leaves minor overlap risk with adjacent Cloudflare or S3-style skills, so 4 rather than 5.	4 / 5
	Total	14 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/cloudflare-r2/SKILL.md
Commit: f484c82

Reviewed: ~12 hours 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.