Api Patterns
CheckedHelps with API, patterns as part of agent workflows workflows.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add vudovn/ag-kit --skill api-patterns -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
vudovn
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.
Automated safety checks
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 vudovn/antigravity-kit at 549ba3dc2e.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- 549ba3dc2e
- Scanned
- 12 files, 700 lines
About this skill
What it does
This skill provides guidance and resources for designing APIs, focusing on principles and decision-making rather than rigid patterns. It offers a curated collection of documents covering various API styles (REST, GraphQL, tRPC), response structures, versioning strategies, authentication methods, rate limiting, documentation best practices, and security considerations. The goal is to help agents make informed choices when building APIs for 2025 and beyond.
When to use it
- When choosing between REST, GraphQL, or tRPC API styles.
- During the design phase of a new API, ensuring proper resource naming and HTTP method usage.
- When planning how to handle API versioning and evolution.
- To select appropriate authentication methods (JWT, OAuth, Passkey, API Keys).
- For guidance on structuring API responses and implementing pagination.
Key capabilities
- API Style Decision Tree: Provides a guide for choosing between REST, GraphQL, and tRPC.
- REST Design Guidance: Covers resource naming, HTTP methods, and status codes.
- Response Structure Patterns: Includes information on envelope patterns, error formats, and pagination.
- Versioning Strategies: Offers advice on URI, Header, and Query versioning approaches.
- Authentication Options: Explores JWT, OAuth, Passkey, and API Key authentication methods.
- Rate Limiting Techniques: Discusses Token Bucket and Sliding Window rate limiting.
- Documentation Best Practices: Provides guidance for OpenAPI/Swagger documentation.
Example prompts
- "What are the pros and cons of using GraphQL versus REST for this project?"
- "How should I structure API responses to include pagination?"
- "What are some best practices for versioning an API?"
- "Can you give me guidance on implementing rate limiting?"
Tips & gotchas
- Selective Reading: The skill emphasizes reading only the relevant files based on the specific context of the request. Refer to the "Content Map" within the skill's documentation to identify appropriate resources.
- Context Matters: API design choices should be driven by user requirements and project needs, not simply following pre-defined patterns.
- Consider Security: The skill includes guidance on security testing and addressing OWASP API Top 10 vulnerabilities.