Skip to content
TrustedSkillsbeta
Back to all skills

Dev Api Design

Listed
vasilyu1983·vlatest·backend·MIT

Helps with API, design as part of developing backend services and APIs workflows.

Repository

Install on your platform

This skill no longer installs under the name dev-api-design. vasilyu1983/ai-agents-public is deleted or private, so it cannot be installed from.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-24. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

vasilyu1983

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 failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 17 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: agentexperience.ax, cloud.google.com, create.t3.gg, datatracker.ietf.org, docs.pact.io….

    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.

    Hosts contacted

    github.comsource hostopensource.orgstandardsdatatracker.ietf.orgundeclaredwww.rfc-editor.orgundeclaredspec.openapis.orgstandardsspec.graphql.orgundeclaredgrpc.ioundeclaredprotobuf.devundeclaredwww.asyncapi.comundeclaredjson-schema.orgstandardswww.w3.orgstandardscloud.google.comundeclaredgoogle.aip.devundeclareddocs.stripe.comundeclaredwww.oreilly.comundeclaredowasp.orgundeclaredtrpc.ioundeclaredcreate.t3.ggundeclaredmodelcontextprotocol.iodocumentationplatform.openai.comdocumentationopenapi-generator.techundeclaredschemathesis.readthedocs.ioproject documentationdocs.pact.ioundeclaredopentelemetry.ioundeclaredagentexperience.axundeclaredapi.github.comsource host

    What it found (3 of 27)

    • skills/universal/dev-api-design/data/sources.json:14contacts datatracker.ietf.org
      "url": "https://datatracker.ietf.org/doc/html/rfc9110",
    • skills/universal/dev-api-design/data/sources.json:20contacts datatracker.ietf.org
      "url": "https://datatracker.ietf.org/doc/html/rfc9457",
    • skills/universal/dev-api-design/data/sources.json:32contacts datatracker.ietf.org
      "url": "https://datatracker.ietf.org/doc/draft-ietf-httpapi-idempotency-key-header/",

  • 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 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 vasilyu1983/ai-agents-public at 3ee3637d25.

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

Commit
3ee3637d25
Manifest
skills/universal/dev-api-design/SKILL.md
Scanned
31 files, 10,733 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 assists in designing, implementing, and documenting production-grade APIs using various styles including REST, GraphQL, gRPC, and tRPC. It leverages modern best practices for API development such as contract design (OpenAPI), versioning/deprecation strategies, authentication/authorization, rate limiting, pagination, error models based on RFC 9457, and developer documentation. The skill aims to guide the creation of operable-by-default APIs with features like idempotency, observability, and trace context.

When to use it

  • Designing a new backend service or API workflow.
  • Defining an OpenAPI contract for a REST API.
  • Implementing authentication and authorization mechanisms (e.g., JWT Bearer).
  • Creating consistent error responses based on RFC 9457.
  • Planning pagination strategies for list endpoints with large datasets.

Key capabilities

  • API design across multiple styles: REST, GraphQL, gRPC, tRPC
  • Contract-first API development using OpenAPI or GraphQL schema definition.
  • Error handling following RFC 9457 Problem Details format.
  • Implementation of authentication and authorization (e.g., JWT Bearer).
  • Rate limiting and idempotency strategies.
  • Pagination implementation with cursor-based approaches.
  • API versioning using URL versioning (/api/v1/resource).
  • Guidance on observability practices, including W3C Trace Context and request IDs.

Example prompts

  • "Design a REST API endpoint for retrieving user data, following OpenAPI standards."
  • "What are the key elements of an RFC 9457 Problem Details error response?"
  • "How can I implement cursor-based pagination for a list endpoint?"

Tips & gotchas

  • The skill emphasizes contract-first design using OpenAPI or GraphQL schema. Start with defining the API contract before implementation.
  • Familiarity with HTTP semantics (RFC 9110) and modern best practices is beneficial to maximize the skill's effectiveness.
  • Consider the performance implications of different pagination strategies when dealing with large datasets.