skills sourced live from GitHub · all skills listed are free · each skill is provided under its author's license.
home / Security / API Security Best Practices Skill by @sickn33
The skill is the skills/api-security-best-practices folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.
Implement secure API design patterns including authentication, authorization, input validation, rate limiting, and protection against common API vulnerabilities.
Walks through secure API design: authentication, authorisation, input validation, rate limiting and protection against common API vulnerabilities, with a check of inputs and prerequisites.
The original SKILL.md is organised into these sections:
Written and maintained by @sickn33. It is published under the MIT license, which allows reuse with attribution. See the author profile. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.
# API Security Best Practices Review the request boundary from caller identity through authorization, validated input, storage and observable response. Preserve the application's actual identity provider and data model rather than introducing a second authentication system. ## When to Use Use when adding a protected endpoint, reviewing object access, replacing permissive request parsing, or investigating an API abuse path. For a concrete defect, start with the failing route and its callers; do not deploy unrelated security infrastructure. ## Inputs and prerequisites Record the routes, caller/tenant model, identity provider, token contract, runtime and locked dependency versions, database schema, proxy topology and authorized test scope. Use synthetic identities in a test environment. Existing task authorization carries forward; production scans, account writes and message sends need their own authority. …
Excerpt only, quoted from the author's repository. Open the repository for the complete file.