CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

legacy-js

Use when auditing slow page loads, heavy assets, or rendering delays related to Avoid serving legacy JavaScript to modern browsers. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

73%

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/legacy-js/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.

A well-structured, token-efficient overview that correctly pushes implementation detail into a real one-level-deep reference file. Its weaknesses are in the body itself: the Check and Fix steps name techniques but give no executable commands or config examples, and the workflow lacks an explicit post-fix verification checkpoint.

Suggestions

Include one minimal executable snippet in the body (e.g., the `<script type="module">` / `<script nomodule>` pair or a browserslist/Vite `build.target` line) so the Fix step is actionable without opening the reference.

Make the Check step concrete: name the measurement method (e.g., Lighthouse's 'legacy-javascript' flag, bundle analyzer output, DevTools network waterfall) instead of 'Analyze the project's JavaScript output'.

Add a post-fix verification checkpoint (re-run Lighthouse/PageSpeed Insights and confirm the targeted metric improved) to close the Check → Fix loop.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and sectioned, but the intro ('Modern browsers can execute ES6+ code faster and more efficiently; serving them transpiled ES5 with polyfills adds unnecessary weight') explains a concept Claude already knows, and the Quick Reference bullets ('Use differential serving (module/nomodule)', 'Compile code to modern targets') duplicate the Fix section. These are minor, trimmable instances rather than pervasive padding.

4 / 5

Actionability

Concrete technique names appear ('differential serving (module/nomodule)', 'set a modern target'), but the guidance stays high-level: 'Analyze the project's JavaScript output' gives no command or tool, and 'Update the build configuration' names no config key or snippet — all executable code is deferred to references/rule.md. This matches 'some concrete guidance but incomplete; missing key details' better than level 4, which requires concrete code or commands in the body.

3 / 5

Workflow Clarity

A rough sequence exists (Check → Fix → Explain → Code Review), but validation checkpoints are implicit at best: the body says 'Analyze the project's JavaScript output to see if modern browsers are being served unnecessary ES5 code' but never instructs re-measuring after the fix. Not a destructive/batch operation, so no hard cap, but 'steps listed with checkpoints missing or implicit' fits level 3; level 4 would require most checkpoints present.

3 / 5

Progressive Disclosure

The body is a concise, well-sectioned overview that defers all code examples and framework-specific guidance via a clearly signaled, one-level-deep pointer ('For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`'), and that file exists in the bundle and contains the detailed material. Content is appropriately split and navigation is easy, matching the top anchor.

5 / 5

Total

15

/

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.

A solid trigger-oriented description with an explicit 'Use when...' clause, named tools, and a sensible verify-before-recommending instruction. Its weaknesses are the absent statement of what the skill actually does (the fix techniques), missing common synonyms like 'bundle size'/'polyfills'/'transpiled', and generic leading performance triggers that raise conflict risk with sibling performance skills.

Suggestions

Rewrite the opening trigger around the niche (e.g., 'Use when Lighthouse flags legacy-javascript, or bundle analysis shows ES5 polyfills or transpiled code served to modern browsers') to reduce overlap with sibling performance skills.

Add an explicit capability statement naming the fix, e.g., 'Sets up differential serving (module/nomodule) and modern build targets (browserslist, Vite/Babel targets) to cut legacy-JS payload', so the 'what' is concrete rather than implied.

Replace the embedded rule title 'related to Avoid serving legacy JavaScript to modern browsers' with natural phrasing and add common synonyms (bundle size, transpiled, polyfills) to broaden trigger coverage.

DimensionReasoningScore

Specificity

Several specific actions are named with concrete tools — 'auditing slow page loads, heavy assets, or rendering delays', 'Verify the actual bottleneck in DevTools, Lighthouse, or field data', 'before recommending changes'. Not level 5 because coverage has a real gap: the skill's actual remediation (differential serving, modern build targets) is never mentioned.

4 / 5

Completeness

Both parts are present: an explicit 'Use when auditing slow page loads, heavy assets, or rendering delays...' trigger plus an audit/verify action statement. Not level 5 because the 'what' is never stated as the skill's capabilities — what the skill actually changes (differential serving via module/nomodule, modern build targets) is absent, and the awkward embedded rule title 'related to Avoid serving legacy JavaScript to modern browsers' muddies it.

4 / 5

Trigger Term Quality

Good natural keyword coverage: 'slow page loads', 'heavy assets', 'rendering delays', 'legacy JavaScript', 'modern browsers', 'DevTools', 'Lighthouse', 'field data'. Not level 5 because common variations users would say are missing (e.g., 'bundle size', 'transpiled', 'polyfills', 'ES5').

4 / 5

Distinctiveness Conflict Risk

The niche is named ('Avoid serving legacy JavaScript to modern browsers'), but the opening trigger clause ('slow page loads, heavy assets, or rendering delays') is generic performance language that would equally match sibling performance skills (image optimization, lazy loading, bundle reduction). Level 4 requires only minor overlap with closely related skills; here the broad leading triggers create real overlap risk within a performance-rule family.

3 / 5

Total

15

/

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/legacy-js/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.