CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

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

78%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 tidy, well-structured single-purpose skill that delegates detail appropriately to references/rule.md. The main weaknesses are minor over-explanation of known concepts and the lack of an explicit verification checkpoint inline.

Suggestions

Drop or shorten the rationale-heavy intro sentence and the 'Explain' meta-section to assume Claude's understanding of why paste-blocking is harmful.

Add an explicit verification checkpoint in the body (e.g., 'Confirm paste works in the rendered input via keyboard/screen-reader testing') rather than only pointing to the reference.

DimensionReasoningScore

Conciseness

The body is lean and sectioned, but the opening sentence ('Restricting pasting makes it difficult for users to use password managers...') and the 'Explain' section restate rationale Claude already knows and could be trimmed.

4 / 5

Actionability

Gives concrete, executable guidance ('Remove any code (e.g., onpaste="return false")') and clear Quick Reference dos/don'ts; executable code examples live in the reference file, which is acceptable for an instruction-only skill but leaves a minor gap inline.

4 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence with a verification pointer ('note how to verify the fix with browser accessibility tooling'), but no explicit validate-then-retry checkpoint in the body itself.

4 / 5

Progressive Disclosure

A well-organized overview with clearly signaled, one-level-deep navigation to references/rule.md (verified present) for full details, code examples, and framework-specific guidance.

5 / 5

Total

17

/

20

Passed

Description

83%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 well-constructed description with an explicit 'Use when' trigger and a concrete, multi-action 'what' clause. It is distinct enough for the paste-inputs niche, though trigger-term coverage could include more natural synonyms and the review actions are somewhat generic to accessibility auditing.

Suggestions

Add natural trigger synonyms such as 'paste event', 'onpaste', and 'password fields' so the description matches how users actually phrase the request.

Tie the review actions more tightly to the paste rule (e.g., 'check for paste-blocking attributes and event handlers') rather than generic accessibility inspection.

DimensionReasoningScore

Specificity

Names the domain plus several concrete review actions ('inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), but the actions are generic accessibility-review verbs rather than paste-specific operations, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (check native semantics, inspect keyboard/focus/accessible-name/screen-reader output) and 'when' via a clear 'Use when reviewing...' trigger clause with concrete triggers.

5 / 5

Trigger Term Quality

Includes natural phrases a user might say ('Allow pasting into form inputs', 'rendered HTML', 'interactive components', 'design-system patterns'), but misses common synonyms like 'paste event', 'onpaste', and 'password fields'.

4 / 5

Distinctiveness Conflict Risk

The paste-specific framing gives it a clear niche, but the broad 'reviewing rendered HTML, interactive components, or design-system patterns' trigger creates minor overlap risk with sibling accessibility-review skills.

4 / 5

Total

17

/

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.

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.