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

76%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is concise, well-organized, and properly uses progressive disclosure with a valid reference file. Its main weakness is actionability: it gives specific but non-executable guidance with no code examples.

Suggestions

Add at least one concrete code snippet (e.g., an aria-busy/aria-live spinner markup example) to move guidance from descriptive to copy-paste ready.

Remove the duplicated rule-page URL already present in frontmatter metadata to tighten the body.

Consider a short reusable checklist under Code Review so the 'flag exact files/requests' directive maps to specific inspection steps.

Dimension	Reasoning	Score
Conciseness	The body is lean and structured (Quick Reference, Check, Fix, Explain, Code Review) without restating concepts Claude already knows; nearly every token earns its place, with only minor redundancy from the repeated rule-page URL.	3 / 3
Actionability	Guidance names concrete specifics (skeletons for content, spinners for actions, aria-busy/aria-live), but there are no executable code or command examples — it describes an approach rather than giving copy-paste-ready steps.	2 / 3
Workflow Clarity	For this simple checklist-style skill the Check→Fix→Explain→Code Review structure is unambiguous, and the Code Review section embeds a verification requirement ('describe the measurement method used to confirm the issue').	3 / 3
Progressive Disclosure	The body is a concise overview with a single, clearly signaled one-level-deep pointer to references/rule.md (a real, confirmed file), with content appropriately split and easy to navigate.	3 / 3
	Total	11 / 12 Passed

Description

67%

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 provides explicit 'when' triggers and concrete auditing actions, but its second-person voice and overlap with general performance skills limit specificity and distinctiveness. It is solid but not exemplary.

Suggestions

Rewrite in third person (e.g., 'Audits slow page loads...') to avoid the second-person specificity penalty.

Add natural trigger terms users actually say, such as 'loading spinners', 'skeletons', and 'progress bars'.

Sharpen distinctiveness by foregrounding the loading-indicator focus (perceived-performance UX feedback) over generic 'heavy assets / rendering delays' phrasing.

Dimension	Reasoning	Score
Specificity	Concrete actions are named ('auditing slow page loads, heavy assets, or rendering delays', 'Verify the actual bottleneck in DevTools, Lighthouse, or field data'), which would anchor at 3, but the second-person voice ('Use when...') triggers the guideline's -1 specificity penalty, lowering it to 2.	2 / 3
Completeness	An explicit 'Use when...' clause supplies the trigger, and the description states what the skill does (auditing/verifying loading-indicator bottlenecks), answering both what and when.	3 / 3
Trigger Term Quality	Natural phrases like 'slow page loads', 'heavy assets', and 'rendering delays' appear, but common user variations such as 'loading spinner', 'skeleton', or 'progress bar' are missing, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The loading-indicator framing gives a niche, but 'slow page loads, heavy assets, rendering delays' overlaps with general web-performance skills, so it could still trigger a sibling performance skill.	2 / 3
	Total	9 / 12 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: 48405aa

Reviewed: about 9 hours 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.