CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

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

Quality

Content

72%

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 body that uses progressive disclosure effectively to push detail into a real reference file. Its main weakness is actionability: the body itself contains only directive prompts and no executable code, relying on the reference for everything concrete.

Suggestions

Inline one minimal executable debounce/throttle snippet (or a copy-paste listener example) in the body so the skill is actionable without opening the reference.

Surface at least one validation/verification checkpoint directly in the body (e.g. 'confirm the handler fires at most once per N ms in DevTools') rather than delegating all verification to references/rule.md.

Add concrete event-name triggers (scroll, resize, input, mousemove) to the Check/Code Review sections to match how users describe the problem.

DimensionReasoningScore

Conciseness

The ~30-line body is lean: a short intro, a compact Quick Reference with concrete delay values, and brief action sections, delegating all detailed material to references/rule.md. Every section earns its place with minimal concept restatement.

3 / 3

Actionability

The body provides concrete specifics (150-300ms / 100ms delays) but no executable code — only directive prompts ('Add debounce or throttle to high-frequency event handlers'), with the actual code examples living entirely in the reference file.

2 / 3

Workflow Clarity

The Check / Fix / Explain / Code Review sections give a loose sequence, but there are no explicit validation checkpoints or feedback loops in the body; the verification steps are delegated to the reference rather than surfaced here.

2 / 3

Progressive Disclosure

A clear overview with a well-signaled one-level-deep reference ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), and the referenced file exists and holds the detailed material, keeping content appropriately split.

3 / 3

Total

10

/

12

Passed

Description

75%

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 clear, well-triggered description with an explicit 'Use when' clause and a distinct niche, weakened only by slightly technical trigger terms and a single-verb action set. It cleanly answers what and when without fluff.

DimensionReasoningScore

Specificity

Names the domain and concrete actions ('reviewing scripts, client components, bundles, or runtime behavior', 'Inspect both source code and the browser execution path'), but these are variants of a single review/inspect activity rather than multiple distinct concrete actions like the score-3 anchor's extract/fill/merge.

2 / 3

Completeness

Explicitly answers both what (review/inspect debounce and throttle handlers and execution paths) and when via the 'Use when reviewing scripts, client components, bundles, or runtime behavior related to Debounce and throttle event handlers' trigger clause.

3 / 3

Trigger Term Quality

'Debounce and throttle event handlers' is a natural user term, but the description leans technical ('bundles', 'runtime behavior', 'browser execution path') and omits the common event names (scroll, resize, input, search) users would actually mention.

2 / 3

Distinctiveness Conflict Risk

Targets a specific, well-bounded niche (debounce/throttle event-handler review) with distinct triggers, making it unlikely to fire for unrelated skills.

3 / 3

Total

10

/

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.