CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interaction-to-next-paint

Use when auditing slow page loads, heavy assets, or rendering delays related to Optimize interaction to next paint. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

72%

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/interaction-to-next-paint/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.

A lean, well-structured overview that correctly delegates implementation detail to a single real reference file. Its weaknesses are concentrated in the Fix section, which reads as generic hints rather than instruction, and the absence of an explicit verify-after-fixing loop.

Suggestions

Make the 'Fix' section actionable: name the concrete techniques (e.g., yielding with scheduler.yield()/setTimeout chunking, moving computation to a worker) or at least one short code snippet instead of repeating the Quick Reference bullets.

Add an explicit validation loop — re-measure INP after applying fixes and confirm responses are under 200ms before declaring the issue resolved.

Remove the duplicated INP definition (intro vs. 'Explain' section) and the redundant rule-page URL to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is short and tight, but contains minor over-explanation: the INP definition appears in both the intro ('it measures how quickly your page responds to user interactions throughout the session') and the 'Explain' section, and the rule-page URL at the bottom duplicates the frontmatter metadata. Not 5 for these small redundancies; not 3 because the padding is incidental, not structural.

4 / 5

Actionability

'Check' offers concrete guidance (named tools 'Chrome DevTools or PageSpeed Insights' plus a 'within 200ms' threshold), but 'Fix' is high-level hints ('Break up long tasks into smaller chunks', 'Use web workers for heavy computation') with no specific steps or code in the body — implementation is entirely deferred to the reference. Not 2 because the named tools, threshold, and real executable reference lift it above minimal; not 4 because the Fix section lacks any executable detail.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections imply a coherent measure-then-optimize sequence, and 'Verify interaction responses occur within 200ms' acts as an implicit checkpoint. Not 4 because no explicit validation or verification steps are stated (e.g., re-measure after fixes); not lower because this is a non-destructive, read-heavy audit task.

3 / 5

Progressive Disclosure

A concise overview body with a clearly signaled, one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — and the file exists with exactly that content (code examples, ~257 lines). No nested references, no content that should be inlined.

5 / 5

Total

15

/

20

Passed

Description

67%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.

A solid description with an explicit trigger clause, named tooling, and a verification-first framing that distinguishes it from generic performance advice. Its main weaknesses are missing the most common user phrasings (INP, Core Web Vitals) and a 'what' that undersells the skill's scope.

Suggestions

Add the terms users actually use when diagnosing this metric — 'INP', 'Core Web Vitals', 'page feels sluggish/unresponsive' — to the trigger clause.

Expand the 'what' to name the optimization capabilities the skill covers (e.g., measuring INP, breaking up long tasks, offloading to web workers), not just verification and recommendations.

DimensionReasoningScore

Specificity

Concrete actions with named tools ('auditing slow page loads, heavy assets, or rendering delays', 'Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes') go beyond generic domain-naming, but coverage of what the skill does is not comprehensive. Not 5 because it stops at audit/verify/recommend without mentioning the optimization actions it covers.

4 / 5

Completeness

Both 'what' ('Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes') and an explicit 'Use when...' trigger clause are present. Not 5 because the 'what' is a single action chain rather than a comprehensive statement of the skill's capabilities.

4 / 5

Trigger Term Quality

Natural phrases like 'slow page loads', 'heavy assets', and 'rendering delays' are present, but common variations users would actually say are missing — 'INP', 'Core Web Vitals', 'sluggish'/'unresponsive' page. Not 4 because those omissions are among the most likely phrases for this exact need, not just a few stray synonyms.

3 / 5

Distinctiveness Conflict Risk

The 'related to Optimize interaction to next paint' qualifier gives it a clear niche, but 'slow page loads' and 'heavy assets' could also trigger general performance-audit skills (LCP, bundle-size) — minor overlap with closely related skills.

4 / 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/interaction-to-next-paint/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.