CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

event-delegation

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

Quality

74%

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/event-delegation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 a well-structured, appropriately brief overview with a real one-level-deep reference file holding the code examples, and the Check/Fix directives are concrete. Its main weaknesses are an introductory paragraph that re-explains well-known event-delegation rationale and a Code Review section that duplicates the frontmatter description.

Suggestions

Delete or compress the opening rationale paragraph — Claude already knows why per-element listeners are costly — and let the Quick Reference bullets carry the essentials.

Replace the duplicated 'Code Review' paragraph with a short verification checklist (e.g., confirm the delegated listener works for newly added elements and that the old per-element listeners were removed).

Number the Check → Fix → Verify sequence so the workflow order and its verification checkpoint are explicit.

DimensionReasoningScore

Conciseness

The opening paragraph ('Adding hundreds of individual event listeners... consumes significant memory and creates performance overhead... event delegation solves both problems at once') explains event-delegation rationale that Claude already knows, and the 'Code Review' section largely repeats the frontmatter description ('Review scripts, client components, and browser execution paths related to...'). Not score 4 because more than minor trimming is possible; not score 2 because the body is short and the Quick Reference and Check/Fix sections are tight.

3 / 5

Actionability

The guidance is concrete and directive: 'Find any code in this file that attaches the same event handler to multiple elements in a loop', 'Refactor these per-element event listeners to use event delegation on the common parent container', 'Use event.target.closest() to identify the intended target element'. Implementation code is appropriately deferred to the existing references/rule.md, which contains the pattern and closest() examples. Not score 5 because the inline guidance lacks even a minimal delegation snippet and verification steps are described only abstractly ('state how the change should be verified').

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a coherent review-then-refactor sequence, and the Code Review section does call for verification ('state how the change should be verified in the browser'). Not score 5 because the sections are unnumbered with no explicit ordering or validation checkpoint between check and fix; not score 3 because the sequence is clear and the operation is non-destructive single-file review, so no validation cap applies.

4 / 5

Progressive Disclosure

The ~30-line body is a clean overview with well-labeled sections, and the pointer 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' is clearly signaled; the referenced file exists, is one level deep, and itself contains the code examples with no nested references. Under the simple-skill guidance this fully matches the clear-overview/one-level-deep anchor.

5 / 5

Total

16

/

20

Passed

Description

66%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 an explicit 'Use when' trigger clause and names the domain and inspection actions, but it is built from a templated sentence with a duplicated rule-name fragment ('related to Use event delegation for dynamic content') that hurts readability, and its trigger scope is broad enough to overlap with generic JS review skills.

Suggestions

Rewrite the duplicated fragment into a grammatical trigger clause, e.g., 'Use when reviewing scripts, client components, or runtime behavior involving event listeners on dynamic content (AJAX-loaded lists, rendered tables).'

State the skill's concrete operations instead of generic review verbs — e.g., 'Detects per-element listener attachment in loops and refactors it to parent-based event delegation using event.target.closest()'.

Narrow the trigger terms to the rule's actual domain (event listeners, click handlers, dynamic lists) to reduce conflict with other JavaScript review skills.

DimensionReasoningScore

Specificity

The description names the domain ('Use event delegation for dynamic content') and two concrete actions ('reviewing scripts, client components, bundles, or runtime behavior' and 'Inspect both source code and the browser execution path'), but coverage is not comprehensive — the actions are generic review/inspect verbs rather than the skill's actual operations (check for per-element listeners, refactor to delegation, explain). Not score 4 because it does not list several specific actions with only minor gaps; not score 2 because it goes beyond naming the domain to state what the skill does with the inspection path.

3 / 5

Completeness

Both 'what' and 'when' are present: the explicit trigger clause 'Use when reviewing scripts, client components, bundles, or runtime behavior related to...' covers when, and 'Inspect both source code and the browser execution path so fixes target the real bottleneck or bug' covers what. Not score 5 because the 'what' is weakened by the awkward embedded duplication 'related to Use event delegation for dynamic content', which reads as a template error and muddies the capability statement; not score 3 because both halves are explicitly stated.

4 / 5

Trigger Term Quality

Good keyword coverage with natural terms users would say when this skill applies: 'scripts, client components, bundles, or runtime behavior', 'event delegation', 'dynamic content', 'browser'. A few common variations are missing — e.g., 'event listeners', 'click handlers', 'AJAX-loaded content'. Not score 5 because synonym coverage is incomplete; not score 3 because the present terms are natural phrasings, not just technical jargon.

4 / 5

Distinctiveness Conflict Risk

The trigger scope 'reviewing scripts, client components, bundles, or runtime behavior' is quite broad and would overlap with many other JavaScript review skills; only the embedded event-delegation phrase narrows it. Score 4 is not warranted ('minor overlap risk with closely related skills') because generic script-review triggers could fire this skill for unrelated performance or bug reviews.

3 / 5

Total

14

/

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/event-delegation/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.