Skip to content
Back to skills

Api Design

ASecurity

Guide API design decisions for clear, stable, and ergonomic interfaces.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 6, 2026
ai-agentsgoapi

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 6, 2026

npx -y skills add dileepkpandiya/skilleval --skill api-design --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Api Design?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Api Design
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dileepkpandiya-api-design/badge)](https://www.skillsdirectory.com/skills/dileepkpandiya-api-design)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: api-design
description: Guide API design decisions for clear, stable, and ergonomic interfaces.
version: 0.1.0
triggers:
  - design an api
  - review endpoint design
  - improve sdk interface
agents:
  - claude
---
# API Design Skill

Use this skill when designing HTTP APIs, SDK methods, command interfaces, or internal service contracts.
Optimize for predictable behavior, explicit errors, and long-term compatibility.

## Design checklist

Define the primary user journey before naming endpoints or methods.
Choose resource names that describe domain concepts rather than implementation details.
Use consistent pagination, filtering, sorting, and idempotency conventions across the API.
Treat versioning as a compatibility strategy, not as a substitute for careful change management.

## Request and response guidance

Prefer structured request bodies for operations with multiple parameters.
Return stable identifiers and timestamps in machine-readable formats.
Include error codes that clients can branch on, plus messages that humans can understand.
Make partial failure behavior explicit for batch operations.

## Evaluation guidance

Call out ambiguous ownership of resources, overloaded parameters, and hidden side effects.
Recommend defaults that reduce client surprise.
Explain tradeoffs when there are multiple acceptable designs.
When suggesting examples, keep payloads small but realistic enough to validate the contract.

Files in this skill

  • SKILL.md1.4 KB
  • tasks.yaml661 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…