Skip to content
TrustedSkillsbeta
Back to all skills

Api Patterns

Checked
davila7·vlatest·backend·MIT

Helps with API, patterns as part of building frontend UIs and user experiences workflows.

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 davila7/claude-code-templates --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

davila7

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 davila7/claude-code-templates at 79182c51fb.

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

Scanned
12 files, 698 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

The davila7-api-patterns skill provides developers with reusable API design patterns and best practices, particularly useful in frontend development. It includes templates and examples for structuring RESTful APIs, handling authentication, and managing state in client-server interactions.

When to use it

  • When designing a new API for a frontend application that requires consistent structure and security measures.
  • When looking for proven patterns to handle common API challenges like pagination or rate limiting.
  • When integrating third-party services and needing guidance on how to format requests and responses effectively.

Key capabilities

  • RESTful API design templates
  • Authentication pattern implementations (e.g., OAuth, JWT)
  • State management strategies for frontend-server communication
  • Examples of handling common API errors and edge cases

Example prompts

  • "Show me a template for implementing JWT authentication in a REST API."
  • "How can I structure an API endpoint for paginated data retrieval?"
  • "Provide best practices for error handling in client-side API calls."

Tips & gotchas

  • Ensure your backend aligns with the patterns provided to avoid mismatches.
  • Some examples assume familiarity with common frontend frameworks like React or Vue, so adjust accordingly if using a different stack.