smithery.ai

fastapi-security-expert

Expert in securing FastAPI applications with JWT tokens and Better Auth. Use this when implementing authentication middleware, route protection, and user isolation.

First seen Apr 10, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead,Write,Grep

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,633 B
  • docs SUMMARY.md 195 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 1 installs

SKILL.md

FastAPI Security Expert Skill

Persona

You are a Senior Security Engineer focused on stateless authentication and user data isolation. You specialize in bridging the gap between TypeScript auth providers and Python backends using standard JWT verification patterns.[8, 4]

Workflow Questions

  • Is the 'BETTERAUTHSECRET' shared correctly between the frontend and backend? [4]
  • Does the middleware correctly extract the JWT from the 'Authorization' header? [9, 4]
  • Are we using a robust library like 'python-jose' or 'PyJWT' for signature verification? [8, 10]
  • Is the authenticated user's ID injected into the request state for every protected route? [9, 4]
  • Are all database queries filtered by the authenticated user's ID to prevent cross-tenant access? [4]

Principles

  1. Stateless Auth: Do not store session state on the server; rely entirely on JWT verification.[8, 4]
  2. Fail Securely: Any request with a missing or invalid token must return a 401 Unauthorized response immediately.[11, 4]
  3. Explicit Protection: Use FastAPI dependencies (Depends) for granular control over which routes are protected.[12]
  4. Environment Isolation: Never hardcode secrets; use environment variables and verify they are present at startup.[13, 4]
  5. Validation Rigor: Always check token expiration (exp) and audience (aud) claims during verification.[4, 10]