agentleFS
smukhsmukh/a11y-agent-skills/skills/accessible-authentication/SKILL.md

accessible-authentication

Skill8 starsChanged 2 months agoMITView on GitHub

1. Map each available authentication path and its initial, invalid, expired, retry, and successful states. Use test accounts and synthetic codes; preserve the site's security policy. 2. Read the authentication review guide for cognitive burden, credential entry, recovery, and policy boundaries. 3. Replay whole-value paste, password-manager entry where available, keyboard submission, and error recovery. Record what was actually exercised rather than inferring support from autocomplete markup. 4. Repair the source that owns the barrier. Re-run the same path, including failure…

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the authentication review guide for cognitive burden, credential entry, recovery, and policy boundaries.

    line 19
  2. Distinctive:

    Follow the guide's manual checks for browser/password-manager and screen-reader behavior.

    line 27
  3. Distinctive:

    Do not remove MFA, weaken rate limits, change account enumeration behavior, or invent a recovery policy.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Accessible authentication

Workflow

  1. Map each available authentication path and its initial, invalid, expired, retry, and successful states. Use test accounts and synthetic codes; preserve the site's security policy.
  2. Read the authentication review guide for cognitive burden, credential entry, recovery, and policy boundaries.
  3. Replay whole-value paste, password-manager entry where available, keyboard submission, and error recovery. Record what was actually exercised rather than inferring support from autocomplete markup.
  4. Repair the source that owns the barrier. Re-run the same path, including failure and retry, and add a behavioral test for the supported input mechanism.
  5. Follow the guide's manual checks for browser/password-manager and screen-reader behavior; report untested combinations explicitly.

Boundaries

General form labels and validation remain in accessible-forms. This skill owns the complete authentication path, including challenges outside the initial form. Do not remove MFA, weaken rate limits, change account enumeration behavior, or invent a recovery policy. A passing clipboard test does not prove password-manager support or WCAG conformance.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.