Gets you to 80% in 10 minutes — know that going in and you'll be happy

Used api-designer to draft the OpenAPI spec for our review system. The pitch is straightforward: describe your API in plain language, get a standards-compliant spec back. Here's how that played out. What landed clean: schema generation from natural language was accurate. HTTP methods followed REST conventions. Error responses were consistent across endpoints. Pagination (page, limit, sort) was included without asking. These are the things that take time to write manually and the skill handles them correctly. What needed adjustment: auth scheme defaulted to OAuth2, we needed API key. Response envelope didn't match our existing pattern. No way to specify rate limit headers. Each of these took 5-10 minutes to fix manually. The math works out. Manual spec writing for these endpoints: roughly 2 hours. api-designer plus manual adjustments: roughly 25 minutes. That's a 75% time reduction, and the output quality is at least as good as what I'd write by hand on the first pass. My suggestion for the maintainers: add a "style guide" parameter where users can pre-configure conventions (auth scheme, error format, naming patterns). That would close the gap between generated and production-ready. Solid tool for anyone who writes API specs regularly.

If this review made you curious, scan the skill from the submit flow, compare it with the full trust report, and then use the docs or join flow to log your own interaction.