Skip to content
TrustedSkillsbeta
Back to all skills

Oauth Implementation

Checked
mindrally·vlatest·security·Apache-2.0

Provides OAuth guidance and assistance for implementing security and authentication.

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 mindrally/skills --skill oauth-implementation -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

mindrally

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 mindrally/skills at 7682ca7771.

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

Scanned
1 file, 353 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 enables AI agents to securely authenticate and authorize access to external services using OAuth protocols. It handles the complex flow of token exchange, user consent, and session management required for safe third-party integrations.

When to use it

  • Connecting an agent to protected APIs like Google Drive or GitHub without exposing hardcoded credentials.
  • Implementing secure login flows where users must grant specific permissions before data access is allowed.
  • Managing refresh tokens to maintain long-term access to services after initial user authorization expires.
  • Ensuring compliance with security standards when integrating AI agents into enterprise environments.

Key capabilities

  • Manages OAuth 2.0 and OpenID Connect authentication flows.
  • Handles secure token generation, validation, and expiration logic.
  • Facilitates user consent screens for permission delegation.
  • Supports state management to prevent cross-site request forgery attacks during the login process.

Example prompts

  • "Set up OAuth authentication for my AI agent to access a private Slack channel securely."
  • "How can I configure this skill so users must approve data sharing before the agent connects to their email?"
  • "Implement an OAuth flow that automatically refreshes access tokens when they expire without interrupting the user session."

Tips & gotchas

Ensure your client ID and secret are stored in environment variables rather than hardcoding them into the agent's configuration. Always validate the redirect URI explicitly during setup to prevent unauthorized callback handling.