Skip to content
TrustedSkillsbeta
Back to all skills

Authentication Patterns

Checked
travisjneuman·vlatest·security·MIT

Identifies common authentication vulnerabilities like weak passwords, MFA bypasses, and insecure session management in code.

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 travisjneuman/.claude --skill authentication-patterns -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

travisjneuman

Taken from the source listing. We haven't verified who controls this account.

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 travisjneuman/.claude at 050878886e.

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

Commit
050878886e
Manifest
skills/authentication-patterns/SKILL.md
Scanned
1 file, 508 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 guidance on various authentication patterns, enabling AI agents to securely verify user identities and control access to resources. It offers explanations of common methods like OAuth 2.0, OpenID Connect, and SAML, along with considerations for choosing the appropriate pattern based on specific application requirements. The skill aims to improve security posture by implementing robust authentication workflows.

When to use it

  • Integrating with third-party services: When your agent needs to access data or functionality from external platforms that require user authentication (e.g., Google Drive, Salesforce).
  • Building secure web applications: To guide the implementation of login and authorization features in a new application.
  • Auditing existing authentication flows: To identify potential vulnerabilities and areas for improvement in current security practices.
  • Implementing Single Sign-On (SSO): When you need users to authenticate once and access multiple related applications without re-entering credentials.

Key capabilities

  • Explanation of OAuth 2.0 principles and grant types.
  • Overview of OpenID Connect for identity verification.
  • Description of SAML for enterprise authentication scenarios.
  • Guidance on selecting appropriate authentication patterns.

Example prompts

  • "Explain the difference between Authorization Code Grant and Implicit Grant in OAuth 2.0."
  • "What are the security considerations when implementing OpenID Connect?"
  • "Recommend an authentication pattern suitable for a mobile application accessing a REST API."

Tips & gotchas

This skill assumes some basic understanding of web development and security concepts. The complexity of implementation will vary significantly depending on the chosen authentication pattern and specific integration requirements.