api-artifacts

Generate OpenAPI, Postman, AsyncAPI, and GraphQL artifacts from architecture manifests.

2|1|Updated Feb 7, 2026
One-click install
npx skills add https://github.com/navraj007in/architecture-cowork-plugin --skill api-artifacts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: api-artifacts
Source: https://github.com/navraj007in/architecture-cowork-plugin/tree/main/skills/api-artifacts
Command: npx skills add https://github.com/navraj007in/architecture-cowork-plugin --skill api-artifacts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the generation of comprehensive API artifacts (OpenAPI specs, Postman collections, AsyncAPI specifications, and GraphQL schemas) from architecture manifests, eliminating manual replication and drift across documentation and testing artifacts.

Core Features & Use Cases

  • OpenAPI 3.1 generation: Derives a per-service REST API spec from responsibilities and shared types.
  • Postman collection generation: Produces ready-to-use collections for API testing with environment variables and sample requests.
  • AsyncAPI generation: Creates event-driven interface specs for all message channels defined in the manifest.
  • GraphQL schema generation: Generates GraphQL schemas and input types from shared contracts and service definitions.
  • Template-driven output: Ensures consistent naming, versions, and examples across artifacts.

Use Case: When you have a multi-service architecture described in a manifest, generate all necessary API artifacts in one pass to accelerate integration and testing.

Quick Start

Use this skill to generate OpenAPI, Postman, AsyncAPI, and GraphQL artifacts from your manifest file (e.g., manifest.yaml). The artifacts will be output to an artifacts/ directory and include openapi.yaml, postman-collection.json, asyncapi.yaml, and graphql-schema.graphql.

Frequently Asked Questions about api-artifacts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate OpenAPI specs from an architecture manifest?

Generate OpenAPI specs from an architecture manifest by defining service responsibilities and shared types. The Skill derives a per-service REST API spec, ensuring consistent schemas, naming, and authentication alignment without manual replication.

Can I generate AsyncAPI and GraphQL schemas from the same manifest file?

Yes, you can generate AsyncAPI and GraphQL schemas from the same manifest file. The Skill processes event-driven interfaces and shared contracts to produce AsyncAPI specifications for message channels and GraphQL schemas for service definitions in one pass.

What is the best way to automate Postman collection creation for multiple services?

Automate Postman collection creation by deriving ready-to-use collections from your architecture manifest. The Skill generates collections with environment variables and sample requests, ensuring consistent naming and versions across API testing artifacts.

How do I prevent documentation drift across OpenAPI and AsyncAPI files?

Prevent documentation drift by generating OpenAPI and AsyncAPI files from a single architecture manifest. This template-driven approach derives artifacts from shared types and configuration rules, eliminating manual replication and ensuring consistent schemas.

Does this approach work for both REST services and event-driven interfaces?

Yes, this approach works for both REST services and event-driven interfaces. The Skill applies to architectures described in the manifest, generating OpenAPI for REST and AsyncAPI for event-driven message channels, ensuring consistent authentication alignment.

What format does my manifest need to be in to generate API artifacts?

Your manifest needs to define service responsibilities, shared types, and configuration rules. Using a format like manifest.yaml, the Skill outputs API artifacts including openapi.yaml, postman-collection.json, asyncapi.yaml, and graphql-schema.graphql to an artifacts directory.