preconnect

Use when auditing slow page loads, heavy assets, or rendering delays related to Use preconnect for critical third-party origins. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

65%

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

Quality

Content

61%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 concise, well-structured overview that correctly delegates implementation detail to a single one-level-deep reference file. Its weaknesses are executable specificity — no inline code example and no named measurement step — which leaves the check-to-fix workflow implicit.

Suggestions

Include one copy-paste-ready inline example in the Fix section (e.g., <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>) so the primary action is executable without opening the reference

Make the Check step concrete by naming the measurement: Lighthouse's 'preconnect-to-required-origins' audit or a DevTools/Waterfall view of DNS/TCP/TLS timing

Fix the reference pointer to match references/rule.md's actual content (drop 'framework-specific guidance' or add that section), and clean up the stray empty '##' header in the reference

Dimension	Reasoning	Score
Conciseness	The ~30-line body is lean and assumes Claude's competence ('Preconnecting to essential origins can shave hundreds of milliseconds off the critical path by handling connection overhead ahead of time' adds only rule-specific value). Minor trimmable redundancy: Check/Fix/Explain partially restate the Quick Reference bullets, and 'Code Review' reads as boilerplate ('Flag exact files, requests, or rendering steps...').	4 / 5
Actionability	'Add <link rel="preconnect"> for critical third-party origins and remove it for non-essential or underutilized domains' is a concrete instruction, but the body contains no executable code example (the HTML examples live only in references/rule.md), and 'Check' stays vague ('Review the page's head for preconnect hints') without naming the Lighthouse 'preconnect-to-required-origins' audit or waterfall inspection. Some concrete guidance but incomplete.	3 / 5
Workflow Clarity	The Check -> Fix -> Explain sequence is coherent and the Code Review section gestures at measurement ('describe the measurement method used to confirm the issue'), but verification checkpoints remain implicit rather than explicit steps (no named tool, audit, or pass/fail criterion between check and fix). Steps listed with validation gaps.	3 / 5
Progressive Disclosure	Scored against the actual bundle: one reference (references/rule.md), clearly signaled ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), one level deep, with a concise overview body — near level 5. Minor organization gaps keep it at 4: the body promises 'framework-specific guidance' that references/rule.md does not clearly deliver, and the reference contains a stray empty '##' header.	4 / 5
	Total	14 / 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 has an explicit and natural 'Use when' trigger plus a sensible verify-before-recommending action, but the rule title is duplicated mid-sentence, producing a garbled capability statement. Cleaning up that sentence and adding a couple of concrete action verbs would lift specificity and completeness.

Suggestions

Remove the duplicated rule title from mid-sentence (e.g., 'Audit and add <link rel="preconnect"> hints for critical third-party origins such as font and API hosts. Use when auditing slow page loads, heavy assets, or rendering delays.')

State the skill's deliverable explicitly in the description (what the user gets: a preconnect recommendation with measurement evidence) rather than only the auditing context

Add common trigger synonyms such as 'page speed', 'latency', or 'fonts' to broaden natural keyword coverage

Dimension	Reasoning	Score
Specificity	Names the domain ('preconnect for critical third-party origins') and 1-2 concrete actions ('Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes'), but the pasted rule title mid-sentence ('related to Use preconnect for critical third-party origins') garbles the capability statement and coverage is not comprehensive. It is above level 2 (domain plus real actions exist) but below level 4, which requires a list of several specific actions.	3 / 5
Completeness	An explicit 'Use when auditing slow page loads, heavy assets, or rendering delays...' trigger is present, and a what exists ('Verify the actual bottleneck... before recommending changes'). The what is weakened by the grammatically broken title insertion and only implies the actual deliverable (recommending/adjusting preconnect hints), so it fits 'when' explicit and 'what' present but could be more explicit.	4 / 5
Trigger Term Quality	'slow page loads', 'heavy assets', 'rendering delays', 'preconnect', 'third-party origins', 'DevTools', and 'Lighthouse' are natural phrases users would say, giving good keyword coverage. Missing common variations such as 'page speed', 'performance', 'latency', 'fonts', or 'DNS', so it does not reach comprehensive level 5.	4 / 5
Distinctiveness Conflict Risk	'preconnect' and 'third-party origins' carve a clear niche, but the generic performance triggers ('slow page loads, heavy assets, rendering delays') would also fire for many sibling performance skills (image optimization, lazy loading, bundling). Mostly distinct with minor overlap risk, so not level 5.	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/preconnect/SKILL.md
Commit: 7bfd868

Reviewed: 1 day 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.