api-spec

Use when the user wants to design, review, or document an API (REST, OpenAPI, versioning, error models, contract testing, authentication), or when…

Skill by Leostruka

IndexedMIT

Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/leostruka-api-spec

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

About

Use when the user wants to design, review, or document an API (REST, OpenAPI, versioning, error models, contract testing, authentication), or when generating/maintaining OpenAPI specs as machine-readable context for AI agents.

Use cases: documents, design, backend, testing

Reviews

Write a review

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools: No tools found
Secrets: None asked for
Install scripts: None found

Network hosts it talks to 1

codeload.github.com · found in install command

Files it touches

~/.claude/skills/api-spec

What's inside

Skill name: api-spec
Description: Use when the user wants to design, review, or document an API (REST, OpenAPI, versioning, error models, contract testing, authentication), or when generating/maintaining OpenAPI specs as machine-readable context for AI agents.
License: MIT
Instructions: 47 lines in SKILL.md · view on GitHub

Files (1)

SKILL.md

SKILL.md (first lines)

# API Spec

Design and review HTTP/gRPC/GraphQL APIs, and keep the contract explicit,
versioned, and machine-readable (OpenAPI). The spec is the primary context
for agents — they work from the spec, not from implementation memory.

## Design protocol

1. **Collect constraints** — consumers, auth, rate limits, error handling,
   versioning.
2. **Choose style** — REST, gRPC, GraphQL, or hybrid per use case.
3. **Design endpoints** — nouns as resources, consistent paths, status
   codes, error model.
4. **Specify input/output/behavior** — every endpoint declares input schema,
   output schema, observable behavior. A spec lacking I/O is incomplete.
5. **Write the contract** — OpenAPI spec (or proto), validated with tools.
6. **Add tests** — contract, serialization, happy/unhappy paths.
7. **Document + sync** — spec stays in version control, in sync with code.

## What a spec must include

1. **Endpoints** — paths, methods, parameters, request/response schemas.
2. **Authentication** — type, headers, token format.
3. **Error responses** — status codes, error schemas, retry semantics.
4. **Versioning** — version, deprecation policy, migration path.
5. **Rate limits** — rps, burst, backoff strategy.

## Process

```
Design/review API → generate/update OpenAPI → validate against impl →
use spec as agent context → keep in VCS
```

## Anti-patterns

- No spec, or an outdated one.
- Spec in prose instead of OpenAPI.
- Spec not versioned / not in version control.
- Agents reading implementation code instead of the spec.

## Output rule

Deliver a spec file, examples, and a test command. Validate with
`swagger-codegen` or equivalent when available.

From Leostruka/devin-bundle, MIT.

Signals

Stars: 0
Forks: 0
Open issues: 1
Last commit (this folder): Sep 19, 2026 (1 month ago)
Last release: Oct 24, 2026 (4 days ago)

From GitHub (fetched Oct 24, 2026).

Details

License: MIT
Repository: github.com/Leostruka/devin-bundle
First seen: Oct 24, 2026
Last checked: Oct 24, 2026
Source: GitHub github-graphql

More from Leostruka

Cite this page

api-spec skill. Agent Mart. https://agentmart.dev/skills/leostruka-api-spec (last updated 2026-10-24)