CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

javascript-minification

Use when reviewing scripts, client components, bundles, or runtime behavior related to Minify all JavaScript files. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/javascript-minification/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%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 a well-structured, appropriately split overview with an excellent one-level-deep reference that carries the implementation details. Its weaknesses are background explanations of concepts Claude already knows (intro sentence, 'Explain' section) and the absence of any executable command or config snippet in the body itself, which are the rubric's two heaviest dimensions.

Suggestions

Cut the intro sentence and the 'Explain' section — why minification helps is knowledge Claude already has; keep only the actionable bullets and pointer.

Add one copy-paste-ready snippet to the 'Fix' section, e.g., `npx terser src/app.js --compress --mangle --output dist/app.min.js` or a two-line Vite/webpack minify config, so the body is executable without opening the reference.

In the 'Check' section, state a concrete verification step (e.g., 'confirm dist output contains no comments/whitespace or ships .min.js files') rather than the abstract 'Verify that all JavaScript files are minified'.

DimensionReasoningScore

Conciseness

The body is mostly efficient bullet lists, but the intro sentence ('Unminified JavaScript adds hundreds of KB to page weight... where every byte counts') and the entire 'Explain' section restate performance benefits Claude already knows. Not 2 because padding is limited to those two spots rather than several padded sections.

3 / 5

Actionability

Concrete tool names are given ('Vite, webpack', 'Terser', 'UglifyJS', 'Enable tree-shaking') but the body contains no executable commands or config snippets — all code is deferred to references/rule.md. Not 4 because anchor 4 requires concrete code or commands with only minor gaps, and the body has none.

3 / 5

Workflow Clarity

A clear Check -> Fix -> Explain -> Code Review sequence is present, and the 'Check' section ('Verify that all JavaScript files are minified in production') serves as a checkpoint. Not 5 because no explicit in-body method for verifying the built output is actually minified (e.g., inspecting dist files or .min.js artifacts).

4 / 5

Progressive Disclosure

A concise ~45-line overview with a clearly signaled one-level-deep reference ('see references/rule.md'); verified that file exists and contains the full details (build-tool configs, framework examples, verification checks) with no nested references. Content is appropriately split and easy to navigate.

5 / 5

Total

15

/

20

Passed

Description

66%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 an explicit 'Use when' trigger and a serviceable 'what', with good natural trigger terms around minification and bundles. Its weaknesses are the awkward embedding of the rule title inside the trigger clause, limited distinct concrete actions, and generic review framing that overlaps sibling frontend performance rules.

Suggestions

Restructure to state concrete capabilities first ('Enable build-tool minification with Terser/UglifyJS, verify production bundles are minified'), then a separate 'Use when the user mentions minification, bundle size, or unminified JavaScript in production builds' trigger clause.

Replace the rule-title phrase 'related to Minify all JavaScript files' with natural trigger synonyms ('minification', 'minified files', 'production build') so distinctiveness comes from the skill's own terms rather than a pasted title.

Differentiate the review framing from sibling performance skills by naming minification-specific artifacts (e.g., dist output, .min.js files, source maps) instead of the generic 'scripts, client components, bundles, or runtime behavior' boilerplate.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ('Inspect both source code and the browser execution path', 'reviewing scripts, client components, bundles') but coverage is not comprehensive — no mention of configuring build tooling or verifying production output. Not 4 because 'reviewing/inspecting' phrasings are variations of the same two actions rather than several distinct capabilities.

3 / 5

Completeness

Has both an explicit 'Use when reviewing scripts, client components, bundles...' trigger and a 'what' ('Inspect both source code and the browser execution path so fixes target the real bottleneck or bug'). Not 5 because the 'what' is embedded awkwardly inside the 'when' clause and read through the rule title rather than stated as concrete capabilities.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'Minify', 'JavaScript files', 'scripts', 'bundles', 'runtime behavior', 'source code', 'browser execution path'. Not 5 because common synonyms users would say ('minification', 'production build', tool names like Terser or UglifyJS) are missing.

4 / 5

Distinctiveness Conflict Risk

The framing 'reviewing scripts, client components, bundles, or runtime behavior' is generic boilerplate shared across sibling frontend performance skills; distinctness rests solely on the 'Minify all JavaScript files' qualifier. Not 4 because that broad review framing creates genuine overlap risk with closely related performance skills.

3 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/javascript-minification/SKILL.md

Reviewed

Table of Contents

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.