agentsclimarketplace
Sign in

Api design principles

Skill AravindS-Wick/aravindhan-skills/skills/library/api-design-principles

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time.From its SKILL.md

Install
npx -y skills add AravindS-Wick/aravindhan-skills --skill api-design-principles

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.4 KB, 244 tokens by cl100k_base, as published. Nobody here has run it

API Design Principles

Master REST and GraphQL API design principles to build intuitive, scalable, and maintainable APIs that delight developers and stand the test of time.

Use this skill when

  • Designing new REST or GraphQL APIs
  • Refactoring existing APIs for better usability
  • Establishing API design standards for your team
  • Reviewing API specifications before implementation
  • Migrating between API paradigms (REST to GraphQL, etc.)
  • Creating developer-friendly API documentation
  • Optimizing APIs for specific use cases (mobile, third-party integrations)

Do not use this skill when

  • You only need implementation guidance for a specific framework
  • You are doing infrastructure-only work without API contracts
  • You cannot change or version public interfaces

Instructions

  1. Define consumers, use cases, and constraints.
  2. Choose API style and model resources or types.
  3. Specify errors, versioning, pagination, and auth strategy.
  4. Validate with examples and review for consistency.

Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Resources

  • resources/implementation-playbook.md for detailed patterns, checklists, and templates.

What ships with it: 5 files

37.9 KB alongside SKILL.md, 1 of them executable

assets/

references/

resources/

Gives 0 of the 12 instructions most api design skills give in 244 tokens

Counted across 224 of the 224 authors here whose files we hold, read 2026-09-06

  • Use plural nouns for resource namesin 50 of 224, across 49 files
  • Implement pagination for all list endpointsin 42 of 224, across 32 files
  • Use cursor-based pagination for large datasetsin 42 of 224, across 40 files
  • Return appropriate HTTP status codes for all responsesin 31 of 224, across 21 files
  • Use URL path versioning for API changesin 29 of 224, across 19 files
  • Use HTTP methods semantically for CRUD operationsin 22 of 224, across 13 files
  • Use HTTP methods for resource actionsin 20 of 224, across 18 files
  • Use plural nouns in kebab-case for resource URLsin 18 of 224, across 9 files
  • Enforce authentication and authorization on all resourcesin 17 of 224, across 7 files
  • Use standard HTTP status codesin 17 of 224
  • Validate all incoming request data against a schemain 16 of 224, across 7 files
  • Limit URL nesting to two levelsin 16 of 224

Said here and by no other author read

  • Model resources or types

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.