redundant-entry

Use when reviewing any process that spans multiple screens, steps, or modal stages. Follow the real user journey and compare fields across steps instead of reviewing screens in isolation.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, lean instruction skill that delegates details appropriately to a single real reference file. It is actionable, clearly sequenced, and avoids explaining concepts Claude already knows.

Dimension	Reasoning	Score
Conciseness	The body is lean and well-organized into tight Quick Reference, Check, Fix, Explain, and Code Review sections; every token earns its place with only a brief, relevant motivational opening.	3 / 3
Actionability	Gives concrete, specific review guidance such as 'Flag fields that should be auto-populated or selectable' and 'Auto-populate repeat fields, add same-as toggles', which is actionable without needing code.	3 / 3
Workflow Clarity	The Check, Fix, Explain, Code Review sequence forms a clear review workflow with an explicit review criterion (flag non-prefilled repeated fields); adequate for a simple review skill.	3 / 3
Progressive Disclosure	The body is a concise overview with a single clearly signaled, one-level-deep reference to references/rule.md, which exists and holds the detailed code examples and best practices.	3 / 3
	Total	12 / 12 Passed

Description

67%

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 and clearly states what the skill does, scoring well on completeness. Specificity and trigger-term coverage are adequate but could be sharpened with more concrete review actions and the natural terms users say.

Suggestions

Add concrete user-facing trigger terms like 'checkout', 'signup', 'onboarding', or 'multi-step form' so the description matches language users actually say.

List a few more specific concrete actions (e.g., 'auto-populate repeated fields', 'add same-as toggles') to lift specificity toward a comprehensive set.

Tighten the niche by naming the accessibility context (e.g., 'WCAG 2.2 redundant entry') to reduce overlap with general UX review skills.

Dimension	Reasoning	Score
Specificity	Names the domain ('process that spans multiple screens, steps, or modal stages') and concrete actions ('Follow the real user journey', 'compare fields across steps'), but does not comprehensively list multiple distinct actions.	2 / 3
Completeness	Explicitly answers both what ('Follow the real user journey and compare fields across steps') and when ('Use when reviewing any process that spans multiple screens, steps, or modal stages') with an explicit trigger clause.	3 / 3
Trigger Term Quality	Includes natural terms like 'reviewing', 'screens', 'steps', and 'modal stages', but misses common variations users would actually say such as 'checkout', 'onboarding', 'forms', or 'redundant entry'.	2 / 3
Distinctiveness Conflict Risk	The cross-step field-comparison niche is fairly specific, but the trigger 'any process that spans multiple screens' is broad enough to overlap with sibling accessibility or UX review skills.	2 / 3
	Total	9 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/redundant-entry/SKILL.md
Commit: 48405aa

Reviewed: about 8 hours ago

Table of Contents

Discovery Implementation Validation

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.