Skip to content
TrustedSkillsbeta
Back to all skills

Api Development Patterns

Checked
kaakati·vlatest·backend

Helps with API, patterns as part of agent workflows workflows.

Repository

Install on your platform

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

Installs under a different name. Its SKILL.md names it API Development Patterns, not the name it is listed under, so the command below uses that name.
  1. 1

    Run this in your project

    terminal
    $ npx skills add kaakati/rails-enterprise-dev --skill "API Development 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

kaakati

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 kaakati/rails-enterprise-dev at bd0b7c1cc3.

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

Commit
bd0b7c1cc3
Manifest
plugins/reactree-rails-dev/skills/api-development-patterns/SKILL.md
Scanned
2 files, 2,284 lines
Copies in repo
2 — all of them scanned
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 provides guidance and examples for applying common API development patterns. It helps developers design robust, scalable, and maintainable APIs by leveraging established solutions to recurring challenges. The focus is on enterprise-level API development practices, promoting consistency and reducing complexity.

When to use it

  • When designing a new public or internal API.
  • Refactoring an existing API for improved performance or maintainability.
  • Troubleshooting issues related to API scalability or security.
  • Onboarding new developers to your team's API development standards.
  • Ensuring APIs adhere to architectural best practices.

Key capabilities

  • Provides examples of common API patterns.
  • Offers guidance on applying these patterns in enterprise environments.
  • Focuses on scalability and maintainability considerations.
  • Supports consistent API design across teams.

Example prompts

  • "Show me an example of the 'Command' pattern for a REST API."
  • "What are some best practices for versioning an API?"
  • "How can I implement rate limiting in my API using the 'Circuit Breaker' pattern?"
  • “Explain how to use the Adapter pattern when integrating with a legacy system.”

Tips & gotchas

This skill assumes a basic understanding of API design principles and common architectural patterns. While it provides examples, adapting them to specific contexts may require additional expertise and consideration of your project’s unique requirements.