CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

69%

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

Quality

Content

67%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-organized, actionable overview with a properly used one-level-deep reference and a coherent Check/Fix/Explain/Code Review sequence. Its main weaknesses are a duplicated concept-explanation paragraph (both inline and in the reference) and verification guidance that prompts but does not specify concrete validation steps.

Suggestions

Remove the opening concept-explanation paragraph (or reduce it to one line), since it repeats the 'Why It Matters' section of references/rule.md verbatim and explains tree-shaking basics Claude already knows.

Add one inline before/after conversion snippet (require/module.exports → import/export) so the Fix step is copy-paste concrete and does not depend on the reference file, whose own ES-module example block is empty.

Make the Code Review verification step concrete, e.g., 'after conversion, verify the bundler output contains no CommonJS interop wrapper and test the changed script path in the browser' instead of only prompting to state how it should be verified.

DimensionReasoningScore

Conciseness

The body is mostly tight (Quick Reference bullets, short Check/Fix/Explain/Code Review sections), but the opening paragraph ('ES modules are statically analyzable — bundlers can determine at build time... CommonJS require() is dynamic and prevents this optimization') explains concepts Claude already knows and is duplicated verbatim as 'Why It Matters' in references/rule.md. This matches anchor 3 (mostly efficient but includes some unnecessary explanation or could be tightened) rather than 4, since a full paragraph of known-concept explanation plus cross-file duplication is more than a minor trim.

3 / 5

Actionability

Concrete, exact targets are given: 'Identify any use of require(), module.exports, or exports' and 'Convert all require() and module.exports statements to ES module import/export syntax', plus the specific mechanic 'Add type="module" to script tags'. It is mostly executable guidance with minor gaps (anchor 4): no conversion example is shown inline, and the reference's own ES-module code blocks are empty. Not 5 because the examples do not fully cover the common conversion cases; not 3 because the guidance names exact identifiers and transformations rather than pseudocode.

4 / 5

Workflow Clarity

A coherent single-process sequence is present — Check → Fix → Explain → Code Review — with a verification directive ('state how the change should be verified in the browser'). This is a simple, non-destructive skill so the sequence is unambiguous, matching anchor 4 (clear sequence with most checkpoints present, minor validation gaps): verification is prompted but no concrete validation step (e.g., confirm the bundle no longer contains the CJS interop shim) is given. Not 5 because checkpoints are implicit rather than explicit; not 3 because the sequence is clear, not gap-ridden.

4 / 5

Progressive Disclosure

The ~30-line body is well-sectioned and points to a real, one-level-deep reference with a clear purpose statement ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md') — verified the file exists and is not nested further. Minor gap: the intro paragraph duplicates the reference's 'Why It Matters' section instead of deferring it, so anchor 4 (good structure, minor organization gaps) fits better than 5 (content appropriately split).

4 / 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 has an explicit and grammatically correct "Use when" trigger clause and stays concise, but its "what" is limited to vague inspection language and it omits the skill's core capability (converting CommonJS to ES modules). Trigger keywords cover the ESM side but miss CommonJS-side synonyms, and the generic boilerplate trigger creates overlap risk with sibling JS rules.

Suggestions

State the core capability concretely, e.g., 'Convert require()/module.exports to ES module import/export syntax and enable tree-shaking' instead of the vague 'Inspect both source code and the browser execution path'.

Add CommonJS-side trigger terms users would naturally say, such as 'CommonJS', 'require()', 'module.exports', and 'tree-shaking', to improve trigger coverage.

Replace the generic 'reviewing scripts, client components, bundles, or runtime behavior' boilerplate (shared with sibling rules) with triggers specific to module syntax so the skill is distinguishable from other JavaScript checklist skills.

DimensionReasoningScore

Specificity

The description names the domain ("scripts, client components, bundles, or runtime behavior related to Use ES modules (import/export)") and one or two actions ("reviewing", "Inspect both source code and the browser execution path"), but never states the core capability such as converting require()/module.exports to import/export or enabling tree-shaking. It matches anchor 3 (names domain and 1-2 concrete actions, not comprehensive) rather than 4, which requires several specific actions.

3 / 5

Completeness

It has an explicit "Use when..." clause ("Use when reviewing scripts, client components, bundles, or runtime behavior...") and a what-statement ("Inspect both source code and the browser execution path so fixes target the real bottleneck or bug"). Both are present but the what is vague ("inspect") and the when is generic boilerplate shared by sibling rules, matching anchor 4 (both present, when could be more explicit) rather than 5 (concrete, fully explicit what and when).

4 / 5

Trigger Term Quality

It includes "ES modules (import/export)", "scripts", "bundles", "source code", and "browser execution path", but misses the natural terms users would most likely say: "CommonJS", "require()", "module.exports", and "tree-shaking". This matches anchor 3 (some relevant keywords but missing common variations or synonyms) rather than 4 (good keyword coverage).

3 / 5

Distinctiveness Conflict Risk

Only the phrase "Use ES modules (import/export)" distinguishes it; the surrounding trigger ("reviewing scripts, client components, bundles, or runtime behavior") is template boilerplate that would equally fire for sibling JavaScript checklist skills (e.g., script loading or deferral rules). This matches anchor 3 (somewhat specific but could still overlap with similar skills) rather than 4, which requires mostly-distinct triggers.

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.

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