Name: bunnycdn
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

Blog Docs Log in Get started

bunnycdn

BunnyCDN integration. Manage CDNs. Use when the user wants to interact with BunnyCDN data.

Quality

61%

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

Quality

Content

61%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 a well-structured, action-oriented CLI integration guide with concrete commands and a useful actions table. Its weaknesses are an unnecessary 'what is a CDN' intro and — more importantly — the absence of validation/confirmation steps for the destructive operations it exposes, which caps workflow clarity.

Suggestions

Delete the opening paragraph explaining what a CDN is and who uses it; Claude already knows this and it adds tokens without value.

Add a validation/confirmation checkpoint before destructive actions (e.g. 'Before running delete-* or purge-* actions, confirm the target ID with the user and verify the resource exists via the corresponding get-* action').

Add one fully worked end-to-end example (e.g. listing pull zones, then purging one by ID) to close the placeholder gap in actionability.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient commands and tables, but opens by explaining what a CDN is and who uses it ('BunnyCDN is a content delivery network (CDN) that speeds up website loading times by caching content on a global network of servers...') — concept explanation Claude already knows — plus minor padding in the prose, fitting the 'mostly efficient but includes some unnecessary explanation' anchor.	3 / 5
Actionability	It provides concrete, copy-paste-ready CLI commands for install, login, connection, action search/run, and proxy requests, plus a 20-row popular-actions table — mostly executable, with only minor gaps (placeholders like CONNECTION_ID and <actionId> require substitution and no fully worked end-to-end example is given).	4 / 5
Workflow Clarity	The connection workflow is clearly sequenced with state-based feedback loops (poll until READY, re-poll after client action), but the skill exposes destructive/batch operations (delete pull/storage/DNS zone, purge cache) with no validation or confirmation guidance, triggering the destructive-operations cap at 3.	3 / 5
Progressive Disclosure	No bundle files are provided, but the single file is well-organized into clearly headed sections (Overview, Working with BunnyCDN, Authentication, Connecting, Searching, Popular actions, Running, Proxy, Best practices) with easy navigation, fitting the 'good structure; most content appropriately placed' anchor.	4 / 5
	Total	14 / 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 successfully states both what the skill does and when to use it, and the BunnyCDN brand gives it strong distinctiveness. Its main weakness is low specificity — 'Manage CDNs' is generic and lists no concrete actions, and the trigger phrase 'interact with BunnyCDN data' is awkward rather than a natural user phrase.

Suggestions

Replace the generic 'Manage CDNs' with 2-4 concrete actions (e.g. 'Create and update pull zones, storage zones, and DNS zones; purge cache; view statistics').

Rewrite the 'Use when' clause with natural trigger phrases users would actually say (e.g. 'Use when the user wants to manage BunnyCDN pull zones, storage zones, DNS zones, or purge cache').

Add common synonyms and resource names (pull zones, storage zones, edge rules, DNS) to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain ('BunnyCDN integration', 'Manage CDNs') but the only action ('Manage') is generic and minimal, with no concrete operations listed — closer to the anchor 'Names the domain but actions are minimal or generic' than to the multi-action anchor above.	2 / 5
Completeness	Both 'what' ('BunnyCDN integration. Manage CDNs.') and 'when' ('Use when the user wants to interact with BunnyCDN data.') are present and explicit, though the 'when' clause is somewhat generic — fitting the anchor where both exist but the trigger could be more specific.	4 / 5
Trigger Term Quality	It includes the brand keyword 'BunnyCDN' and 'CDNs', plus a 'Use when...' trigger, but misses common natural variations and synonyms users would say (e.g. 'pull zones', 'storage zones', 'edge rules', 'purge cache'), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	BunnyCDN is a clearly named, niche product with distinct brand triggers, and the 'Use when...' clause scopes it to BunnyCDN data specifically, giving it a clear niche with minimal conflict risk.	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/bunnycdn/SKILL.md
Commit: f484c82

Reviewed: 4 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.