CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

code-splitting

Use when reviewing large SPA bundles, new dependency additions, or routes that feel slow to hydrate. Focus on code that is not required for the initial view and can move behind route transitions, user interaction, or viewport-based loading.

Quality

75%

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/code-splitting/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 lean, well-structured review skill whose body correctly delegates implementation detail to a real, one-level-deep reference file. The remaining improvements are small: trim the motivational opening paragraph, name a concrete bundle visualizer, and add a post-fix verification step.

Suggestions

Trim the opening concept paragraph — Claude already knows what code splitting is; keep at most the concrete 500 KB / 3–5 s stat if it is needed for user-facing explanations.

Name a specific tool in "Analyze your bundle with a visualizer" (e.g., webpack-bundle-analyzer or source-map-explorer) so the step is directly executable.

Add a verification step after Fix, e.g., "After converting, confirm the entry bundle shrinks and routes still hydrate without errors before recommending the change."

DimensionReasoningScore

Conciseness

The body is mostly lean directives, but the opening paragraph trims poorly: "Code splitting means users only download and parse the code they actually need for the current page, dramatically improving Time to Interactive" is a definitional explanation of a concept Claude already knows, and the 500 KB / 3–5 second stat is motivational padding. It stays at 4 rather than 3 because the over-explanation is confined to one short paragraph and every other section (Quick Reference, Check, Fix, Explain, Code Review) is tight; not 5 because that known-concept sentence is exactly the kind of token that should be cut.

4 / 5

Actionability

As an instruction-only skill the guidance is specific and executable without inline code: "Convert the identified static imports to dynamic imports using import() and add appropriate loading states" and "Inspect route modules, heavy feature imports, and third-party libraries loaded on initial render. Flag dependencies that can move behind import()...". It falls short of 5 because "Analyze your bundle with a visualizer" names no tool and "appropriate loading states" is unspecified; above 3 because the targets and technique are concrete, not pseudocode-level hints.

4 / 5

Workflow Clarity

Check ("Identify any large third-party imports or feature modules... that could be loaded lazily") followed by Fix ("Convert the identified static imports to dynamic imports...") forms a coherent identify-then-convert sequence, and the labeled sections make each mode unambiguous — meeting the simple-skill bar. It misses 5 because there is no verification step after the Fix (e.g., confirm the entry bundle shrank and routes still hydrate); it is above 3 because the flow is clear and explicitly sequenced rather than implicit.

4 / 5

Progressive Disclosure

A lean ~40-line overview with a single, clearly signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and the bundle check confirms references/rule.md exists and delivers exactly what is promised (dynamic import code examples, route-based splitting, framework guidance) with no further indirection. Content is appropriately split between overview and reference with easy navigation.

5 / 5

Total

17

/

20

Passed

Description

62%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, well-phrased "Use when" trigger clause and occupies a distinct SPA performance niche, but the "what" rests on a single focus sentence and it omits the skill's most natural trigger vocabulary ("code splitting", "lazy loading", "dynamic import"). It is a solid mid-to-good description whose main gap is missing primary synonyms and an action-oriented capability statement.

Suggestions

Include the natural phrases users most often say for this skill — "code splitting", "lazy loading", "dynamic imports", "bundle size" — in the trigger clause (e.g., "Use when reviewing large SPA bundles, bundle size regressions, or routes that feel slow to hydrate, or when the user mentions code splitting or lazy loading.").

State the "what" as concrete actions rather than a focus statement, e.g., "Identify code not needed for the initial view and convert it to dynamic import() behind route transitions, user interactions, or viewport triggers."

DimensionReasoningScore

Specificity

The description names its domain concretely ("large SPA bundles, new dependency additions, or routes that feel slow to hydrate") but states only one focus directive — "Focus on code that is not required for the initial view and can move behind route transitions, user interaction, or viewport-based loading" — rather than a list of concrete actions. It is above score 2 (the domain and review targets are specific, not generic) but below score 4 because it never enumerates what the skill actually does (e.g., convert static imports to dynamic import(), lazy-load third-party libraries).

3 / 5

Completeness

The "when" is explicit and concrete: "Use when reviewing large SPA bundles, new dependency additions, or routes that feel slow to hydrate." The "what" is present but phrased as a scoping statement ("Focus on code that is not required for the initial view and can move behind...") rather than explicit action verbs. It is above score 3 because the what is clearly stated, not merely implied, but below score 5 because it lacks a concrete action list paired with the trigger phrases.

4 / 5

Trigger Term Quality

Relevant natural keywords are present ("SPA bundles", "dependency additions", "hydrate", "routes", "viewport-based loading"), but the most common phrases a user would actually say for this skill — "code splitting", "lazy loading", "dynamic imports", "bundle size" — are all absent. Score 4 would require good coverage including those primary synonyms; score 2 would mean only generic keywords, which is not the case.

3 / 5

Distinctiveness Conflict Risk

The SPA hydration niche ("routes that feel slow to hydrate", "viewport-based loading") is distinct with clear triggers. Minor overlap risk remains with closely related performance/dependency-audit skills that could also fire on "large SPA bundles" or "new dependency additions", which keeps it below score 5 but well above the broad-overlap anchors at 2–3.

4 / 5

Total

14

/

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/code-splitting/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.