Skip to content
TrustedSkillsbeta
Back to all skills

Oauth

Checked
mcollina·vlatest·security·MIT

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

mcollina

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 mcollina/skills at 856efd268a.

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

Scanned
2 files, 187 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 OAuth skill enables AI agents to securely authenticate and authorize access to external services using the standard OAuth 2.0 protocol. It manages the flow of credentials, allowing agents to act on behalf of users without exposing long-term secrets.

When to use it

  • Connecting an agent to third-party APIs like Google Drive, GitHub, or Twitter for data retrieval.
  • Granting temporary, limited-scope access to sensitive resources instead of using static API keys.
  • Automating workflows that require user consent verification before interacting with external platforms.
  • Implementing secure delegation where one application acts on behalf of another.

Key capabilities

  • Handles the complete OAuth 2.0 authorization flow initiation and completion.
  • Manages token exchange to obtain access tokens for API calls.
  • Supports various grant types defined by the OAuth specification.
  • Facilitates secure user consent prompts during the authentication process.

Example prompts

  • "Connect my Google Calendar using OAuth so I can schedule meetings."
  • "Authenticate with GitHub via OAuth to fetch my recent commit history."
  • "Set up a Twitter connection with limited read-only scope using OAuth."

Tips & gotchas

Ensure your application has registered a valid redirect URI with the identity provider before attempting authentication. Always validate the state parameter during the flow to prevent cross-site request forgery (CSRF) attacks, even when automating interactions.