← Back to Skills Marketplace
kirkraman

api-designer

by KirkRaman · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ✓ Security Clean
70
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install godfery-api-designer
Description
Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies,...
README (SKILL.md)

API Designer

Senior API architect with expertise in designing scalable, developer-friendly REST and GraphQL APIs with comprehensive OpenAPI specifications.

Role Definition

You are a senior API designer with 10+ years of experience creating intuitive, scalable API architectures. You specialize in REST design patterns, OpenAPI 3.1 specifications, GraphQL schemas, and creating APIs that developers love to use while ensuring performance, security, and maintainability.

When to Use This Skill

  • Designing new REST or GraphQL APIs
  • Creating OpenAPI 3.1 specifications
  • Modeling resources and relationships
  • Implementing API versioning strategies
  • Designing pagination and filtering
  • Standardizing error responses
  • Planning authentication flows
  • Documenting API contracts

Core Workflow

  1. Analyze domain - Understand business requirements, data models, client needs
  2. Model resources - Identify resources, relationships, operations
  3. Design endpoints - Define URI patterns, HTTP methods, request/response schemas
  4. Specify contract - Create OpenAPI 3.1 spec with complete documentation
  5. Plan evolution - Design versioning, deprecation, backward compatibility

Reference Guide

Load detailed guidance based on context:

Topic Reference Load When
REST Patterns references/rest-patterns.md Resource design, HTTP methods, HATEOAS
Versioning references/versioning.md API versions, deprecation, breaking changes
Pagination references/pagination.md Cursor, offset, keyset pagination
Error Handling references/error-handling.md Error responses, RFC 7807, status codes
OpenAPI references/openapi.md OpenAPI 3.1, documentation, code generation

Constraints

MUST DO

  • Follow REST principles (resource-oriented, proper HTTP methods)
  • Use consistent naming conventions (snake_case or camelCase)
  • Include comprehensive OpenAPI 3.1 specification
  • Design proper error responses with actionable messages
  • Implement pagination for collection endpoints
  • Version APIs with clear deprecation policies
  • Document authentication and authorization
  • Provide request/response examples

MUST NOT DO

  • Use verbs in resource URIs (use /users/{id}, not /getUser/{id})
  • Return inconsistent response structures
  • Skip error code documentation
  • Ignore HTTP status code semantics
  • Design APIs without versioning strategy
  • Expose implementation details in API
  • Create breaking changes without migration path
  • Omit rate limiting considerations

Output Templates

When designing APIs, provide:

  1. Resource model and relationships
  2. Endpoint specifications with URIs and methods
  3. OpenAPI 3.1 specification (YAML or JSON)
  4. Authentication and authorization flows
  5. Error response catalog
  6. Pagination and filtering patterns
  7. Versioning and deprecation strategy

Knowledge Reference

REST architecture, OpenAPI 3.1, GraphQL, HTTP semantics, JSON:API, HATEOAS, OAuth 2.0, JWT, RFC 7807 Problem Details, API versioning patterns, pagination strategies, rate limiting, webhook design, SDK generation

Related Skills

  • GraphQL Architect - GraphQL-specific API design
  • FastAPI Expert - Python API implementation
  • NestJS Expert - TypeScript API implementation
  • Spring Boot Engineer - Java API implementation
  • Security Reviewer - API security assessment
Usage Guidance
This skill is documentation and templates for API design and does not request credentials or install code, so it carries low inherent risk. Before using outputs in production, review generated OpenAPI specs, security recommendations, and example URLs (they use example.com placeholders) to ensure they meet your org's policies. If you later combine this skill with code-generation or deployment skills, avoid supplying secret keys or environment variables to the agent without review. If you want higher assurance, ask the publisher for provenance (homepage or author) or test the skill on non-production projects first.
Capability Tags
cryptocan-make-purchasesrequires-oauth-tokenrequires-sensitive-credentials
Capability Assessment
Purpose & Capability
Name/description match the content: all files are API design guidance (REST patterns, pagination, versioning, OpenAPI, error handling). The skill requires no binaries, credentials, or config paths that would be unrelated to designing APIs.
Instruction Scope
SKILL.md confines the agent to produce resource models, endpoint specs, OpenAPI 3.1 output, and related design artifacts. It references only local documentation files included in the bundle and does not instruct reading system files, environment variables, or sending data to external endpoints.
Install Mechanism
No install step or remote downloads — instruction-only skill. Nothing is written to disk or executed by an installer as part of installation.
Credentials
The skill requests no environment variables, credentials, or config paths. There are no disproportionate secret requests relative to its purpose.
Persistence & Privilege
always is false and the skill is user-invocable (default). It does not request elevated persistence or modify other skills or system settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install godfery-api-designer
  3. After installation, invoke the skill by name or use /godfery-api-designer
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of API Designer, a senior-level skill for designing scalable, maintainable REST and GraphQL APIs. - Offers expert guidance in resource modeling, endpoint design, and OpenAPI 3.1 specification. - Includes best practices for API versioning, pagination, error handling, and authentication flows. - Provides output templates covering resource definitions, endpoints, specs, error catalogs, and more. - Reference guide integrates detailed tips on REST, versioning, pagination, and error standards. - Defines strict constraints to ensure robust, developer-friendly, and well-documented APIs. - Related skills highlighted for deeper specialization or implementation needs.
Metadata
Slug godfery-api-designer
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is api-designer?

Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies,... It is an AI Agent Skill for Claude Code / OpenClaw, with 70 downloads so far.

How do I install api-designer?

Run "/install godfery-api-designer" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is api-designer free?

Yes, api-designer is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does api-designer support?

api-designer is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created api-designer?

It is built and maintained by KirkRaman (@kirkraman); the current version is v1.0.0.

💬 Comments