agentsclimarketplace

Api design

Skill nevitonsantana/adaptive-skills/skills/api-design

38 portable Agent Skills for disciplined, reviewable AI-assisted work across Codex, Claude Code, GitHub Copilot, and compatible agents.

Install
npx -y skills add nevitonsantana/adaptive-skills --skill api-design

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.
  • 1 stars1 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.

What its author says it does

Copied from the file, not written here

Shape a contract so inputs, outputs, errors, names, and compatibility are clear and hard to misuse.

SKILL.md

1.8 KB, as published. Nobody here has run it

Overview

Use this skill to design or review interfaces between systems or modules with clarity and change-awareness.

When to Use

  • new endpoints or interfaces
  • payload redesign
  • public or semi-public contract changes

When NOT to Use

  • private local implementation details with no meaningful contract

Core Moves

  1. Name the contract responsibility.
  2. Define inputs and outputs.
  3. State failure semantics.
  4. Review naming for real-world use.
  5. Check compatibility cost for consumers.

Optional Modules

  • Error taxonomy — Expand failure classes when misuse or recovery matters.
  • Compatibility pass — Map what breaks for current consumers.
  • Ownership note — Clarify who owns the contract and its evolution.

Activation Triggers

  • Use the error taxonomy when clients need to react differently to failures.
  • Use the compatibility pass when consumers already exist.
  • Add ownership when many teams touch the contract.

Expected Output

  • contract statement
  • input/output model
  • error model
  • compatibility note

Verification

  • The contract responsibility is singular.
  • Consumers can understand success and failure clearly.
  • Backwards-compatibility assumptions are explicit.

Handoff Signals

  • The contract needs product or policy review.
  • The change requires coordinated rollout across teams.

Pairs Well With

  • communication
  • architecture-review
  • testing

Anti-patterns

  • Encoding ambiguity into flexible payloads.
  • Changing a contract without naming compatibility cost.
  • Optimizing for implementation convenience over consumer clarity.

Keep looking

Skills are one crate of 328,083. 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.