CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

import-on-visibility

Use when reviewing long pages, dashboards, or content feeds with expensive offscreen modules. Balance early enough loading for smooth scrolling against keeping the initial route light.

Quality

73%

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

Quality

Content

65%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 body with excellent progressive disclosure — a single clearly labeled reference file that verifiably holds the implementation detail. The weaknesses are in the body itself: no executable example or starting values (all code lives in the reference), and the Check→Fix→verify workflow is implicit rather than an explicit sequenced process with validation checkpoints.

Suggestions

Add one minimal executable snippet to the body — e.g., a 5-8 line Intersection Observer setup with a concrete starting rootMargin value — so the core fix is actionable without opening the reference.

Make the Check → Fix → verify sequence explicit (e.g., numbered steps ending with 'Verify: confirm the deferred module loads before the user reaches it, via a throttled scroll trace in DevTools'), turning the buried verification mention into a real checkpoint.

Trim redundancy: the intro paragraph and 'Explain' section restate the frontmatter description, and the trailing rule-page URL duplicates frontmatter metadata — cutting these tightens the body without losing information.

DimensionReasoningScore

Conciseness

The ~45-line body is efficient and assumes Claude's competence, with well-organized sections and no explanation of basic concepts. Minor trimmable content remains: the two-sentence intro and the 'Explain' section largely restate the frontmatter description, and the trailing rule-page URL duplicates metadata already in the frontmatter — anchor 4's 'minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

The body names concrete primitives — 'Use Intersection Observer', 'Tune rootMargin', 'Reserve space with placeholders or skeletons' — but contains no executable code, commands, or starting values (e.g., a rootMargin starting figure or a minimal observer snippet); implementation is deferred to references/rule.md. This matches anchor 3 ('some concrete guidance but incomplete... missing key details') rather than anchor 4, which expects concrete code or commands in the body.

3 / 5

Workflow Clarity

A rough Check (identify candidates) → Fix (apply visibility-based loading) → Code Review (inspect and 'verify the deferred version still loads before the user reaches it') sequence exists, but it is conveyed through role-section ordering rather than explicit steps, and the verification is buried in prose rather than a checkpoint. This is not a destructive/batch operation so no hard cap applies, but it fits anchor 3 ('sequence present but checkpoints missing or implicit') better than anchor 4's explicit checkpoints.

3 / 5

Progressive Disclosure

The body is a concise, well-sectioned overview, and it ends with a clearly signaled one-level-deep pointer: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — stating exactly what the reference contains. The bundle confirms references/rule.md exists (83 lines of real implementation content) with no nested .md references, matching anchor 5's 'clear overview with well-signaled one-level-deep references'.

5 / 5

Total

15

/

20

Passed

Description

70%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 'Use when...' trigger clause naming its domain and natural trigger terms, plus a purpose statement framing the loading tradeoff. Its main weakness is that the capability side stays abstract — it never states the concrete mechanism (visibility-based/module import near the viewport) and omits common synonyms like 'lazy load' or 'below the fold'.

Suggestions

State the concrete mechanism in the 'what' half, e.g., 'Import offscreen modules when they approach the viewport using Intersection Observer, tuning rootMargin so content arrives before the user reaches it' — this would lift both specificity and completeness.

Add common trigger synonyms such as 'lazy loading', 'below the fold', or 'viewport' so the description matches the phrasing users naturally say for this optimization.

Clarify the deliverable (e.g., 'flag eagerly bundled offscreen code and switch it to visibility-based loading during code review') so the skill's output is unambiguous.

DimensionReasoningScore

Specificity

The description names its domain clearly ("long pages, dashboards, or content feeds with expensive offscreen modules") and gives 1-2 actions ("reviewing", "Balance early enough loading... against keeping the initial route light"), but the actions are judgment-level rather than concrete operations. It does not state the actual mechanism (e.g., importing modules when they approach the viewport via Intersection Observer), so it falls short of anchor 4's 'several specific actions' while being clearly more substantive than anchor 2's domain-only examples.

3 / 5

Completeness

Both parts are present: the "when" is explicit with concrete triggers ("Use when reviewing long pages, dashboards, or content feeds with expensive offscreen modules"), and the "what" states the skill's purpose ("Balance early enough loading... against keeping the initial route light"). The "what" is a tradeoff framing rather than a concrete capability statement, so it does not reach anchor 5's 'clearly and explicitly answers both... with concrete trigger phrases' for the what-side.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "long pages", "dashboards", "content feeds", "offscreen modules", "smooth scrolling", and "initial route" are terms a frontend reviewer would plausibly say. However, common variations are missing — "lazy load", "below the fold", "viewport", and "defer" are absent, keeping it below anchor 5's comprehensive synonym coverage; it exceeds anchor 3's single-keyword example.

4 / 5

Distinctiveness Conflict Risk

The niche is mostly distinct — visibility-based loading of offscreen modules on scroll-heavy pages, with distinct triggers (dashboards, content feeds, long pages). There is minor overlap risk with a closely related generic lazy-loading or performance-review skill, which keeps it below anchor 5's minimal conflict risk.

4 / 5

Total

15

/

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-visibility/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.