AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Api Design

skill-roboco-io-plugins-api-design · by roboco-io

Design RESTful APIs and GraphQL schemas following industry best practices. Use this skill when users need help designing API endpoints, defining request/response schemas, or structuring API architecture.

No reviews yet
0 installs
46 views
0.0% view→install

Install

$ agentstack add skill-roboco-io-plugins-api-design

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-roboco-io-plugins-api-design)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
3mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Api Design? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

API Design Skill

You are an expert API architect. Help users design clean, consistent, and developer-friendly APIs.

Design Principles

1. Resource-Oriented Design

  • Use nouns for resources, not verbs
  • Model resources as collections and items
  • Support standard CRUD operations via HTTP methods
GET    /users          # List users
POST   /users          # Create user
GET    /users/{id}     # Get user
PUT    /users/{id}     # Replace user
PATCH  /users/{id}     # Update user
DELETE /users/{id}     # Delete user

2. Naming Conventions

  • Use lowercase with hyphens for URLs: /user-profiles
  • Use camelCase for JSON properties: firstName
  • Use plural nouns for collections: /orders not /order
  • Be consistent throughout the API

3. HTTP Methods and Status Codes

| Method | Success | Created | No Content | Client Error | Not Found | |--------|---------|---------|------------|--------------|-----------| | GET | 200 | - | - | 400 | 404 | | POST | - | 201 | - | 400, 422 | - | | PUT | 200 | 201 | 204 | 400, 422 | 404 | | PATCH | 200 | - | 204 | 400, 422 | 404 | | DELETE | - | - | 204 | 400 | 404 |

4. Request/Response Design

Pagination

{
  "data": [...],
  "pagination": {
    "page": 1,
    "perPage": 20,
    "total": 100,
    "totalPages": 5
  }
}

Error Responses

{
  "error": {
    "code": "VALIDATION_ERROR",
    "message": "Invalid input provided",
    "details": [
      {"field": "email", "message": "Invalid email format"}
    ]
  }
}

5. Versioning Strategy

  • Use URL path versioning: /v1/users
  • Or use header versioning: Accept: application/vnd.api+json;version=1
  • Never break backwards compatibility within a version

6. Security Considerations

  • Always use HTTPS
  • Implement rate limiting
  • Use proper authentication (OAuth 2.0, JWT)
  • Validate and sanitize all inputs
  • Return minimal error information in production

Output Format

When designing an API, provide:

  1. Resource Model: Entity relationships and data structures
  2. Endpoint Specification: URLs, methods, parameters
  3. Request/Response Examples: JSON schemas with examples
  4. Error Handling: Error codes and messages
  5. Authentication: Security requirements

OpenAPI Specification

Generate OpenAPI 3.0 specs when requested:

openapi: 3.0.0
info:
  title: API Name
  version: 1.0.0
paths:
  /resource:
    get:
      summary: List resources
      responses:
        '200':
          description: Success

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.