Name: belugacdn
Rating: 57.599999999999994 (1 reviews)
Author: membranedev

belugacdn

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

Quality

66%

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

Quality

Content

75%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 highly actionable with executable commands and a clear connection-state workflow, but it carries some unnecessary concept explanation and inlines reference-style detail that could be split into bundle files for better progressive disclosure.

Suggestions

Remove the CDN definition and editorializing (e.g. the opening paragraph and 'so you can focus on the integration logic') since Claude already knows what a CDN is.

Move the full clientAction state reference and the proxy-options flag table into a references/ file, leaving a concise summary and a one-level link in SKILL.md.

Fix the step numbering so the referenced 'Step 2' has an explicitly labeled 'Step 1' (e.g. '1. connection ensure', '2. wait for READY').

Dimension	Reasoning	Score
Conciseness	The body is mostly concrete commands, but it opens by explaining what a CDN is ('BelugaCDN is a content delivery network (CDN) service...') and includes editorializing ('so you can focus on the integration logic rather than auth plumbing') that Claude does not need, fitting the score-3 anchor of mostly efficient with some unnecessary explanation.	3 / 5
Actionability	It provides fully executable, copy-paste-ready commands covering the common cases (install, login, connection ensure, action list/run, proxy) plus a flag table, matching the score-5 anchor for fully executable guidance covering common cases.	5 / 5
Workflow Clarity	The install→auth→connect→poll→search→run sequence is clear with explicit state-based feedback loops (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR and re-polling), but step numbering is inconsistent ('Step 2' referenced without a labeled Step 1), fitting the score-4 anchor of clear sequence with minor gaps.	4 / 5
Progressive Disclosure	Sections are well-organized and there are no nested references, but all content (including the full clientAction state reference and the proxy-options table that could live in separate files) is inlined in SKILL.md, fitting the score-4 anchor of good structure with minor organization gaps.	4 / 5
	Total	16 / 20 Passed

Description

57%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 includes an explicit 'Use when...' trigger and a named brand giving it decent completeness and distinctiveness, but its capability list is generic and it lacks the natural CDN-specific trigger terms users would actually say.

Suggestions

Replace generic actions ('Manage data, records, and automate workflows') with concrete BelugaCDN operations such as 'create and configure pull zones, manage cache settings and origins, and manage SSL certificates'.

Add natural trigger keywords users would say, e.g. 'Use when the user mentions BelugaCDN, a CDN, pull zones, cache settings, origins, or SSL certificates.'

Tighten the 'when' clause to reference specific BelugaCDN resources (pull zones, billing, team members) rather than just 'BelugaCDN data'.

Dimension	Reasoning	Score
Specificity	It names the domain (BelugaCDN) but the listed actions ('Manage data, records, and automate workflows') are generic rather than concrete CDN operations such as creating pull zones or managing cache settings, matching the score-2 anchor for minimal/generic actions.	2 / 5
Completeness	Both 'what' ('Manage data, records, and automate workflows') and 'when' ('Use when the user wants to interact with BelugaCDN data') are present, but the 'when' clause could be more specific, matching the score-4 anchor.	4 / 5
Trigger Term Quality	'BelugaCDN', 'data', 'records', and 'workflows' provide some relevant keywords, but it misses common natural terms and synonyms a user would say (CDN, pull zone, cache, SSL, origin), fitting the score-3 anchor of partial keyword coverage.	3 / 5
Distinctiveness Conflict Risk	The named brand 'BelugaCDN' establishes a clear niche with minimal conflict risk beyond closely related CDN skills, matching the score-4 anchor of mostly distinct with minor overlap.	4 / 5
	Total	13 / 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/belugacdn/SKILL.md
Commit: f484c82

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