CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

72%

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/redundant-entry/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 clean, short overview that defers code and implementation detail to a real, well-signaled reference file, and its guidance is concrete and actionable for an instruction-only skill. Its main cost is redundancy: the motivation paragraph and the Check/Code Review sections repeat content that lives in (or duplicates) references/rule.md, which could be tightened without losing clarity.

Suggestions

Merge the near-duplicate 'Check' and 'Code Review' sections into a single review section to remove the repeated 'review the flow and flag repeated fields' guidance.

Drop or compress the opening motivation paragraph — 'Why It Matters' in references/rule.md already covers the same rationale, so the body can start with the Quick Reference.

DimensionReasoningScore

Conciseness

Mostly efficient, but the opening motivation paragraph ('Re-entering the same information increases cognitive load, slows task completion...') duplicates rule.md's 'Why It Matters' section, and the 'Check' and 'Code Review' sections near-duplicate the same instruction ('Review this multi-step flow for information that is requested more than once... Flag fields' vs 'Review multi-step forms, checkout, onboarding, support, and account flows... Flag exact steps'). The repetition is more than minor, so it does not reach the 'efficient' anchor.

3 / 5

Actionability

Concrete, executable directives for an instruction-only skill: 'Auto-populate repeated fields or offer a clear selection such as "same as billing"', 'Review checkout, signup, onboarding, and support flows step by step', and the explicit exception rule 'Password confirmation can be a valid security exception, but general profile data is not'. Code examples are appropriately deferred to references/rule.md; a 5 would require the common cases to be covered inline.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a clear, unambiguous sequence for this single-purpose review skill, and the referenced rule.md supplies pass/fail thresholds and verification steps. The body itself does not inline those validation checkpoints, which is a minor gap keeping it below the explicit-validation anchor.

4 / 5

Progressive Disclosure

A short, well-sectioned body with a single clearly signaled, one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md'. The file exists in the bundle and contains exactly that content, so the split between overview and detail is clean and easy to navigate.

5 / 5

Total

16

/

20

Passed

Description

62%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 explicitly pairs a 'Use when...' trigger with a concrete reviewing method, so it clearly answers both what and when. Its weaknesses are the missing natural trigger synonyms (redundant entry, auto-populate, checkout/forms) and a thin set of concrete capabilities, which limit trigger matching and specificity.

Suggestions

Add the natural terms users would actually say — 'redundant entry', 're-entering the same information', 'auto-populate', 'multi-step forms', 'checkout flows' — so the description triggers on real user phrasing instead of abstract process language.

State the concrete outputs, e.g. 'flags repeated fields that lack prefill or a "same as" selection and recommends auto-population', to broaden the list of specific capabilities beyond a single method sentence.

Mention the WCAG 2.2 / accessibility framing to sharpen distinctiveness against generic UX or flow-review skills.

DimensionReasoningScore

Specificity

The description names the domain (reviewing multi-step processes) and 1-2 concrete actions — 'Follow the real user journey and compare fields across steps instead of reviewing screens in isolation' — but does not list several specific capabilities as the score-4 anchor requires. The actions are more concrete than the generic score-2 anchor, so 3 is the best fit.

3 / 5

Completeness

Both parts are explicit: the 'when' is 'Use when reviewing any process that spans multiple screens, steps, or modal stages' and the 'what' is 'Follow the real user journey and compare fields across steps'. The when-clause is explicit but abstract rather than tied to concrete user-mention trigger phrases (e.g., 'when the user mentions redundant entry or auto-population'), so it sits between the 4 and 5 anchors, and closer to 4.

4 / 5

Trigger Term Quality

Some relevant keywords are present ('multiple screens, steps, or modal stages', 'fields', 'user journey'), but the natural phrases a user would actually say — 'redundant entry', 're-entering the same information', 'auto-populate', 'multi-step form', 'checkout' — are missing; even the rule's own name never appears. More than a few natural terms are missing, so it does not reach the good-coverage anchor.

3 / 5

Distinctiveness Conflict Risk

'compare fields across steps instead of reviewing screens in isolation' is a distinctive reviewing method that clearly differentiates this from generic review skills. However, 'reviewing any process that spans multiple screens, steps, or modal stages' is fairly broad and could minorly overlap with general UX or flow-review skills, so it does not earn the clear-niche anchor.

4 / 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/redundant-entry/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.