CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

cloudflare

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

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/cloudflare/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 skill is highly actionable — every operation is expressed as an exact, runnable CLI command with clear state-handling for the connection lifecycle. Its weaknesses are the missing validation for destructive actions (which caps workflow clarity), a company-intro paragraph that wastes tokens, and minor structural inconsistencies like the dangling 'Step 2' reference.

Suggestions

Add a validation/confirmation step before destructive or batch actions (e.g., verify the zone ID with 'get-zone' and confirm with the user before 'delete-zone' or 'purge-all-cache'), which would lift the workflow_clarity cap.

Delete the 'Cloudflare is a web infrastructure and security company...' intro paragraph and tighten vague sentences like 'Those will be used to adjust tooling...' to improve token efficiency.

Fix the internal navigation: either label the sections as Step 1/Step 2 or replace 'skip to **Step 2**' and the '1b' heading with the actual section names ('Searching for actions', 'Running actions').

DimensionReasoningScore

Conciseness

The body is mostly lean commands and tables, but opens with two sentences explaining what Cloudflare is ('Cloudflare is a web infrastructure and security company. It provides services like CDN, DDoS protection, and DNS...') — a concept Claude already knows — plus vague filler like 'Those will be used to adjust tooling to be used best with your harness'.

3 / 5

Actionability

Copy-paste-ready commands throughout: 'membrane connection ensure "https://www.cloudflare.com/" --json', 'membrane action list --connectionId=... --intent "QUERY"', 'membrane action run <actionId> --input {...} --json', plus a proxy flag table and a table of concrete action keys (list-zones, create-dns-record, purge-all-cache) that cover the common cases.

5 / 5

Workflow Clarity

The install → login → connect → poll → search → run sequence is present with state-based checkpoints (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR) and a polling loop, but the skill covers destructive and batch operations (delete-zone, delete-worker, purge-all-cache) with no validation or confirmation guidance, capping this dimension at 3; additionally 'skip to **Step 2**' references a section that does not exist and the '1b' heading has no labeled '1a' or 'Step 2'.

3 / 5

Progressive Disclosure

A single well-sectioned SKILL.md (~160 lines) with clear headers and scannable tables, no nested references, and no bundle files provided; minor gaps remain (dangling 'Step 2' pointer, a 20-row action table that could live in a reference file), keeping it below the clean split of anchor 5.

4 / 5

Total

15

/

20

Passed

Description

66%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 correctly names the Cloudflare niche and includes an explicit 'Use when' clause, so trigger confusion is unlikely. However, it undersells the skill's actual breadth — only 'Manage Accounts' is named while the body covers zones, DNS, Workers, and cache operations — and it lacks the concrete trigger phrases users would naturally say.

Suggestions

Enumerate more concrete capabilities in the description, e.g. 'Manage Cloudflare accounts, zones, DNS records, Workers, and cache purging', to raise specificity.

Add natural trigger keywords users would actually say — DNS records, domains, zones, Workers, cache purge, firewall rules — so the description matches real requests.

Make the 'when' clause more concrete, e.g. 'Use when the user mentions Cloudflare, DNS records, zones, Workers, or wants to purge cache'.

DimensionReasoningScore

Specificity

'Manage Accounts' is one concrete action on a named domain, but the description stops there — matching anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive') rather than 4, since the body covers zones, DNS records, Workers, cache, and firewall rules that the description never mentions.

3 / 5

Completeness

Both a 'what' ('Manage Accounts') and an explicit 'when' ('Use when the user wants to interact with Cloudflare data') are present, but the 'when' is broad rather than concrete trigger phrases — anchor 4, not 5; not 3 because the 'when' is explicitly stated rather than merely implied.

4 / 5

Trigger Term Quality

'Cloudflare' and 'Accounts' are terms users would naturally say, but common variations a user would actually utter — DNS records, zones, Workers, cache purge, firewall rules, domains — are all missing, matching the 'Some relevant keywords but missing common variations or synonyms' anchor.

3 / 5

Distinctiveness Conflict Risk

The description names a specific commercial product (Cloudflare), giving it a clear niche with a distinct trigger term and minimal conflict risk with other skills.

5 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Revision

f484c82

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill