openapi-open-responses

Updates the open_responses Dart package from OpenResponses OpenAPI specification changes.

Updated May 23, 2026

Search Tags:#code scaffolding #openapi #verification #dart #llm api #api client #spec sync

Ready to run

npx skills add https://github.com/kiranimmadi2/promptforge-ai --skill openapi-open-responses-kiranimmadi2

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: openapi-open-responses
Source: https://github.com/kiranimmadi2/promptforge-ai/tree/main/ai_clients_dart/packages/open_responses/.agents/skills/openapi-open-responses
Command: npx skills add https://github.com/kiranimmadi2/promptforge-ai --skill openapi-open-responses-kiranimmadi2

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Keeping a Dart SDK in sync with an evolving OpenAPI specification requires manual diffing, model scaffolding, and verification. This Skill automates the fetch-review-scaffold-verify cycle for the open_responses package against the OpenResponses unified LLM API spec. ## Core Features & Use Cases - Spec Fetch & Review: Downloads the latest OpenResponses OpenAPI spec and reviews changes against the current implementation using the shared api-toolkit CLI. - Scaffolding & Verification: Scaffolds new Dart models from spec schemas and runs verification checks across coverage, exports, and serialization. - Use Case: When the OpenResponses spec adds a new streaming event type, run the workflow to fetch the spec, review the diff, scaffold the new sealed variant in lib/src/models/streaming, and verify compliance before release. ## Quick Start Ask the assistant to fetch the latest OpenResponses OpenAPI spec and review what changed in the open_responses package.

Frequently Asked Questions about openapi-open-responses

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

FAQPage Schema

How do I update a Dart SDK from an OpenAPI spec change?▼

Run the api-toolkit fetch command with the skill's config directory to download the latest spec, then run review to inspect changes. Scaffold new models, promote the reviewed spec into packages/open_responses/specs, and finish with the verify command.

How do I verify OpenAPI spec coverage in the open_responses package?▼

Run api_toolkit.py verify with --checks all --scope all and the skill's config directory. It validates model coverage, exports, and serialization against the manifest, then run dart analyze, dart format, and unit tests separately.

Does this workflow require API authentication?▼

No authentication is required. The OpenResponses spec is fetched from a public URL, and the specs.json config sets requires_auth to false with no auth environment variables.

Why are some spec-required fields nullable in the Dart models?▼

Certain fields are intentionally nullable for provider compatibility, since many providers return partial responses. These deviations are documented in the manifest with acknowledged tags and explanatory notes.

What are the limitations of the scaffolding workflow?▼

Scaffolding relies on the manifest's placement patterns and type mappings, so unusual schema shapes may need manual adjustment. Sealed hierarchies and discriminator mappings must be reviewed against the package references before verification.