Skip to content
TrustedSkillsbeta
Back to all skills

Api Design Principles

Checked
rmyndharis·vlatest·backend·MIT

Helps with API, design, principles 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 rmyndharis/antigravity-skills --skill api-design-principles -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

rmyndharis

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 rmyndharis/antigravity-skills at 3eff4af253.

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

Commit
3eff4af253
Manifest
skills/api-design-principles/SKILL.md
Scanned
6 files, 1,768 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 equips AI agents with a foundational understanding of core API design principles, enabling them to evaluate and critique RESTful architectures. It helps ensure that generated interfaces prioritize clarity, consistency, and maintainability for human developers.

When to use it

  • Reviewing proposed API endpoints before implementation to catch structural flaws early.
  • Generating documentation that enforces standard naming conventions and resource hierarchy.
  • Auditing existing codebases to identify violations of RESTful best practices like proper HTTP method usage.
  • Designing stateless interactions where the agent must ensure requests are self-contained without session dependencies.

Key capabilities

  • Evaluates adherence to RESTful constraints (statelessness, cacheability, uniform interface).
  • Suggests improvements for endpoint naming and resource representation.
  • Identifies potential security risks related to improper access control or data exposure in API definitions.
  • Assists in structuring error responses and status codes according to industry standards.

Example prompts

  • "Critique this REST API design for compliance with standard principles and suggest specific improvements."
  • "Generate a set of API endpoints for a user management system that strictly follows RESTful conventions."
  • "Explain why using POST for updating resources violates API design best practices in this context."

Tips & gotchas

Ensure the agent has access to relevant schema definitions when evaluating complex APIs, as abstract principles may not apply uniformly without context. This skill focuses on architectural patterns rather than specific implementation languages or frameworks like Django or Spring.