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

57%

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

Quality

Content

43%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 well-structured for progressive disclosure, cleanly deferring detail to a real reference file, but it is light on actionable/executable guidance and presents a loose template rather than a validated workflow.

Suggestions

Move or summarize at least one concrete executable snippet (e.g., a Cache-Control header example or a Lighthouse/DevTools check command) into the body so the skill is actionable without opening the reference.

Replace the Check/Fix/Explain template with a short sequenced workflow that includes an explicit validation checkpoint (e.g., 'Verify via Lighthouse from multiple regions before recommending a CDN change').

Remove the opening CDN-definition paragraph and the redundant 'Explain' section, which restate a concept Claude already knows and duplicate the Quick Reference.

Dimension	Reasoning	Score
Conciseness	Mostly short and efficient, but the opening paragraph explains what a CDN is (a concept Claude already knows) and the Quick Reference plus 'Explain' section repeat that same latency/edge-server content.	3 / 5
Actionability	The body gives high-level direction ('Configure a CDN to serve static assets with proper caching headers') with no executable code or commands in the body itself; concrete guidance is deferred entirely to references/rule.md.	2 / 5
Workflow Clarity	Check/Fix/Explain/Code Review read as a loose template rather than a sequenced workflow, and the Code Review auditing step lacks an explicit validation checkpoint despite the body demanding a measurement method to confirm the issue.	2 / 5
Progressive Disclosure	The body is a clean overview that signals a single one-level-deep reference (references/rule.md, verified to exist and hold the bulk of detail), with well-organized section headers and easy navigation.	5 / 5
	Total	12 / 20 Passed

Description

71%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 is specific and trigger-rich for performance auditing, but suffers from a templated 'related to Use a content delivery network' insertion that muddies the 'what' and weakens distinctiveness against sibling performance skills.

Suggestions

Rewrite the description so the 'what' (configure/audit CDN delivery of static assets) is stated cleanly and separately from the 'when' trigger clause, removing the templated 'related to Use a content delivery network' phrasing.

Add CDN-specific natural trigger terms (e.g., 'latency', 'TTFB', 'CDN', 'edge cache') to improve trigger-term coverage and distinctiveness from other performance skills.

Tighten the trigger to be CDN-specific (e.g., 'Use when static assets are served without a CDN or edge cache causing high latency') to reduce overlap with general performance auditing skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions (audit slow page loads/heavy assets/rendering delays, verify bottleneck in DevTools/Lighthouse, recommend changes), though the awkward 'related to Use a content delivery network' phrase introduces a templated gap.	4 / 5
Completeness	Has an explicit 'Use when...' clause with concrete triggers and an implied 'what' (verify bottleneck before recommending changes), but the 'what' is tangled with the 'when' rather than cleanly stated.	4 / 5
Trigger Term Quality	Includes natural debugging terms ('slow page loads', 'heavy assets', 'rendering delays', 'DevTools', 'Lighthouse') users would say, but misses CDN-specific synonyms like 'latency' or 'TTFB' and the phrase 'Use a content delivery network' is templated rather than a natural utterance.	4 / 5
Distinctiveness Conflict Risk	Trigger symptoms (slow page loads, heavy assets, rendering delays) overlap broadly with sibling performance skills; CDN specificity relies on the tacked-on 'related to Use a content delivery network' phrase.	3 / 5
	Total	15 / 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
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/cdn/SKILL.md
Commit: 30756a7

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