← Back to Skills Marketplace
veeramanikandanr48

Api Designer

by Veera · GitHub ↗ · v0.1.0
cross-platform ✓ Security Clean
3627
Downloads
1
Stars
22
Active Installs
1
Versions
Install in OpenClaw
/install api-designer
Description
Use when designing REST or GraphQL APIs, creating OpenAPI specifications, or planning API architecture. Invoke for resource modeling, versioning strategies, pagination patterns, error handling standards.
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 appears coherent and low-risk: it only contains design guidance and templates and requests no credentials or installs. Before relying on generated specs in production, review them for correctness, security (auth/rate-limiting), and any organization-specific conventions. Because the package source/homepage is unknown, avoid pasting real secrets or production credentials into prompts and validate outputs against your internal security and API governance standards. If you need provenance, ask the publisher for a homepage, license, or authorship information before wider deployment.
Capability Analysis
Type: OpenClaw Skill Name: api-designer Version: 0.1.0 The skill bundle is a comprehensive knowledge base for an AI agent focused on API design. All files, including the SKILL.md and various reference markdown documents, contain only informational content, best practices, and examples related to REST/GraphQL API design, OpenAPI specifications, error handling, pagination, and versioning. There is no evidence of prompt injection attempts against the agent, data exfiltration, malicious execution, or any other harmful behavior. The example CLI commands in `references/openapi.md` are for user information and are not instructions for the agent to execute, nor are they inherently malicious.
Capability Assessment
Purpose & Capability
Name, description, SKILL.md, and the included reference docs (OpenAPI, pagination, versioning, error handling, REST patterns) are coherent and directly relevant to designing REST/GraphQL APIs and producing OpenAPI specs.
Instruction Scope
Runtime instructions are limited to API-design activities (resource modeling, spec generation, versioning, pagination, error handling). They do not instruct reading system files, environment variables, or contacting external endpoints beyond normal documentation examples.
Install Mechanism
No install spec and no code files that would be written to disk; lowest-risk instruction-only skill.
Credentials
The skill does not declare or require any environment variables, credentials, or config paths; requested capabilities are proportionate to an API design assistant.
Persistence & Privilege
always:false and no special privileges or hints of modifying other skills or system settings. Autonomous invocation is allowed (platform default) but is not combined with other risky privileges.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install api-designer
  3. After installation, invoke the skill by name or use /api-designer
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
Initial release of api-designer skill: - Provides expert guidance for designing REST and GraphQL APIs, including OpenAPI 3.1 specifications. - Covers resource modeling, endpoint design, error handling, versioning, pagination, and authentication. - Includes detailed reference guides and mandatory design constraints. - Outputs comprehensive API specifications, documentation templates, and best practices.
Metadata
Slug api-designer
Version 0.1.0
License
All-time Installs 23
Active Installs 22
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, pagination patterns, error handling standards. It is an AI Agent Skill for Claude Code / OpenClaw, with 3627 downloads so far.

How do I install Api Designer?

Run "/install 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 (open-source). 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 Veera (@veeramanikandanr48); the current version is v0.1.0.

💬 Comments