Rest Api Design Patterns
CheckedHelps with REST APIs, API, design as part of developing backend services and APIs 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 manutej/crush-mcp-server --skill rest-api-design-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
manutej
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 manutej/crush-mcp-server at bb8eed14fe.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- bb8eed14fe
- Scanned
- 6 files, 8,660 lines
- Copies in repo
- 2 — all of them scanned
About this skill
What it does
This skill provides guidance and examples for designing REST APIs using established design patterns. It helps ensure your API is well-structured, maintainable, and scalable by applying proven techniques. The skill covers common scenarios and offers practical advice for implementing robust API solutions.
When to use it
- When starting a new backend project requiring a RESTful API.
- When refactoring an existing API to improve its design and consistency.
- To troubleshoot issues related to API usability or performance.
- For learning best practices in REST API development.
Key capabilities
- Provides examples of common REST API design patterns.
- Offers guidance on structuring API endpoints and resources.
- Helps ensure API maintainability and scalability.
- Covers practical considerations for robust API implementation.
Example prompts
- "Suggest a design pattern for handling resource versioning in my API."
- "How can I implement pagination effectively in my REST API?"
- "What are some best practices for error handling in a RESTful API?"
Tips & gotchas
This skill assumes you have a basic understanding of REST principles and HTTP methods. While it provides guidance, practical coding experience is still required to fully apply the patterns.