Results for “swagger”

Generates OpenAPI 3.0/3.1 specs, TypeScript client types, and curl examples from existing route handler code. Supports Express, Next.js API routes, Fastify, and Hono. Produces complete documentation including auth requirements, rate limits, error codes, and request/response examples. Activate on: 'generate API docs', 'OpenAPI from code', 'document endpoints', 'API reference', 'swagger generation', 'endpoint documentation'. NOT for: API design from scratch (use api-architect), deployment (use devops-automator), testing (use test-automation-expert).

The English summary is being prepared. Showing the original description.

Kubb (OpenAPI / Swagger コードジェネレーター) リファレンス。 kubb.config.ts、TypeScript 型・TanStack Query フック・Zod・Faker・MSW モック生成プラグイン、 Fetch / Axios / SWR / React Query クライアント、plugin-client (自前クライアント)。 CLI 8 コマンド、拡張レジストリ (kubb add)、Kubb Studio、Kit (kubb/kit)、 parser-ts / parser-md、adapter-oas、diagnostics、プラグインベース、モノレポ対応。 TanStack Query 本体の API は tanstack-query スキル。

The English summary is being prepared. Showing the original description.

Provides patterns to generate comprehensive REST API documentation using SpringDoc OpenAPI 3.0 and Swagger UI in Spring Boot 3.x applications. Use when setting up API documentation, configuring Swagger UI, adding OpenAPI annotations, implementing security documentation, or enhancing REST endpoints with examples and schemas.

The English summary is being prepared. Showing the original description.

Generates OpenAPI 3.0/3.1 specs, TypeScript client types, and curl examples from existing route handler code. Supports Express, Next.js API routes, Fastify, and Hono. Produces complete documentation including auth requirements, rate limits, error codes, and request/response examples. Activate on: 'generate API docs', 'OpenAPI from code', 'document endpoints', 'API reference', 'swagger generation', 'endpoint documentation'. NOT for: API design from scratch (use api-architect), deployment (use devops-automator), testing (use test-automation-expert).

The English summary is being prepared. Showing the original description.

Generates OpenAPI 3.0/3.1 specifications from Express, Next.js, Fastify, Hono, or NestJS routes. Creates complete specs with schemas, examples, and documentation that can be imported into Postman, Insomnia, or used with Swagger UI. Use when users request "generate openapi", "create swagger spec", "openapi documentation", or "api specification".

The English summary is being prepared. Showing the original description.

Generates API documentation using OpenAPI/Swagger specifications with interactive documentation, code examples, and SDK generation. Use when users request "API documentation", "OpenAPI spec", "Swagger docs", "document API endpoints", or "generate API reference".

The English summary is being prepared. Showing the original description.

Hunt shadow / zombie / undocumented API surface (OWASP API9 Improper Inventory Management) — enumerate the full API version history (v1/v2/beta/legacy paths, header- and subdomain-based versioning), pull and diff every reachable OpenAPI/Swagger spec (including ones only findable via the Wayback Machine), and behaviorally diff old vs. current versions for auth/rate-limit/validation regressions rather than just response-shape differences. Distinct from hunt-api-misconfig, which owns exploitation once you have a spec or endpoint (mass assignment, JWT, OData, Swagger-chain attacks); distinct from hunt-subdomain, which owns host-level discovery. This skill owns the version-inventory and behavioral-diff workflow itself. Use when the target has versioned API paths, multiple specs, a changelog referencing deprecated endpoints, or a mobile app whose hardcoded backend calls look older than the current web app's.

The English summary is being prepared. Showing the original description.

Create and maintain API documentation in OpenAPI 3.0, a standard format for describing APIs. Document endpoints, request and response data, authentication, and errors with clear examples and reusable definitions.

• Create a specification for a user API
• Document request, response, and error examples
• Update documentation after API changes

Create API specifications, interactive documentation, and developer portals that explain how to use an API. The skill also covers authentication examples, SDK generation, example testing, and migration guides to help developers integrate and maintain their applications.

• Create API specifications with authentication examples
• Build interactive API documentation
• Generate SDKs from OpenAPI specifications

Turn API code into documentation covering available operations, inputs, outputs, authentication, and errors. Add practical request examples and usage guides, with OpenAPI specifications or Postman collections where possible to help developers explore and use the API.

• Document a new API from its code
• Update documentation after API changes
• Prepare API guides for new developers or external users

Generate an MCP server, a service exposing tools to AI agents, and a Power Platform custom connector for Copilot Studio. Outputs include connector definitions, authentication settings, request handling, individual tools, and deployment configuration.

• Connect a Copilot Studio agent to an external API
• Create tools for customer search and analysis
• Generate connector files and authentication settings

Choose how an API, the interface software uses to exchange data, should work. Covers REST, GraphQL, and tRPC selection, consistent responses, pagination, versioning, authentication, request limits, documentation, and security review considerations.

• Choosing between REST, GraphQL, and tRPC
• Standardizing API responses, errors, and pagination
• Planning authentication, request limits, and versioning

