jwt-verify
Implement JWT verification middleware in FastAPI for user auth. Use when securing APIs or handling tokens.
Best use case
jwt-verify is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Implement JWT verification middleware in FastAPI for user auth. Use when securing APIs or handling tokens.
Teams using jwt-verify should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/jwt-verify/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How jwt-verify Compares
| Feature / Agent | jwt-verify | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Implement JWT verification middleware in FastAPI for user auth. Use when securing APIs or handling tokens.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# JWTVerify Instructions
Input: Request with Authorization header, shared secret.
Output: Verified user claims or 401 error.
Steps:
1. Install dependencies if needed (jose, fastapi-security).
2. Generate middleware code.
Example Code:
from fastapi import Depends, HTTPException
from jose import JWTError, jwt
from fastapi.security import HTTPBearer
security = HTTPBearer()
async def verify_jwt(token: str = Depends(security)):
try:
payload = jwt.decode(token.credentials, SECRET_KEY, algorithms=["HS256"])
return payload
except JWTError:
raise HTTPException(401, "Invalid token")Related Skills
inspequte-rule-verify
Perform isolated, file-based verification of an inspequte rule change using verify-input/. Use when producing a go/no-go verification report from spec.md, patch/diff, and report files without reading plan.md or chat logs.
docs-verify
Validates documentation quality and freshness — checks for broken links, stale content, llms.txt sync, image issues, heading hierarchy, and badge URLs. Runs locally or in CI. Use to catch documentation decay before it reaches users.
api-documentation-verify
Verifies API documentation against source code to eliminate fabricated claims, ensure accuracy, and validate examples. Zero tolerance for unverified claims, marketing language, or non-runnable code examples. Use before committing API docs or during documentation reviews.
twilio-verify
Verify: 2FA SMS/voice/email, TOTP, phone verification, Verify Guard fraud prevention, SNA
aposd-verifying-correctness
Verify code correctness before claiming done or committing. Run 6-dimension checklist: requirements coverage, concurrency safety, error handling, resource management, boundary conditions, and security. Output PASS/FAIL per dimension with final DONE/NOT DONE verdict. Use after implementation as pre-commit gate. Triggers on: is it done, ready to commit, verify correctness, did I miss anything, pre-commit check.
verify-issue
Verify a completed issue by comparing implementation against acceptance criteria, running tests, and critiquing the work. Adds review notes as a comment on the ticket. Supports both Linear and Jira backends via progressive disclosure. Use as the final step in the issue workflow after execute-issue, when the user mentions "verify", "review", or "check" an issue.
32-analyze-verify-150
[32] ANALYZE. Ensure every critical claim has verifiable evidence with confidence levels. Each fact must have source + confidence percentage. If confidence <85%, enter Loop150 to find more sources. Use for critical decisions, factual claims, legal/compliance work, or any situation where unverified claims are dangerous.
emaillistverify-automation
Automate Emaillistverify tasks via Rube MCP (Composio). Always search tools first for current schemas.
verify-information-rule
This rule ensures that the AI always verifies information before presenting it, avoiding assumptions and speculation.
add_platform.verify
Sets up platform directories and verifies deepwork install works correctly. Use after implementation to confirm integration.
verify-claude-setup
Verify .claude directory configuration is complete and correct. Use when checking if agents, hooks, rules, and memory are properly set up, or after making changes to .claude configuration.
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.