API Security Review
Review API security including authentication, authorization, rate limiting, input validation, and data exposure.
Install
/plugin marketplace add sethdford/claude-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add sethdford/claude-skills --skill api-security-reviewgit clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/security/application-security/skills/api-security-review ~/.claude/skills/api-security-reviewPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# API Security Review Review APIs for authentication, authorization, rate limiting, input validation, and data exposure risks. ## Context You are a senior security architect reviewing API security for $ARGUMENTS. APIs are high-value targets because they often bypass UI validation and directly access backend systems. Common API vulnerabilities: broken authentication, missing authorization, rate limit bypass, input injection, excessive data exposure. ## Domain Context - **API Authentication**: API keys, OAuth 2.0, JWT, mTLS, basic auth (deprecated) - **Authorization**: Role-based access control (RBAC), attribute-based access control (ABAC), resource ownership checks - **Rate Limiting**: Per-user, per-IP, per-endpoint; prevents brute force and DoS - **Data Exposure**: Over-fetching (returning unnecessary fields), under-fetching (multiple requests), error messages revealing internals - **API Versioning**: Managing breaking changes, deprecation timelines ## Instructions 1. **Review Authentication**: - **API Keys**: Are keys stored securely? Rotated regularly? Can they be revoked? - **OAuth 2.0**: Is the correct flow used? (Authorization Code for web apps, PKCE for mobile, Client Credentials for service-to-service) - **JWT**: Signed with strong algorithm (RS256, not HS256 unless symmetric key is secure)? Verified on every request? Expiration enforced? - **mTLS**: Certificates exchanged, validated, and rotated regularly? 2. **Review Authorization**:
Details
- Skill name
api-security-review- Repository
- sethdford/claude-skills
- Path
security/application-security/skills/api-security-review/SKILL.md- License
- MIT
- Repo updated
- 11 March 2026
FAQ
What does the API Security Review skill do?
Review API security including authentication, authorization, rate limiting, input validation, and data exposure.
How do I install the API Security Review skill?
Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is API Security Review popular?
It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.
Related skills
A B Test Design
48sethdford/claude-skills
Design rigorous A/B tests with hypotheses, variants, metrics, and sample size calculations.
A B Test Design Pm
48sethdford/claude-skills
Analytics and experimentation skill for product managers.
Abuse Case Design
48sethdford/claude-skills
Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.
Asset Inventory
48sethdford/claude-skills
Create a comprehensive inventory of assets (data, systems, infrastructure, people) and their criticality, value, and dependencies. Use when prioritizing threats and allocating security resources.
Alert Triage
48sethdford/claude-skills
Triage security alerts to classify as true/false positives and prioritize investigation and response.
Certificate Management
48sethdford/claude-skills
Manage digital certificates for HTTPS, mutual TLS, code signing, and infrastructure security.
Browse the most popular Claude skills, all security skills, or write your own with the skills generator.