agentskills.codes
OP

openapi-spec-generation

by Anhvu1107Source

ALWAYS use this when the request matches Openapi Spec Generation: Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns.

Install

mkdir -p .claude/skills/openapi-spec-generation-anhvu1107 && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14167" && unzip -o skill.zip -d .claude/skills/openapi-spec-generation-anhvu1107 && rm skill.zip

Installs to .claude/skills/openapi-spec-generation-anhvu1107

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

ALWAYS use this when the request matches Openapi Spec Generation: Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns.
170 chars✓ has a “when” trigger

About this skill

OpenAPI Spec Generation

Selective Reading Rule

Start with:

  • references/senior-master-standard.md
  • references/usage-routing.md
  • references/quality-checklist.md

Then load only the inherited docs, scripts, assets, or examples that match the user's actual task.

Comprehensive patterns for creating, maintaining, and validating OpenAPI 3.1 specifications for RESTful APIs.

Use this skill when

  • Creating API documentation from scratch
  • Generating OpenAPI specs from existing code
  • Designing API contracts (design-first approach)
  • Validating API implementations against specs
  • Generating client SDKs from specs
  • Setting up API documentation portals

Do not use this skill when

  • The task is unrelated to openapi spec generation
  • You need a different domain or tool outside this scope

Instructions

  • Clarify goals, constraints, and required inputs.
  • Apply relevant best practices and validate outcomes.
  • Provide actionable steps and verification.
  • If detailed examples are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed patterns and examples.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

More by Anhvu1107

View all by Anhvu1107 →

jq

Anhvu1107

ALWAYS use this when the request matches JQ: Expert jq usage for JSON querying, filtering, transformation, and pipeline integration.

00

pdf

Anhvu1107

ALWAYS use this when the task involves reading, extracting, splitting, merging, rotating, creating, validating, OCR-ing, form-filling, or otherwise producing or modifying PDF files.

00

007

Anhvu1107

ALWAYS use this when the request matches 007: Security audit, hardening, threat modeling (STRIDE/PASTA), Red/Blue Team, OWASP checks, code review, incident response, and infrastructure security for any project.

00

lex

Anhvu1107

ALWAYS use this when the request matches LEX: Centralized ''Truth Engine'' for cross-jurisdictional legal context (US, EU, CA) and contract scaffolding.

00

seo

Anhvu1107

ALWAYS use this when the request matches SEO: Run a broad SEO audit across technical SEO, on-page SEO, schema, sitemaps, content quality, AI search readiness, and GEO.

00

docx

Anhvu1107

ALWAYS use this when the user needs a Word document created, edited, inspected, validated, templated, or transformed, including tracked changes, comments, formatting-preserving updates, XML-level edits, or polished .docx deliverables.

00

Search skills

Search the agent skills registry