Api Reference Quality

by samber594cf70d343eMIT3 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 10 days ago

Audit a published API reference at the endpoint level against its spec surface - every operation, parameter, response code, and error documented, request/response examples present, per-language code snippets in parity, try-it affordances working - and install the source-of-truth gates that stop reference drift (spec-driven generation, OpenAPI lint, contract tests, snippet parity in CI). Use whenever the user mentions API reference docs, OpenAPI docs completeness, undocumented endpoints or error codes, stale or drifting docs, or docs CI gates - even if they never say "reference quality". Endpoint-level reference only. Do NOT use for portal IA and onboarding - use samber/developer-platform-skills@developer-portal-design instead.

Only the file list is public. File contents are available once the skill is installed in a workspace.

PathSizeType
evals/evals.json28.9 KBapplication/json
references/audit-rubric.md8.3 KBtext/markdown
references/measured-evidence.md12.3 KBtext/markdown
references/tooling-catalog.md5.6 KBtext/markdown
SKILL.md17.3 KBtext/markdown

Source and attribution

Source:samber/developer-platform-skillsinskills/api-reference-qualityat commit594cf70

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal