CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

66

Quality

80%

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

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean, well-structured overview that delegates detail to a single real reference file and provides specific actionable review instructions. The main gap is the absence of an explicit verification step and inline executable examples to confirm a successful CommonJS-to-ESM conversion.

Suggestions

Add a brief verification step (e.g. confirm no require()/module.exports remain, check that the bundle tree-shakes the module) to the workflow.

Inline one short before/after code snippet (require vs import) so the core guidance is executable without opening the reference.

Note browser-specific validation (type="module" script tag / bundler output) as the confirmation path for the runtime behavior the description emphasizes.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, covering only the relevant rationale and actionable review steps with no padding or explanation of basic concepts, matching the "lean and efficient; every token earns its place" anchor.

5 / 5

Actionability

Concrete, specific instructions ("Identify any use of require(), module.exports...", "Convert all require() and module.exports statements") are present, but no executable code examples are inlined (they are delegated to the reference), fitting the "mostly executable guidance; minor gaps" anchor rather than fully copy-paste-ready 5.

4 / 5

Workflow Clarity

The Check/Fix/Explain/Code Review sections give a clear single-purpose sequence for this simple skill, but there is no explicit validation or verification checkpoint for confirming the conversion, placing it just below the explicit-checkpoint 5 anchor.

4 / 5

Progressive Disclosure

A concise overview with a clearly signaled, real one-level-deep reference (references/rule.md) and well-organized sections matches the "clear overview with well-signaled one-level-deep references" anchor; the skill is well under 50 lines.

5 / 5

Total

18

/

20

Passed

Description

75%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 clearly states what the skill does and when to use it, with concrete review targets and natural trigger phrasing. It is slightly broad in scope, creating minor overlap risk with adjacent frontend review skills, and could name a few more natural trigger variations.

Suggestions

Tighten the scope trigger to emphasize the CommonJS-vs-ESM conversion angle (e.g. mention require()/module.exports) to reduce overlap with generic frontend review skills.

Add a couple of natural user phrasings (e.g. "import/export", "tree-shaking", "convert require to import") to broaden trigger-term coverage.

Reduce the duplicated "Use ES modules (import/export)" phrasing inside the trigger clause for cleaner readability.

DimensionReasoningScore

Specificity

Names the ES modules domain and several concrete review targets ("scripts, client components, bundles, or runtime behavior"; "Inspect both source code and the browser execution path"), with only minor coverage gaps, matching the "lists several specific actions" anchor rather than the comprehensive 5.

4 / 5

Completeness

Both "what" (review scripts/components/bundles/runtime behavior, inspect source and browser path) and an explicit "Use when..." trigger are present, but the "when" could be more specific, matching the 4 anchor rather than the fully explicit 5.

4 / 5

Trigger Term Quality

Includes natural terms users would say ("reviewing scripts, client components, bundles, runtime behavior", "ES modules (import/export)") but misses some common synonyms/variations, fitting the "good keyword coverage; a few natural terms missing" anchor instead of the comprehensive 5.

4 / 5

Distinctiveness Conflict Risk

The ES modules focus provides a clear niche, though the broad "scripts, client components, bundles, runtime behavior" scope creates minor overlap with related frontend review skills, fitting "mostly distinct; minor overlap risk" rather than the minimal-conflict 5.

4 / 5

Total

16

/

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.