CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

import-on-interaction

Use when reviewing slow initial loads caused by optional features. Prioritize code that is expensive to download or execute and not required for the first viewport, first input, or core task completion.

Quality

72%

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/import-on-interaction/SKILL.md
SKILL.md
Quality
Evals
Security

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.

A well-structured, token-efficient overview that sequences the workflow clearly and points to a real one-level-deep reference for implementation detail. Its main weakness is that the body itself contains no executable example, so following the fix requires a hop to the reference file.

Suggestions

Include one minimal inline dynamic import() snippet in the Fix section (listener → show loading state → await import) so the core pattern is executable without opening the reference file.

Add a brief verification cue in Code Review such as how to confirm the deferred code is absent from the initial bundle (e.g. checking the build output or network tab), turning the implicit checkpoint into a concrete one.

DimensionReasoningScore

Conciseness

The body is lean with tight one-to-two-line sections and no padding; the only minor trim is the opening motivation paragraph ('Users should not pay the download, parse, and execution cost for features they may never use'), which restates a concept Claude already knows.

4 / 5

Actionability

Directives are specific about what to inspect ('event handlers, modal triggers, drawers, editors, maps, export actions, third-party widgets') and what to do ('user-triggered dynamic import(), add immediate loading feedback'), but no inline code or commands appear — all executable examples are deferred to references/rule.md, leaving the body's guidance incomplete on its own.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a clear sequence with verification checkpoints ('ensure the initial render still works without the deferred feature'; 'verify the fix keeps the initial path lighter without degrading the triggered flow'). It falls short of anchor 5 because verification is a single-line directive with no error-recovery or re-check loop.

4 / 5

Progressive Disclosure

A short overview body with one clearly signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — which exists in the bundle, and no nested references; navigation is trivial.

5 / 5

Total

16

/

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.

A solid description with an explicit trigger clause and a reasonably clear scope, but it describes what to look for rather than what the skill does, omitting the core import-on-interaction mechanism. Keyword coverage misses the natural synonyms users would most likely say.

Suggestions

State the core action explicitly, e.g. 'Defer non-critical JavaScript behind user-triggered dynamic import() so it stays out of the initial bundle' — this would raise both specificity and completeness.

Add natural trigger synonyms users would say, such as 'lazy loading', 'code splitting', 'bundle size', or 'slow page load', to improve trigger term coverage.

Clarify the 'what' alongside the 'when' by pairing the 'Use when' clause with a leading capability statement in third person (e.g. 'Reviews and defers non-critical code...').

DimensionReasoningScore

Specificity

The description names the domain ('reviewing slow initial loads caused by optional features') and one concrete action ('Prioritize code that is expensive to download or execute'), but never states the skill's actual mechanism — deferring code to a user interaction via dynamic import — so coverage is not comprehensive.

3 / 5

Completeness

An explicit 'Use when' clause answers 'when', and 'Prioritize code that is expensive to download or execute and not required for...' answers 'what' — but the 'what' only implies the deferral action rather than naming it, so it falls short of the fully explicit anchor 5.

4 / 5

Trigger Term Quality

Relevant phrases like 'slow initial loads', 'optional features', 'first viewport', and 'first input' are present, but common user phrasings such as 'lazy loading', 'code splitting', 'bundle size', or 'page load' are missing, leaving keyword coverage incomplete.

3 / 5

Distinctiveness Conflict Risk

The framing around 'optional features', 'first viewport', 'first input', and 'core task completion' carves a fairly distinct niche within frontend performance, with only minor overlap risk against closely related skills like code-splitting or bundle-size optimization.

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/import-on-interaction/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.