Skip to content
TrustedSkillsbeta
Back to all skills

Api Design Patterns

Checked
bobmatnyc·vlatest·backend·MIT

Helps with API, design, patterns as part of developing backend services and APIs workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add bobmatnyc/claude-mpm-skills --skill api-design-patterns -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

bobmatnyc

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.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

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 bobmatnyc/claude-mpm-skills at 718070a7d6.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
718070a7d6
Manifest
universal/web/api-design-patterns/SKILL.md
Scanned
7 files, 5,616 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill assists in designing robust and scalable APIs using established design patterns for REST, GraphQL, and gRPC. It provides guidance on versioning strategies, authentication methods, error handling, and pagination techniques to ensure API consistency and evolution. The skill emphasizes applying universal API design standards to create a positive developer experience.

When to use it

  • When designing new APIs or refactoring existing ones.
  • To select the appropriate API style (REST, GraphQL, or gRPC) based on specific requirements.
  • For guidance on implementing authentication (OAuth2, JWT, API keys), rate limiting (token bucket, fixed window, sliding window), and idempotency.

Key capabilities

  • API Style Selection: Guidance on choosing between REST, GraphQL, and gRPC.
  • Versioning Strategies: Techniques like URI versioning (/v1/users), header-based versioning, and content negotiation.
  • Pagination Methods: Implementation of offset, cursor, and keyset pagination.
  • Authentication Patterns: Support for OAuth2, JWT, and API key authentication.
  • Rate Limiting Techniques: Token bucket, fixed window, and sliding window rate limiting.
  • Idempotency Handling: Strategies using idempotency keys and conditional requests.
  • Universal Design Principles: Guidance on consistency, evolution, security by default, and developer experience.

Example prompts

  • "What are the best practices for versioning a REST API?"
  • "How do I implement pagination in a GraphQL API?"
  • "Compare and contrast OAuth2 and JWT authentication methods."
  • "Which API style is most suitable for building CRUD-focused APIs with HTTP caching?"

Tips & gotchas

  • The skill provides guidance based on established patterns; adapt them to your specific context.
  • Consider the trade-offs of each API style (REST, GraphQL, gRPC) before making a decision.
  • Plan for versioning and graceful deprecation from the initial design phase.