CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

paste-inputs

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Allow pasting into form inputs. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

77%

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/paste-inputs/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.

A well-structured, lean skill page with excellent progressive disclosure — a single real, one-level-deep reference carrying the code examples and verification detail. The main weakness is the body's own actionability: the Check step names no concrete search commands or the JS-side paste-blocking pattern, deferring nearly all executable detail to the reference file.

Suggestions

Add a concrete search command to the Check section, e.g. `grep -rnE "onpaste|addEventListener\(['\"]paste" src/`, so offenders can be located without opening the reference.

Name the JavaScript paste-blocking pattern (e.g. `e.preventDefault()` in a 'paste' listener) in the Fix section, not just the `onpaste` HTML attribute, since both variants must be removed.

Trim the opening rationale sentence and the "Explain" section, which duplicate the 'Why It Matters' and security/accessibility rationale already in references/rule.md.

DimensionReasoningScore

Conciseness

The ~30-line body is lean and assumes competence — Quick Reference bullets like "Remove `onpaste=\"return false\"` from all input elements" are token-efficient. Minor over-explanation remains: the opening rationale sentence ("Restricting pasting makes it difficult... poor user experience") and the "Explain" section duplicate the 'Why It Matters' content already in references/rule.md. Not 5 because those few sentences could be trimmed; not 3 because there is no padded or tutorial-style material.

4 / 5

Actionability

Concrete anchors exist ("Remove `onpaste=\"return false\"`", "Do not block the 'paste' event"), but the Check section is a one-line directive ("Check the codebase for any JavaScript or HTML attributes that prevent users from pasting") with no search commands, and the JavaScript pattern (addEventListener('paste', e.preventDefault())) appears only in references/rule.md, not the body. This matches anchor 3 — some concrete guidance but incomplete — rather than 4, which would require mostly executable commands or code in the body itself.

3 / 5

Workflow Clarity

A clear Check → Fix → Explain sequence exists, and verification is addressed: the Code Review section says to "note how to verify the fix with browser accessibility tooling or assistive tech", while references/rule.md carries explicit automated (axe/Lighthouse) and manual (keyboard-only) checks. Minor gaps: the body's own verification is a single clause and the Code Review section reads as generic boilerplate. This is not a destructive/batch operation, so the cap of 3 does not apply; it sits above anchor 3 because checkpoints are present, if partially deferred.

4 / 5

Progressive Disclosure

The body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) with a single clearly signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and that file exists, contains the code examples and verification steps, and references no deeper files. This matches the anchor-5 example of a clear overview with well-signaled references.

5 / 5

Total

16

/

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.

A solid, third-person description with an explicit 'Use when...' clause and several concrete review actions. Its main limitation is that the trigger and action vocabulary is generic accessibility-review language; it lacks paste-specific natural terms (password managers, onpaste, copy-paste) that would sharpen both triggering and distinctiveness.

Suggestions

Add paste-specific natural trigger phrases users would actually say, e.g. "password field won't accept paste", "onpaste handler", or "copy-paste blocked".

Make the 'when' clause name concrete scenarios instead of restating the rule title, e.g. "Use when a form field blocks pasting, an input has onpaste='return false', or a password manager cannot fill a field".

DimensionReasoningScore

Specificity

The description lists several concrete review actions — "Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — but never names the concrete fix artifacts (e.g. `onpaste` handlers or `preventDefault` on paste), leaving minor gaps in coverage. Not 5 because the actions are generic review activities rather than a comprehensive set specific to the paste-blocking problem; not 3 because multiple distinct concrete actions are explicitly stated.

4 / 5

Completeness

Both parts are present: the 'what' ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and an explicit "Use when reviewing rendered HTML, interactive components, or design-system patterns related to Allow pasting into form inputs" trigger clause. Not 5 because the 'when' partly restates the rule name ("related to Allow pasting into form inputs") instead of concrete user scenarios like 'password field won't accept paste' or 'onpaste handler'.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "pasting into form inputs", "rendered HTML", "interactive components", "screen-reader output", "focus flow" are phrases a user or reviewer would plausibly say. Missing common variations like "password field", "onpaste", or "copy-paste blocked", so it falls short of the comprehensive-synonym anchor at 5 but sits above anchor 3's 'missing common variations' level only in part — overall closest to anchor 4.

4 / 5

Distinctiveness Conflict Risk

The paste-inputs rule is a clear niche with a distinct trigger phrase, but the broad review vocabulary ("keyboard behavior, focus flow, accessible names, and screen-reader output") overlaps with sibling accessibility-review skills, so minor conflict risk remains. Not 5 because those generic a11y phrases could plausibly fire other accessibility skills; not 3 because the rule-specific trigger clearly anchors it.

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/paste-inputs/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.