Skip to content
TrustedSkillsbeta
Back to all skills

Api Authentication

Checked
aj-geddes·vlatest·security·MIT

Provides API guidance and assistance for implementing security and authentication.

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 aj-geddes/useful-ai-prompts --skill api-authentication -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

aj-geddes

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 aj-geddes/useful-ai-prompts at 3f5182cfd7.

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

Commit
3f5182cfd7
Manifest
skills/api-authentication/SKILL.md
Scanned
6 files, 420 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 and assistance for implementing various API authentication strategies. It covers techniques like JWT tokens, OAuth 2.0, API keys, and session management, emphasizing secure practices to protect sensitive data and API endpoints. The skill offers reference implementations in Node.js and Python.

When to use it

  • Securing API endpoints
  • Implementing user login/logout flows
  • Managing access tokens and refresh tokens
  • Integrating OAuth 2.0 providers
  • Protecting sensitive data
  • Implementing API key authentication

Key capabilities

  • Guidance on implementing JWT (JSON Web Token) authentication.
  • Support for integrating with OAuth 2.0 providers.
  • Instructions for setting up API key authentication.
  • Reference implementations in Node.js and Python.
  • Best practices for secure token storage, password hashing, and secret key management.

Example prompts

  • "How do I implement JWT authentication in Node.js?"
  • "What's the best way to integrate OAuth 2.0 into my API?"
  • "Can you show me an example of using API keys for authentication?"

Tips & gotchas

  • Always use HTTPS for all authentication processes.
  • Store tokens securely, ideally in HttpOnly cookies.
  • Regularly rotate secret keys to maintain security.