Skip to content
TrustedSkillsbeta
Back to all skills

Api Patterns

Checked
sickn33·vlatest·backend·MIT

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.

  1. 1

    Run this in your project

    terminal
    $ npx skills add sickn33/agentic-awesome-skills --skill api-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

sickn33

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 sickn33/antigravity-awesome-skills at 5a4cdd9df8.

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

Commit
5a4cdd9df8
Manifest
skills/api-patterns/SKILL.md
Scanned
1 file, 102 lines
Copies in repo
3 — 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

The api-patterns skill helps AI agents understand and generate common API design patterns, such as RESTful endpoints, GraphQL queries, and API versioning strategies. It provides guidance on structuring requests, handling authentication, and defining response formats for various types of APIs.

When to use it

  • Designing a new API for a web application or microservice architecture
  • Refactoring an existing API to follow best practices
  • Explaining API concepts to developers unfamiliar with REST or GraphQL

Key capabilities

  • Recognition of common RESTful endpoint structures
  • Generation of GraphQL query examples
  • Explanation of API versioning techniques (e.g., URL path, headers)
  • Guidance on authentication methods like OAuth and API keys

Example prompts

  • "Explain how to structure a RESTful API for a user management system."
  • "Generate an example of a GraphQL mutation for updating user data."
  • "What are the best practices for versioning an API?"

Tips & gotchas

  • This skill assumes basic knowledge of HTTP methods and request/response formats.
  • It may not cover domain-specific APIs (e.g., IoT or blockchain) in depth, so additional research is recommended for specialized use cases.