Name: cloudflare-api-shield
Rating: 56.8 (1 reviews)
Author: membranedev

cloudflare-api-shield

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

Quality

65%

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

Quality

Content

67%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 delivers a largely executable, well-sequenced guide to using the Membrane CLI against Cloudflare API Shield, including a solid connection state machine with validation. Its weaknesses are a generic marketing intro, some duplicated commands, and a dangling 'Step 2' reference that breaks the numbered flow.

Suggestions

Remove or condense the opening paragraph ("Cloudflare API Shield protects APIs from abuse and attacks. It's used by businesses of all sizes..."); it does not aid execution.

Fix the 'skip to Step 2' references by either labeling a Step 2 section or rewording to a concrete next action, since no numbered Step 2 exists.

Deduplicate the action-discovery command (it appears under 'Searching for actions' and again under 'Popular actions'); keep one canonical example.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it opens with a marketing-style intro ("protects APIs from abuse and attacks... businesses of all sizes") and repeats the action-discovery command in two sections; could be tightened without losing clarity, so it sits at 3 rather than 4.	3 / 5
Actionability	Concrete, executable commands appear throughout (npm install, membrane login, connection ensure, action run) with flags and JSON examples; not 5 because placeholders like <actionId> and CONNECTION_ID and the duplicated action-list command leave minor gaps for copy-paste use.	4 / 5
Workflow Clarity	The connection flow is a clear state machine with polling and explicit validation of state values (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) plus a retry-after-action loop; not 5 because the text references 'Step 2' without a labeled Step 2 section, leaving the sequence slightly under-specified.	4 / 5
Progressive Disclosure	Content is organized into clear sections (Overview, Working with..., Popular actions, Best practices) with no nested or buried references; not 5 because there are no bundle files and the skill exceeds 50 lines, so the simple-skill exception does not fully apply, though the single-file structure is appropriate.	4 / 5
	Total	15 / 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 correctly pairs a product-specific domain with an explicit 'Use when' trigger, satisfying both the what and when requirements. Its main weakness is generic action language ('manage data, records, automate workflows') that doesn't convey the concrete capabilities of API Shield (endpoint validation, schemas, zones).

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete API Shield capabilities such as 'configure endpoint validation policies, manage schemas, and inspect zone-level API traffic'.

Expand the trigger clause to name specific user intents, e.g. 'Use when the user wants to configure API Shield endpoint validation, manage schemas, or audit API traffic for a zone'.

Drop or sharpen 'automate workflows', which reads as filler and does not signal a distinct API Shield capability.

Dimension	Reasoning	Score
Specificity	Names the domain ("Cloudflare API Shield") and lists actions ("Manage data, records, and automate workflows"), but the actions are generic boilerplate rather than concrete capabilities; not a 2 because it does enumerate multiple actions and a domain.	3 / 5
Completeness	Both "what" ("Manage data, records, and automate workflows") and "when" ("Use when the user wants to interact with Cloudflare API Shield data") are present and explicit, though the when-clause could be more specific about which tasks trigger it; not 5 because the triggers lack concrete use-case phrasing.	4 / 5
Trigger Term Quality	The phrase "Cloudflare API Shield" is a natural term a user would say, but there are no synonyms, related concepts, or variations beyond repeating the product name; below 4 due to missing common variations.	3 / 5
Distinctiveness Conflict Risk	The product-specific name in both description and trigger creates a clear niche with low overlap risk; not 5 because the generic action verbs ("manage data, records") could in principle overlap with other data skills.	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-api-shield/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.