compression

Use when auditing slow page loads, heavy assets, or rendering delays related to Enable text-based compression. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

67%

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

Quality

Content

65%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 and appropriately split with an excellent one-level reference, but it is more overview than instruction: Check and Fix state what to do without any executable command or config snippet, and the workflow lacks a post-fix verification step. The Quick Reference bullets and intro also mildly overlap with knowledge Claude already has.

Suggestions

Add one executable check step, e.g. `curl -sI -H 'Accept-Encoding: gzip' https://example.com/app.js | grep -i content-encoding`, so the Check section can be run directly.

Include a minimal fix snippet (e.g. the 3-line nginx `gzip on; gzip_types ...; gzip_min_length ...;`) in the body, keeping framework detail in references/rule.md.

Close the workflow with an explicit validation step: after enabling compression, re-run the Check and re-measure in Lighthouse to confirm the transfer-size reduction, matching the description's verify-before/after framing.

Dimension	Reasoning	Score
Conciseness	The ~30-line body is mostly efficient with a clean section structure, but the intro sentence ('Compressed assets download faster, reducing the time to first paint...') explains a concept Claude already knows, and some Quick Reference bullets duplicate it.	4 / 5
Actionability	Check names the exact headers to look for ('Content-Encoding: gzip' or 'br') and Fix names the config surfaces (Nginx, Apache, CDN), but neither gives an executable step or command — the actual config code lives only in references/rule.md, leaving the body's guidance concrete but incomplete.	3 / 5
Workflow Clarity	The Check → Fix → Explain → Code Review sections imply a legible sequence, but steps are not ordered/numbered and there is no validation checkpoint (e.g. re-measure or re-check headers after enabling compression), leaving checkpoints implicit.	3 / 5
Progressive Disclosure	The body is a concise overview that delegates implementation detail via a single clearly signaled, one-level-deep pointer ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and that file exists and contains exactly that detail (Nginx/Express config, tradeoffs).	5 / 5
	Total	15 / 20 Passed

Description

70%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 has a clear, explicit 'Use when' trigger with natural user phrasing and named tools (DevTools, Lighthouse), and a sensible verify-before-recommending framing. Its main weaknesses are an incomplete statement of what the skill actually does and the awkward pasted rule name 'Enable text-based compression' inside the trigger phrase.

Suggestions

State the 'what' explicitly, e.g. 'Enables Gzip/Brotli compression for text resources (HTML, JS, CSS) in Nginx, Apache, or CDN configs. Use when auditing slow page loads...'.

Add missing natural trigger terms such as 'gzip', 'brotli', and 'page speed' to improve trigger coverage.

Reword the pasted rule title 'related to Enable text-based compression' into natural language (e.g. 'related to text-based compression') so it reads as a trigger phrase rather than a rule name.

Dimension	Reasoning	Score
Specificity	Explicit actions are limited to 'auditing slow page loads, heavy assets, or rendering delays' and 'Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes' — two concrete actions with named tools, but the skill's core capability (enabling/fixing compression) is never stated, so coverage is not comprehensive.	3 / 5
Completeness	An explicit 'Use when auditing slow page loads, heavy assets, or rendering delays...' trigger answers 'when' clearly, and 'Verify the actual bottleneck... before recommending changes' gives a partial 'what'; the full 'what' (that this skill enables/configures text compression) is not stated.	4 / 5
Trigger Term Quality	Natural phrases users would say are present ('slow page loads', 'heavy assets', 'rendering delays', 'compression', 'DevTools', 'Lighthouse'), but common synonyms like 'gzip', 'brotli', and 'page speed' are missing.	4 / 5
Distinctiveness Conflict Risk	The niche (text-based compression for performance) is mostly distinct, but broad triggers like 'slow page loads' and 'heavy assets' create minor overlap risk with adjacent performance skills (caching, image optimization).	4 / 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/compression/SKILL.md
Commit: 7bfd868

Reviewed: 1 day 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.