apitestspec-composer

Convert API documentation into executable YAML/JSON specs.

5|1|Updated Feb 27, 2026
One-click install
npx skills add https://github.com/winhok/testkit --skill apitestspec-composer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: apitestspec-composer
Source: https://github.com/winhok/testkit/tree/main/skills/apitestspec-composer
Command: npx skills add https://github.com/winhok/testkit --skill apitestspec-composer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, openpyxl, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill converts API documentation (OpenAPI/Swagger, Markdown interface docs, and interface tables) into executable native specs (YAML/JSON), reducing manual translation and maintaining a single source of truth for testing pipelines.

Core Features & Use Cases

  • Converts OpenAPI/Markdown/interface docs into native YAML/JSON specs
  • Exports to Excel/CSV when needed for stakeholders and test planning
  • Hand-offs to additional skills for flow configuration and test execution

Quick Start

Provide your API documentation and the skill will emit a native YAML/JSON spec and, if requested, export to Excel or CSV.

Frequently Asked Questions about apitestspec-composer

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

FAQPage Schema
How do I convert OpenAPI documentation into executable YAML specs for automated testing?

Converting OpenAPI to YAML specs involves parsing the documentation, enforcing structured validation rules, and preserving concrete example values. The skill processes OpenAPI formats to generate native YAML or JSON specs for automated testing.

What is the best way to generate JSON test specs from Markdown API descriptions?

The best way to generate JSON specs from Markdown is using a skill that parses API descriptions and extracts structured data. It outputs native JSON specs while maintaining a single source of truth for testing pipelines.

Can I export API test specifications to Excel or CSV for stakeholder review?

Yes, you can export API test specifications to Excel or CSV. The skill generates native specs and provides optional exports to Excel or CSV formats for stakeholders and test planning.

Does this API spec generation approach work with tabular interface briefs?

Yes, this API spec generation approach works with tabular interface briefs. It processes tabular briefs alongside OpenAPI and Markdown to generate a primary native spec with structured validation.

How do I hand off native specs to downstream test execution tools?

To hand off native specs to downstream test execution, the skill outputs structured YAML or JSON data ready for automated testing pipelines. It clearly communicates with downstream tools such as flow-configurator or scenario-runner.

Why does my API spec conversion need to preserve concrete example values?

Preserving concrete example values in API spec conversion ensures automated tests run against realistic data. The skill enforces structured validation rules while maintaining these examples for downstream testing pipelines.