Name: cloudflare
Rating: 60.8 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

cloudflare

Cloudflare integration. Manage Accounts. Use when the user wants to interact with Cloudflare data.

Quality

71%

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/SKILL.md

Quality

Content

81%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 content is highly actionable with a clear, checkpointed connection workflow and executable commands throughout. Its only real weakness is a brief introductory paragraph that explains Cloudflare itself — background Claude already knows — plus a large inline actions table that would benefit from being split out.

Suggestions

Remove or trim the opening 'Cloudflare is a web infrastructure and security company...' paragraph since it restates knowledge Claude already has.

Consider moving the 'Popular actions' table to a separate ACTIONS.md reference and linking to it from the body to improve progressive disclosure.

Fix the awkward 'Agent Types' line ('Those will be used to adjust tooling to be used best with your harness') for clarity and conciseness.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with executable commands, but the opening paragraph explaining what Cloudflare is ('a web infrastructure and security company... CDN, DDoS protection, and DNS') restates knowledge Claude already has, which is concept-padding penalized by the rubric.	3 / 5
Actionability	Commands are fully executable and copy-paste ready across the common cases (install, login, connection ensure, action list/run, request proxy) with flags and a JSON-output convention documented, matching the 'fully executable; specific examples cover common cases' anchor.	5 / 5
Workflow Clarity	The connection flow is a clear sequence with explicit state-based checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a feedback loop ('poll again after the user completes the action'), giving clear validation and error-recovery guidance.	5 / 5
Progressive Disclosure	The skill is a single well-sectioned file with no nested references and clear headers, but the ~20-row 'Popular actions' table is bulk reference content inlined in SKILL.md that could live in a separate file, keeping it just short of the well-signaled one-level-deep reference anchor.	4 / 5
	Total	17 / 20 Passed

Description

61%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 is well-triggered and clearly niche-targeted, with an explicit 'Use when' clause. Its main weakness is the vague, minimal 'what' — 'Manage Accounts' is generic and omits the concrete Cloudflare capabilities the skill actually exposes (DNS, Zones, Workers, Pages, cache purge).

Suggestions

Replace the generic 'Manage Accounts' with concrete actions, e.g. 'Manage Cloudflare accounts, zones, DNS records, Workers, Pages, and cache.'

Broaden trigger terms to natural user phrasing such as 'DNS records', 'zones', 'Workers', 'Pages', or 'purge cache'.

Keep the explicit 'Use when...' clause but tie it to these specific capabilities for sharper triggering.

Dimension	Reasoning	Score
Specificity	The description only names the Cloudflare domain and the single generic action 'Manage Accounts', which is closer to the minimal/generic anchor ('Processes PDF files') than to listing concrete actions; it is not comprehensive and 'Manage' is vague.	2 / 5
Completeness	It states both a 'what' ('Cloudflare integration. Manage Accounts.') and an explicit 'when' ('Use when the user wants to interact with Cloudflare data.'); the trigger clause is present so it clears the 3-cap, though the 'what' could be more specific, matching the score-4 anchor.	4 / 5
Trigger Term Quality	'Cloudflare' and 'Accounts' are relevant keywords a user might say, but the description omits common variations/synonyms (e.g. DNS, zones, Workers, Pages) that users naturally mention, fitting the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	'Cloudflare integration' occupies a clear, well-known niche with distinct triggers, so it is unlikely to fire for the wrong skill, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.	5 / 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/SKILL.md
Commit: f484c82

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