Test and debug REST and GraphQL APIs using curl, httpie, Postman collections, or scripted tests. Check authentication, invalid inputs, pagination, and response details to identify failures that a successful status code alone may miss.

• Checking authentication and access permissions
• Testing invalid inputs and boundary conditions
• Debugging failed HTTP requests

Build Python APIs with FastAPI and Pydantic V2, including input validation, database operations that avoid blocking other work, and token-based authentication. Implement REST or WebSocket endpoints, then check their behavior with automated tests and generated API documentation.

• Build REST APIs with FastAPI
• Validate input data with Pydantic V2
• Implement JWT authentication and authorization

Build .NET 8 APIs and backend services using C# 12, with clear separation of application responsibilities. The skill covers database access, authentication, API documentation, compilation checks, and integration tests that verify components working together.

• Building endpoints with minimal APIs
• Adding database access with Entity Framework Core
• Separating application responsibilities with MediatR

Guides creation and modification of ASP.NET Core Web API endpoints with correct HTTP semantics, OpenAPI metadata, and error handling. USE FOR: adding new API endpoints (controllers or minimal APIs), wiring up OpenAPI/Swagger, creating .http test files, setting up global error handling middleware. DO NOT USE FOR: general C# coding style, EF Core data access or query optimization (use optimizing-ef-core-queries), frontend/Blazor work, gRPC services, or SignalR hubs.

The English summary is being prepared. Showing the original description.

Operational arsenal for authorized external red-team and bug-bounty recon. Concrete probes, wordlists, regexes, dorks, curl one-liners for: subdomain enum, GraphQL/Swagger/REST discovery, identity fabric (Entra/Okta/ADFS/Google/SAML/M365 deep — Teams/SharePoint/OneDrive), cloud bucket enum (S3/GCS/Azure), CDN/WAF bypass, origin discovery, vendor fingerprinting (Citrix/F5/Pulse/Fortinet/PaloAlto/Cisco/VMware), CI/CD exposure, 48-pattern secret-scan catalog (AWS/GCP/GitHub/Stripe/Slack/Anthropic/OpenAI/Atlassian/DataDog/npm/PyPI), Postman workspaces, breach correlation (HudsonRock/HIBP/DeHashed/IntelX), TLS/JA3 audit, certificate transparency, JS endpoint extraction, package registry leaks, mobile/APK recon, sat imagery, sector-specific recon (healthcare DICOM, finance SWIFT, ICS/SCADA Modbus/BACnet). Detail content in 15 modular reference files, loaded on demand. Use for any authorized recon: scoping, asset discovery, attack-path mapping, secret triage, severity scoring.

The English summary is being prepared. Showing the original description.

Hunt source code and build artifact leakage — JavaScript source maps (.js.map) reconstructing TypeScript/ES6 source, Swagger/OpenAPI JSON endpoint discovery, .env/.git exposure, webpack chunks with hardcoded secrets, robots.txt/security.txt recon, build-info files, asset-manifest.json API route discovery, .DS_Store file listing. Use at the START of every recon session — these findings often unlock the entire attack surface.

The English summary is being prepared. Showing the original description.

Use when adding docstrings, creating API documentation, or building documentation sites. Invoke for OpenAPI/Swagger specs, JSDoc, doc portals, tutorials, user guides.

The English summary is being prepared. Showing the original description.

Use this skill to run a four-panel adversarial advisory review on any pull request that touches the OpenAPM specification artifact (docs/src/content/docs/specs/openapm-*.md), its inline / sidecar JSON Schemas (docs/src/content/docs/specs/schemas/*.schema.json), or the conformance fixture seed (tests/fixtures/spec-conformance/**). The panel fans out to four spec-ecosystem reviewers (swagger-openapi-editor, oci-distribution-editor, pkgmgr-registry-contract-editor, w3c-tag-architect), each running in its own agent thread, and a spec-editor synthesizer that produces a fold-now / defer-v0.1.1 / defer-v0.2 / reject list plus a ship decision keyed off a 1..10 shocked_meter scale. The orchestrator is the sole writer to the PR: ONE consolidated comment, no verdict labels, no merge gating. The panel is advisory -- it surfaces findings, prioritizes folds, and renders a ship recommendation that the maintainer weighs.

The English summary is being prepared. Showing the original description.

Generate API documentation from code. Use when the user wants to document APIs, create API reference, generate endpoint documentation, or needs help with OpenAPI/Swagger specs.

The English summary is being prepared. Showing the original description.

Generate API endpoint code and documentation from specifications. Use when the user wants to create new API endpoints, generate route handlers, scaffold REST APIs, or produce OpenAPI/Swagger specs from code.

The English summary is being prepared. Showing the original description.

Generates and validates technical documentation including docstrings, OpenAPI/Swagger specs, JSDoc annotations, doc portals, and user guides.

The English summary is being prepared. Showing the original description.

Auto-generate API documentation from code and comments. Use when API endpoints change, or user mentions API docs. Creates OpenAPI/Swagger specs from code. Triggers on API file changes, documentation requests, endpoint additions.

The English summary is being prepared. Showing the original description.