Skip to content
TrustedSkillsbeta
Back to all skills

Backend Api Patterns

Checked
duyet·vlatest·backend

Helps with backend development, 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 duyet/codex-claude-plugins --skill backend-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

duyet

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 duyet/claude-plugins at fd0232514c.

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

Commit
fd0232514c
Manifest
team-agents/skills/backend-api-patterns/SKILL.md
Scanned
1 file, 530 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 provides knowledge of common patterns used in backend API design and implementation. It can explain architectural approaches like REST, GraphQL, gRPC, and event-driven architectures. The skill also understands considerations around security, scalability, and maintainability when building APIs.

When to use it

  • Design Review: Get feedback on the proposed architecture for a new backend API or microservice.
  • Troubleshooting: Understand why an existing API is performing poorly or exhibiting unexpected behavior.
  • Technology Selection: Evaluate different API technologies (REST, GraphQL, gRPC) to determine which best fits project requirements.
  • Learning & Education: Gain a better understanding of backend API design principles and patterns.

Key capabilities

  • Knowledge of REST architectural constraints.
  • Understanding of GraphQL query language and schema design.
  • Familiarity with gRPC for high-performance APIs.
  • Explanation of event-driven architectures and message queues.
  • Awareness of API security best practices (authentication, authorization).

Example prompts

  • "Explain the difference between REST and GraphQL."
  • "What are some common patterns for implementing rate limiting in a REST API?"
  • "How does gRPC compare to REST in terms of performance?"
  • "Describe an event-driven architecture for processing user signups."

Tips & gotchas

The skill's effectiveness depends on providing context about the specific technology stack or problem domain. Be prepared to describe existing systems or desired outcomes clearly for best results.