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

74%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/import-on-visibility/SKILL.md

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.

The body is a well-structured, token-efficient overview that defers implementation depth to a real one-level reference. Its main weakness is actionability: the inline guidance is concrete but stops short of executable steps, leaning on the external reference for the actual how.

Suggestions

Add a minimal runnable IntersectionObserver snippet (observer setup + rootMargin example) inline so the skill is actionable without opening the reference.

Include an explicit verification step (e.g., confirm the deferred chunk resolves before the section enters the viewport) to close the workflow loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and efficient with no padding or re-explanation of concepts Claude already knows; every section (Quick Reference, Check, Fix, Explain, Code Review) earns its place.	5 / 5
Actionability	Guidance is concrete ('Use Intersection Observer', 'Reserve space with placeholders or skeletons', 'Tune rootMargin') but stays high-level for an instruction-only skill, missing the specific steps or runnable snippets needed to execute without the external reference.	3 / 5
Workflow Clarity	The Check → Fix → Explain → Code Review sections give a clear sequence, and this is not a destructive/batch operation requiring validation; minor gap is the lack of an explicit verify-the-deferred-load-fires-before-scroll checkpoint.	4 / 5
Progressive Disclosure	A clear overview with a single, well-signaled one-level-deep reference to references/rule.md (which exists), with the bulk of implementation detail correctly deferred to that file.	5 / 5
	Total	17 / 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.

The description is concise, uses third person, and clearly pairs a 'Use when' trigger with a concrete capability statement. It is well-scoped to its niche, with only minor gaps in trigger synonyms and action comprehensiveness.

Suggestions

Add natural synonyms users might say, such as 'lazy loading', 'below-the-fold content', or 'deferred modules', to broaden trigger coverage.

List a few more concrete actions (e.g., 'set up an IntersectionObserver', 'add a skeleton placeholder') to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ('reviewing long pages, dashboards, or content feeds with expensive offscreen modules' and 'Balance early enough loading...against keeping the initial route light') but the action set is not comprehensive.	3 / 5
Completeness	Explicitly answers both what ('Balance early enough loading...against keeping the initial route light') and when ('Use when reviewing long pages, dashboards, or content feeds...'), with the when being concrete and explicit.	4 / 5
Trigger Term Quality	Includes natural trigger phrases ('long pages', 'dashboards', 'content feeds', 'offscreen modules') with a clear 'Use when' clause, though common synonyms like 'lazy load' or 'below the fold' are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a specific niche (visibility-based loading of offscreen modules) that is mostly distinct from sibling skills, with only minor overlap risk against general performance or code-splitting skills.	4 / 5
	Total	15 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/import-on-visibility/SKILL.md
Commit: 30756a7

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.