es-modules

Use when reviewing scripts, client components, bundles, or runtime behavior related to Use ES modules (import/export). Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

Quality

65%

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

Quality

Content

71%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, concise overview with a clean Check/Fix/Explain/Code Review workflow and an exemplary one-level-deep pointer to references/rule.md. Its main weakness is the opening paragraph, which explains background concepts Claude already knows and duplicates content from the reference file.

Suggestions

Trim or remove the opening concept paragraph (tree-shaking/static analysis explanation) — Claude already knows this, and it is duplicated verbatim in the 'Why It Matters' section of references/rule.md.

Consolidate the Quick Reference bullets so they don't restate the intro paragraph's rationale; keep them as pure action items.

Dimension	Reasoning	Score
Conciseness	The body is short overall, but the opening paragraph ("ES modules are statically analyzable — bundlers can determine at build time... tree-shaking. CommonJS require() is dynamic...") explains concepts Claude already knows and duplicates the 'Why It Matters' text in references/rule.md. Some tightening is possible.	3 / 5
Actionability	The Check and Fix sections give concrete, executable direction naming the exact tokens to act on ("Identify any use of require(), module.exports, or exports"; "Convert all require() and module.exports statements to ES module import/export syntax"). Minor gap: no conversion example inline (deferred to references/rule.md).	4 / 5
Workflow Clarity	The Check → Fix → Explain → Code Review sections form a clear, logical sequence, and the Code Review section includes an explicit verification directive ("state how the change should be verified in the browser"). Minor gap: no concrete validation commands or feedback loop in the body itself.	4 / 5
Progressive Disclosure	The body is a well-organized overview with clear section headers and a single, clearly signaled one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and references/rule.md exists in the bundle and holds the code examples and details. Content is appropriately split for a skill of this size.	5 / 5
	Total	16 / 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 has a clear and explicit 'Use when...' trigger with an acceptable what-clause, but it reads like a templated review trigger rather than a statement of the skill's concrete capabilities. It omits the core action (converting CommonJS require/module.exports to import/export) and the most natural trigger terms a user would say.

Suggestions

State the concrete action in the what-clause, e.g. 'Identify require()/module.exports usage and convert it to ES module import/export syntax, then explain the benefits (tree-shaking, static analysis, browser support).'

Add natural trigger terms users would actually say: 'CommonJS', 'require()', 'module.exports', 'convert require to import', and 'tree-shaking'.

Make the trigger distinctive to this rule rather than the generic 'scripts, client components, bundles, or runtime behavior' phrasing shared by sibling frontend rules — e.g. 'Use when a JavaScript file uses CommonJS require()/module.exports or when modernizing module syntax.'

Dimension	Reasoning	Score
Specificity	The description names the domain ("Use ES modules (import/export)") and only 1-2 concrete actions — "reviewing scripts, client components, bundles, or runtime behavior" and "Inspect both source code and the browser execution path". It never states the skill's primary action (converting require()/module.exports to import/export), so coverage is not comprehensive.	3 / 5
Completeness	Both parts are present: an explicit "Use when reviewing scripts... related to Use ES modules (import/export)" trigger, and a what-clause ("Inspect both source code and the browser execution path so fixes target the real bottleneck or bug"). However, the what is underspecified — it describes review context rather than the actual check/fix/explain actions the skill performs.	4 / 5
Trigger Term Quality	Relevant keywords like "ES modules (import/export)", "scripts", "bundles", and "runtime behavior" are present, but the most natural user phrasings for this task — "CommonJS", "require()", "module.exports", "convert require to import" — are absent, leaving common variations and synonyms missing.	3 / 5
Distinctiveness Conflict Risk	"Use ES modules (import/export)" is a specific niche, but the trigger set ("scripts, client components, bundles, or runtime behavior") is a generic frontend-review template that would overlap with many sibling frontend-checklist rules and general JavaScript review skills.	3 / 5
	Total	13 / 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/es-modules/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.