loading-indicators

Use when auditing slow page loads, heavy assets, or rendering delays related to Show loading indicators. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

67%

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/loading-indicators/SKILL.md

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.

The body is well-structured and uses progressive disclosure effectively by deferring all code to a single real reference file. The main gaps are the absence of executable code and explicit validation checkpoints in the body itself.

Suggestions

Add one small inline code snippet (e.g. an aria-busy spinner) so the body is executable without forcing a reference hop for the common case.

Turn the Check/Fix flow into a short numbered sequence with an explicit 'verify in DevTools/Lighthouse → fix → re-measure' validation loop.

Remove the opening restatement of why loading indicators matter (or trim it), since it duplicates references/rule.md and explains a concept Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is lean with well-organized sections and mostly assumes Claude's competence. It loses a point because the opening sentence restates a concept Claude already knows and is duplicated verbatim in references/rule.md.	4 / 5
Actionability	The body names concrete specifics (aria-busy, aria-live, aria-valuenow, skeletons vs spinners) but contains no executable code itself — all code lives in the reference file. Guidance is actionable at a high level but incomplete for direct execution in the body.	3 / 5
Workflow Clarity	Check/Fix/Explain/Code Review provide a rough sequence, but there are no numbered steps or explicit validation checkpoints. The Code Review section hints at measurement but lacks a validate→fix→retry loop, so it does not reach 4.	3 / 5
Progressive Disclosure	The body is a concise overview with a single, clearly signaled one-level-deep reference to a real references/rule.md file. Navigation is easy and content is appropriately split, matching the top anchor.	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.

The description is concise, uses appropriate third-person/trigger guidance, and clearly states when to use the skill. Its main weakness is a thin 'what' that names auditing and verification rather than a richer set of concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain (loading indicators, slow page loads, heavy assets, rendering delays) and 1-2 concrete actions (auditing, verifying the bottleneck in DevTools/Lighthouse/field data), but the action list is not comprehensive. Does not reach 4 because it stops at auditing+verifying rather than listing several specific actions.	3 / 5
Completeness	Explicitly answers 'when' via a clear 'Use when auditing slow page loads...' clause and answers 'what' via 'Verify the actual bottleneck... before recommending changes'. Both are present, but the 'what' is modest and could be more explicit, so it stays at 4 rather than 5.	4 / 5
Trigger Term Quality	Includes natural phrases users would say ('slow page loads', 'loading indicators', 'rendering delays', 'heavy assets') plus tool names (DevTools, Lighthouse). Good coverage but a few common synonyms/variations are missing, so it does not reach 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (loading indicators / performance auditing) with distinct triggers and only minor overlap risk against sibling performance skills. Not a 5 because the perf-auditing framing could overlap with broader performance 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/loading-indicators/SKILL.md
Commit: 30756a7

Reviewed: 18 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.