CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

84%

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

A clean, token-efficient overview with a sensible audit-fix-review workflow and good progressive disclosure via one real reference file. The main gap is actionability: the body describes what to do but defers all executable code to the reference.

Suggestions

Include at least one small executable snippet (e.g., the web-vitals onINP call or a scheduler.yield example) directly in the body so Claude can act without opening the reference.

Add a brief validation/checkpoint note in the Fix section tying the 200ms threshold back to the measurement step.

DimensionReasoningScore

Conciseness

The body is lean and well-organized with tight Quick Reference, Check, Fix, and Explain sections; it assumes Claude's competence and pushes detail to the reference file rather than padding.

3 / 3

Actionability

Guidance is concrete in direction ('break up long tasks', 'use web workers') but the body itself contains no executable code or commands — those live only in references/rule.md, so it stops at descriptive instruction.

2 / 3

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is clear and unambiguous for this single-task skill, and it explicitly instructs verifying the bottleneck in DevTools/Lighthouse/field data before recommending changes.

3 / 3

Progressive Disclosure

The SKILL.md is a concise overview with a single, clearly signaled one-level reference to references/rule.md (which exists), keeping navigation shallow and easy.

3 / 3

Total

11

/

12

Passed

Description

77%

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 strong description with an explicit 'Use when...' trigger, concrete actions, and a distinct INP-focused niche. Its main weakness is omitting the canonical keyword 'INP' that users would actually say when asking about this metric.

Suggestions

Add the acronym 'INP' and the full phrase 'interaction to next paint' as trigger terms so the skill matches how users actually phrase this need.

Consider adding 'Core Web Vitals' or 'responsiveness' as natural keyword variations users commonly mention.

DimensionReasoningScore

Specificity

The description names concrete actions ('auditing slow page loads, heavy assets, or rendering delays' and 'Verify the actual bottleneck in DevTools, Lighthouse, or field data'), going beyond a vague domain label.

3 / 3

Completeness

It opens with an explicit 'Use when...' trigger clause and clearly states what the skill does (audit/verify INP-related issues), satisfying both the 'what' and 'when'.

3 / 3

Trigger Term Quality

It uses natural terms like 'slow page loads' and 'rendering delays', but the core trigger keyword 'INP' or 'interaction to next paint' is absent, so common user phrasing is only partially covered.

2 / 3

Distinctiveness Conflict Risk

The trigger is narrowly scoped to Optimize interaction to next paint (a specific Core Web Vital), making it clearly distinguishable from broader performance skills and unlikely to fire for the wrong one.

3 / 3

Total

11

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.