Skill UI

This tool automates the entire process of creating a complete, production-ready application structure solely from an OpenAPI (Swagger) specification. It analyzes the spec to design the application architecture, generating all necessary layers including controllers, service logic, data models (DTOs), and repositories, adhering to best practices, framework conventions, and separation of concerns. The output includes unit tests, configuration files, and setup instructions, providing a robust, ready-to-use codebase.

This skill automatically converts structured data specifications (such as CSV, JSON schemas, SQL DDL, or Protobuf definitions) into functional, production-ready code. It generates complete models, validation logic, full CRUD API endpoints, and unit tests in multiple languages (Python, TypeScript, Go, etc.), significantly reducing boilerplate coding time and ensuring type safety.

A comprehensive tool for generating OpenAPI/Swagger documentation for Go (Golang) APIs. Developers annotate Go code comments with tags (@Summary, @Param, @Router, etc.) to define API contracts. The tool generates the full specification and provides integration handlers for major Go frameworks (Gin, Echo, Fiber), making the Swagger UI the single source of truth for API consumers. Ideal for maintaining robust, documented backend services.

This tool generates comprehensive API documentation directly from source code. It supports various API types, including REST, GraphQL, and RPC, and extracts crucial details like endpoints, parameters, data models, and authentication methods. It outputs standard formats such as Markdown, OpenAPI 3.0 YAML, and API Blueprint, streamlining the process of creating accurate and complete interface specifications for development teams.

Turn any OpenAPI or Swagger spec into an MCP server using the mcp-use TypeScript SDK. Maps REST operations to LLM-callable tools with zod schemas, auth wiring, live testing, and one-command deploy.

This skill converts standard API specifications, including OpenAPI 3.x and Swagger 2.0 (in YAML or JSON format), into fully functional, import-ready Postman Collection v2.1 JSON files. It automatically maps paths, parameters, request bodies, authentication schemes, and generates corresponding environment variables, allowing users to immediately test defined APIs.

Automatically generates comprehensive API documentation from existing TypeScript or JavaScript source code. It scans public exports, parses detailed JSDoc annotations (including parameters, returns, and throws), and can generate standardized OpenAPI 3.0 specifications for HTTP endpoints, ensuring robust and up-to-date API references.

Coordinate frontend/backend or service-to-service work through one authoritative machine-checkable contract (OpenAPI, AsyncAPI, Protobuf, or JSON Schema), with generated consumer types and contract-verified integration to prevent field drift and mock/production shape mismatch.

A specialized skill for detecting discrepancies (drift) between declared API contracts (such as GraphQL schemas, OpenAPI specs, and RPC manifests) and the actual behavior of live backend handlers. It is used to identify hidden operations, contract mismatches, or vulnerabilities resulting from schema evolution, versioning skew, or implementation gaps. Must be used after initial sandbox assumptions are established.

A comprehensive workflow designed for creating, maintaining, and deploying high-quality API documentation. This process guides users through several phases, including API discovery, generating OpenAPI specifications (Swagger), writing detailed developer guides, adding functional code examples, setting up interactive testing interfaces, and structuring the final documentation site.

Master API documentation with OpenAPI 3.1, AI-powered tools, and modern developer experience practices. Create interactive docs, generate SDKs, and build comprehensive developer portals.

Manage a centralized API inventory on Azure with the .NET SDK: create API Center services, workspaces, APIs, versions, definitions, and environments, import OpenAPI specs, and govern the API lifecycle.