cdn

Use when auditing slow page loads, heavy assets, or rendering delays related to Use a content delivery network. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

81%

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

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-organized with a clean workflow and a properly signaled one-level reference. Its main weakness is actionability: the inline guidance stays abstract while executable detail lives only in the reference.

Suggestions

Add one small inline executable snippet (e.g., a curl command to inspect Cache-Control/cf-ray headers) so the body is actionable without forcing a reference load.

Give at least one concrete 'Check' signal (e.g., 'look for cf-ray or x-amz-cf-id response headers') rather than only 'Check if static assets are served from a CDN'.

Dimension	Reasoning	Score
Conciseness	The body is lean (~30 lines), assumes Claude's competence, and avoids explaining CDN concepts Claude already knows; every line earns its place.	3 / 3
Actionability	Inline guidance is high-level ('Configure a CDN to serve static assets with proper caching headers') with no executable code or commands in the body itself; concrete examples are deferred to the reference.	2 / 3
Workflow Clarity	The Check -> Fix -> Explain -> Code Review sequence is clear, and the Code Review section explicitly requires confirming the issue via measurement before recommending changes, providing a verification checkpoint.	3 / 3
Progressive Disclosure	A concise overview with a clearly signaled, one-level-deep reference to references/rule.md (a real file), with content appropriately split rather than inlined.	3 / 3
	Total	11 / 12 Passed

Description

77%

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 has explicit trigger guidance and concrete actions with named tools, giving it strong specificity and completeness. It is held back by a broken, duplicated 'Use' construction and triggers broad enough to overlap other performance skills.

Suggestions

Fix the broken phrase 'related to Use a content delivery network' (remove the duplicated 'Use') so the trigger reads naturally.

Tighten the trigger so it is clearly CDN-specific rather than overlapping general page-load/asset auditing skills, e.g. 'Use when static assets are served without a CDN and latency is high for distant users.'

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('auditing slow page loads, heavy assets, or rendering delays' and 'Verify the actual bottleneck in DevTools, Lighthouse, or field data'), naming specific measurement tools.	3 / 3
Completeness	Explicitly answers both what (audit/verify the bottleneck) and when ('Use when auditing slow page loads, heavy assets, or rendering delays').	3 / 3
Trigger Term Quality	Natural terms like 'slow page loads, heavy assets, rendering delays' are present, but the clause 'related to Use a content delivery network' is grammatically broken with a duplicated 'Use', muddying the trigger.	2 / 3
Distinctiveness Conflict Risk	The CDN focus narrows it, but the broad performance-auditing triggers ('slow page loads, heavy assets, rendering delays') could overlap with several other performance skills.	2 / 3
	Total	10 / 12 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/cdn/SKILL.md
Commit: 48405aa

Reviewed: about 8 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.