CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

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

The body is well-structured with excellent progressive disclosure: a short overview correctly deferring implementation details to a real references/rule.md file. Its weaknesses are body-level actionability (no executable example or measurement command inline) and implicit validation checkpoints in the Check→Fix workflow.

Suggestions

Add one copy-paste-ready example inline in the Fix section (e.g., `<link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>`) so the body is actionable even before opening the reference.

Make the workflow's validation explicit: add a step after Fix such as "Re-run Lighthouse or reload with DevTools network panel open to confirm the connection is pre-resolved and no unused preconnects remain."

Trim the intro sentence and the "DNS lookup, TCP handshake, and TLS negotiation" bullet — connection-setup mechanics are knowledge Claude already has.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned, but the intro sentence ("can shave hundreds of milliseconds off the critical path by handling connection overhead ahead of time") and the DNS/TCP/TLS bullet explain connection mechanics Claude already knows — minor over-explanation that could be trimmed.

4 / 5

Actionability

The Fix section names the concrete element (`<link rel="preconnect">`) and the Quick Reference gives a usable limit ("limit to 2-4 most critical origins"), but the body contains no copy-paste example or measurement command; the executable details live entirely in references/rule.md.

3 / 5

Workflow Clarity

Check → Fix → Explain implies a sensible audit-then-fix sequence, and the Code Review section requires describing "the measurement method used to confirm the issue", but validation checkpoints are implicit — there is no explicit step to re-measure after applying the fix.

3 / 5

Progressive Disclosure

The body is a clear, well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) with a clearly signaled one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that file exists and contains the detailed examples, so content is appropriately split.

5 / 5

Total

15

/

20

Passed

Description

71%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 a clear, explicit trigger clause and names concrete verification tools, making it functional. Its main flaws are the garbled template phrase "related to Use preconnect for critical third-party origins", the omission of what the skill actually does when invoked, and trigger terms broad enough to overlap with sibling performance skills.

Suggestions

Fix the garbled phrase "related to Use preconnect for critical third-party origins" — either drop the rule-title boilerplate or integrate it grammatically (e.g., "...rendering delays caused by missing preconnect hints to critical third-party origins").

State the skill's core actions so the "what" is explicit: e.g., "Audits <link rel=\"preconnect\"> usage, adds hints for critical third-party origins, and removes them for non-essential domains."

Add narrower trigger terms like "preconnect", "resource hints", or "third-party latency" ahead of broad terms like "slow page loads" to reduce overlap with sibling performance skills.

DimensionReasoningScore

Specificity

The description lists several specific actions with named tools ("auditing slow page loads, heavy assets, or rendering delays", "Verify the actual bottleneck in DevTools, Lighthouse, or field data"), but never states the core fix actions (adding/removing preconnect hints), leaving minor gaps in coverage.

4 / 5

Completeness

An explicit "Use when auditing slow page loads, heavy assets, or rendering delays" trigger is present, but the "what" is weak and garbled — "related to Use preconnect for critical third-party origins" reads as a template artifact and the skill's actual fixing action is never stated.

4 / 5

Trigger Term Quality

Good natural keyword coverage including "slow page loads", "heavy assets", "rendering delays", "preconnect", "DevTools", and "Lighthouse", though common variations like "performance audit", "resource hints", or "third-party scripts" are missing.

4 / 5

Distinctiveness Conflict Risk

Trigger terms like "slow page loads" and "heavy assets" would naturally fire for many sibling performance skills (lazy loading, image optimization, bundling); the preconnect qualifier narrows the scope but only awkwardly.

3 / 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/preconnect/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.