CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

debounce-throttle

Use when reviewing scripts, client components, bundles, or runtime behavior related to Debounce and throttle event handlers. Inspect both source code and the browser execution path so fixes target the real bottleneck or bug.

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/debounce-throttle/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 lean overview delegating code examples and framework specifics to a single, real, one-level-deep reference file. Its weaknesses are padding from known-concept explanations, duplicated review instructions across the Check and Code Review sections, and a Fix section that gives high-level direction without any inline executable guidance or concrete verification steps.

Suggestions

Cut the known-concept explanations — the opening motivation line and the debounce/throttle definitions in Quick Reference — and keep only the non-obvious specifics (the 150-300ms/100ms timing values and the listener-cleanup reminder).

Merge the redundant 'Check' and 'Code Review' sections into a single review section; both currently repeat near-identical instructions to review code for high-frequency event handlers.

Add one minimal inline debounce or throttle implementation (or surface a snippet from references/rule.md) in the Fix section, and turn 'state how the change should be verified in the browser' into a concrete verification step such as checking handler invocation frequency in the DevTools Performance panel.

DimensionReasoningScore

Conciseness

The body is short but spends tokens on concepts Claude already knows — 'Debounce: delays execution until activity stops (search inputs, form validation)' and the opening motivation line about UI jank and INP — and the 'Check' and 'Code Review' sections repeat near-identical review instructions, so it could be tightened rather than being fully lean.

3 / 5

Actionability

There is some concrete guidance ('Use 150-300ms delay for user input, 100ms for scroll/resize', the scroll/resize/input/mousemove event list, 'Flag exact imports, event handlers, runtime side effects') but no executable code in the body — the Fix section says only 'Add debounce or throttle to high-frequency event handlers' and defers all implementation to references/rule.md, leaving key details one hop away.

3 / 5

Workflow Clarity

A rough Check → Fix → Explain sequence is present, but checkpoints are only implicit: 'state how the change should be verified in the browser' directs Claude to describe verification rather than providing an actual validation step, and the redundant Check/Code Review sections blur the sequence.

3 / 5

Progressive Disclosure

The body is a well-organized ~35-line overview that clearly signals one level of external depth ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and references/rule.md exists, is self-contained (no nested references), and appropriately holds the code examples and framework guidance — matching the clear-overview anchor.

5 / 5

Total

14

/

20

Passed

Description

75%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 is well-constructed: it uses third-person imperative voice, has an explicit 'Use when...' trigger clause naming concrete artifacts, and occupies a clear niche around debounce/throttle event handling. Its main limitation is that the capability side leans on generic review/inspect verbs and omits common synonym triggers like 'rate limiting' or specific high-frequency event names.

DimensionReasoningScore

Specificity

Names the domain ('Debounce and throttle event handlers') and several concrete actions — 'reviewing scripts, client components, bundles, or runtime behavior' and 'Inspect both source code and the browser execution path' — but the actions are all review/inspect variants with minor coverage gaps, matching the 'several specific actions; minor gaps' anchor rather than the comprehensive 5.

4 / 5

Completeness

Both parts are present: the when is explicit ('Use when reviewing scripts, client components, bundles, or runtime behavior related to Debounce and throttle event handlers') and the what is stated ('Inspect both source code and the browser execution path so fixes target the real bottleneck or bug'), but the what describes inspection methodology rather than the concrete outcomes the skill produces, keeping it below the fully explicit 5.

4 / 5

Trigger Term Quality

'debounce', 'throttle', 'event handlers', 'client components', and 'bundles' are natural terms users would say, giving good keyword coverage; common variations like 'rate limiting', 'scroll/resize handlers', or 'high-frequency events' are missing, so it is not the comprehensive synonym-level 5.

4 / 5

Distinctiveness Conflict Risk

'Debounce and throttle event handlers' is a clear niche with distinct triggers, but the broad framing 'reviewing scripts, client components, bundles, or runtime behavior' creates minor overlap risk with closely related general JavaScript performance or code-review skills, matching anchor 4 rather than the minimal-conflict 5.

4 / 5

Total

16

/

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/debounce-throttle/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.