CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

54

Quality

61%

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

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 skill body is lean and well-organized with a clean one-level reference to a real bundle file, but it stops at naming tools rather than giving executable config or commands, and lacks verification steps for what is effectively a build-time batch operation.

Suggestions

Add a copy-paste-ready minification config snippet (e.g., a Terser or Vite build config block) so guidance is executable, not just tool names.

Include an explicit verification step such as checking the production bundle size or inspecting output for comments/whitespace.

Trim the opening paragraph and the 'Explain' section, which restate performance concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is short and well-sectioned with minimal padding, though the opening sentence and the 'Check/Explain' sections restate concepts Claude already knows and could be trimmed slightly.

4 / 5

Actionability

It names tools (Terser, UglifyJS, Vite, webpack) and gives a typical savings figure, but provides no executable config snippets, commands, or copy-paste examples — guidance stays at the hint level.

3 / 5

Workflow Clarity

The Check/Fix/Explain structure gives a rough sequence, but minification is a build/deploy batch operation with no explicit verification step (e.g., confirming minified output or measuring bundle size), so checkpoints are missing.

3 / 5

Progressive Disclosure

The body is a concise overview with clear sections and a single, well-signaled one-level reference to references/rule.md, which exists in the bundle; navigation is straightforward.

5 / 5

Total

15

/

20

Passed

Description

58%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 a clear 'Use when...' trigger and identifies the JavaScript minification domain, but it conflates the skill's purpose (minify JS) with a generic code-review framing, weakening specificity and distinctiveness. Trigger terms are present but miss the most natural user phrasings.

Suggestions

Lead with the concrete capability (e.g., 'Minify JavaScript files for production builds') before the review framing so the 'what' matches the skill's purpose.

Add natural trigger terms users actually say, such as 'minify JS', 'reduce bundle size', 'production build optimization', or '.js files'.

Tighten the review clause so it cannot be confused with a general frontend code-review skill; tie inspection explicitly to minification outcomes.

DimensionReasoningScore

Specificity

The description names the domain (minifying JavaScript files) and a couple of concrete actions ('reviewing scripts, client components, bundles, or runtime behavior'), but the actions are framed around inspection rather than the skill's actual minification capability, leaving coverage incomplete.

3 / 5

Completeness

It has an explicit 'Use when...' clause and a stated 'what' (reviewing/inspecting JS to fix bottlenecks), but the 'what' describes reviewing rather than the minification action itself, so the trigger is explicit while the capability framing is slightly indirect.

4 / 5

Trigger Term Quality

It includes some relevant terms ('scripts', 'client components', 'bundles', 'runtime behavior') but omits the most natural phrases a user would say ('minify JS', 'reduce bundle size', '.js files') and over-relies on the awkward literal rule name.

3 / 5

Distinctiveness Conflict Risk

The skill is scoped to JavaScript minification, but the description's emphasis on 'reviewing scripts, client components, and runtime behavior' is broad and could overlap with general frontend code-review skills.

3 / 5

Total

13

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.