Skip to content
TrustedSkillsbeta
Back to all skills

Two Factor Authentication Best Practices

Official
better-auth·vlatest·security

Provides tailored recommendations for implementing robust two-factor authentication based on your system's specifics.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add better-auth/skills --skill two-factor-authentication-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

better-auth

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned better-auth/skills at 20c9e88a5c.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
20c9e88a5c
Manifest
better-auth/twoFactor/SKILL.md
Scanned
1 file, 296 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill provides best practices for implementing two-factor authentication (2FA) to enhance account security. It covers methods like time-based one-time passwords (TOTP), hardware tokens, and backup codes, ensuring users can secure their systems effectively.

When to use it

  • Setting up 2FA for user accounts on web applications or services
  • Auditing existing authentication workflows for vulnerabilities
  • Educating teams on secure 2FA implementation strategies

Key capabilities

  • Recommends TOTP as a standard method for generating one-time codes
  • Explains the importance of hardware tokens for high-security environments
  • Highlights the need for backup codes to prevent lockouts due to lost devices
  • Advises against using SMS-based 2FA due to potential interception risks

Example prompts

  • "How should I implement TOTP in my web application?"
  • "What are the best practices for issuing backup codes during 2FA setup?"
  • "Why is hardware token authentication more secure than app-based 2FA?"

Tips & gotchas

  • Ensure users have access to a secondary authentication method, such as backup codes or a physical token.
  • Avoid relying solely on SMS-based 2FA due to vulnerabilities like SIM swapping.