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

72%

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

This is a lean, well-organized simple skill with effective progressive disclosure to a real reference file. Its main weakness is actionability — it names tools but provides no executable configuration — and the absence of verification steps for confirming production minification.

Suggestions

Add a minimal executable example, e.g. a Terser command or a Vite/webpack build config snippet, so the guidance is copy-paste ready.

Include a verification checkpoint, such as comparing production bundle size before and after or checking that the built JS is minified.

Tighten the 'Code Review' section into concrete checks (e.g., 'confirm terser is in the production build pipeline') rather than restating the description.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence ('Unminified JavaScript adds hundreds of KB', 'Use Terser for modern JavaScript minification') with no padding or explanation of basic concepts; every section is short and purposeful.

3 / 3

Actionability

It offers some concrete pointers ('Enable minification in your build tool (Vite, webpack, etc.)', 'Use Terser') but gives no executable config snippets or commands, so a developer cannot copy-paste a working setup — it describes rather than fully instructs.

2 / 3

Workflow Clarity

Sections (Quick Reference, Check, Fix, Explain, Code Review) provide a light sequence, but for a config/deployment change there are no verification checkpoints (e.g., measure bundle size before/after, confirm production build is minified), capping workflow clarity at 2 per the validation guideline.

2 / 3

Progressive Disclosure

The SKILL.md is a concise overview and cleanly delegates detail to a single, clearly-signaled, one-level-deep reference ('see references/rule.md'), which exists as a real file; navigation is straightforward.

3 / 3

Total

10

/

12

Passed

Description

50%

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 leads with a 'Use when reviewing...' trigger and embeds the rule title awkwardly, blurring the what-vs-when split and reading more like a code-review skill than a minification skill. It is specific enough to avoid being generic but misses a clean capability statement and natural trigger phrasings.

Suggestions

State the skill's action first in third person (e.g., 'Minifies and configures production JavaScript bundles for size reduction'), then add a separate 'Use when...' clause.

Add natural trigger terms users would say, such as 'minify JavaScript', 'production bundle size', and 'terser/webpack config'.

Rewrite in third-person voice and separate the 'what it does' from 'when to use it' to satisfy the completeness anchor.

DimensionReasoningScore

Specificity

It names concrete actions ('reviewing scripts, client components, bundles, or runtime behavior', 'Inspect both source code and the browser execution path') but these describe a review pass rather than the skill's core action (minifying JS), and the imperative/second-person voice ('Use when reviewing...') reduces specificity by 1 per the voice guideline.

2 / 3

Completeness

It answers 'when' explicitly ('Use when reviewing scripts...') but the 'what' is only implied via the awkwardly embedded phrase 'Minify all JavaScript files' rather than a clear capability statement, so it does not cleanly answer both per the level-3 anchor.

2 / 3

Trigger Term Quality

Relevant terms appear ('scripts', 'client components', 'bundles', 'runtime behavior') but it lacks the most natural user phrasings ('minify JavaScript', 'bundle size', 'production build') and awkwardly embeds the rule title 'Minify all JavaScript files' mid-sentence, so coverage is incomplete.

2 / 3

Distinctiveness Conflict Risk

The JavaScript-minification niche is fairly specific, but the generic code-review framing ('reviewing scripts, client components... runtime behavior') could overlap with general JS/performance-review skills, so it is not clearly distinct.

2 / 3

Total

8

/

12

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.