Install any skill in seconds. Free to start, no credit card required.
Get Started Free →dokhacgiakhoa/openapi-spec-generation
Generate and maintain OpenAPI 3.1 specifications from code, design-first specs, and validation patterns.
Passed 19 of 22 test cases with the skill, and 17 of 22 without it.
2 fixed17 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
In OpenAPI 3.0, developers used `nullable: true` for optional payload attributes. We are upgrading our user profile schema to OpenAPI 3.1.0 where `nullable: true` is obsolete. How should a nullable string field be defined in the schema component?
| Checked | Without skill | With skill |
|---|---|---|
| The response uses a type array containing string and null for the schema definition. | Passed | Passed |
| The response explicitly notes that nullable is obsolete in OpenAPI 3.1. | Missed | Passed |
The instructions your model reads when the skill loads.
Comprehensive patterns for creating, maintaining, and validating OpenAPI 3.1 specifications for RESTful APIs.
resources/implementation-playbook.md.resources/implementation-playbook.md for detailed patterns and examples.test cases passed, vs 17 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.