What problem does it solve? Published API references often drift from the engineering API spec, omit error responses, or leave developers unable to make a first authenticated call. This Skill acts as an independent acceptance gate that judges whether an integrating developer can actually integrate from the reference, catching drift, fabricated endpoints, and happy-path-only documentation before the docs ship. ## Core Features & Use Cases - 11-condition review bar: Judges first-call reachability, full operation/event coverage, first-class errors (RFC 9457), rate limits, pagination, versioning/deprecation, runnable samples, and grounding. - Contract-consistency spot-check: Traces every documented endpoint, field, error, and event against the handed-in api-spec, flagging drift or fabricated endpoints as the highest-impact defect. - Machine-parseable verdict: Emits exactly VERDICT: approve or VERDICT: revise plus actionable findings naming the failed condition, location, and fix. - Delta-scoped amendment reviews: On a change request, reviews only the changed blocks re-synced to the updated contract rather than re-reviewing the whole catalog. - Use Case: After authoring a REST API reference from an OpenAPI spec, run this gate before publishing; it returns a revise verdict if a documented endpoint is not declared in the spec or if list endpoints lack pagination conventions. ## Quick Start Use reviewing-api-reference to judge docs/api-reference.md against the handed-in api-spec and give me the verdict with actionable findings.
