CtrlK
BlogDocsLog inGet started
Tessl Logo

accessible-authentication

Use when reviewing sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows. Evaluate the full authentication path, including error handling and backup methods, not just the primary login form.

70

Quality

86%

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

72%

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, actionable review overview that correctly offloads detailed code and standards to a real one-level-deep reference. Its main weakness is redundancy across the Check/Fix/Explain/Code Review sections and the lack of an explicit verify-after-fix feedback loop.

Suggestions

Collapse the overlapping Check and Code Review sections into one sequenced review checklist to remove restated flags and tighten conciseness.

Add an explicit verification step (e.g., 'After fixes, re-test sign-in, MFA, and recovery with a password manager and pasted/autofilled OTP') to give the workflow a clear feedback loop.

Move the duplicated rationale (cognitive/motor/low-vision barriers) into the reference file or trim it, since the intro paragraph and Fix/Explain sections restate the same 'why'.

DimensionReasoningScore

Conciseness

The body is mostly lean and task-oriented, but the Check, Fix, Explain, and Code Review sections restate the same flags (blocked paste, password-manager hostility, transcription, OTP handling) in slightly different wording, so it could be tightened. It is not a verbose wall of known-concept explanation, so it stays above 1.

2 / 3

Actionability

For an instruction-only review skill the guidance is concrete and specific: exact attributes to check (autocomplete="one-time-code", "current-password"), concrete flags to raise, and specific alternative paths (passkeys, magic links, device approval); per the scoring notes, absence of inline code is not penalized when guidance is actionable, and full code examples live in the referenced rule.md.

3 / 3

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is present and the Quick Reference acts as a checklist, but there is no explicit verify/re-check feedback loop and the Check and Code Review sections overlap rather than forming clearly sequenced checkpoints, fitting the score-2 anchor of steps listed with implicit or missing checkpoints.

2 / 3

Progressive Disclosure

The body is a concise overview that signals a single one-level-deep reference ("see references/rule.md"), and rule.md exists and holds the detailed code examples and standards, matching the score-3 anchor for a clear overview with well-signaled one-level-deep references.

3 / 3

Total

10

/

12

Passed

Description

100%

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 is specific, trigger-rich, and clearly distinguishes the skill's niche, with explicit "Use when" guidance covering both what it does and when to invoke it. It uses the standard third-person/trigger form with no fluff or over-claims.

DimensionReasoningScore

Specificity

The description names multiple concrete review targets ("sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows") and a concrete action ("Evaluate the full authentication path, including error handling and backup methods"), matching the score-3 anchor of listing several specific concrete actions.

3 / 3

Completeness

It answers both "what" ("Evaluate the full authentication path, including error handling and backup methods") and "when" (explicit "Use when reviewing..." trigger), satisfying the score-3 anchor for clearly answering both with explicit triggers.

3 / 3

Trigger Term Quality

It opens with "Use when reviewing sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows," covering the natural terms a user would say when requesting an auth accessibility review, aligning with the good-coverage score-3 anchor.

3 / 3

Distinctiveness Conflict Risk

Accessible-authentication review is a clear niche with distinct triggers (MFA, CAPTCHA, recovery, re-auth) unlikely to fire for unrelated skills, matching the score-3 anchor for a clear niche with distinct triggers.

3 / 3

Total

12

/

12

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.