Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →athola/api-review
Evaluates API surface design, consistency, and exemplar alignment.
Passed 12 of 16 test cases with the skill, and 3 of 16 without it.
and 13 more in the full report
12 fixed4 passed either way6 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
We drafted findings for `lib/auth.ts` in `.review/findings.json`. What specific command line invocation must be run to verify that every citation and verbatim anchor resolves against the repository root?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies running python plugins/imbue/scripts/citation_verifier.py --findings .review/findings.json --repo-root . | Missed | Passed |
| Requires dropping or labeling UNVERIFIED any finding where citation verification fails. | Missed | Passed |
The instructions your model reads when the skill loads.
pensive:code-refinement)pensive:architecture-review)Use this skill to review public API changes, design new surfaces, audit consistency, and validate documentation completeness. Run it before any API release to confirm alignment with project guidelines.
api-review:surface-inventoryapi-review:exemplar-researchapi-review:consistency-auditapi-review:docs-governanceapi-review:evidence-logapi-review:findings-verifiedCatalog all public APIs by language. Record stability levels, feature flags, and versioning metadata. Use tools like rg to find public symbols (e.g., pub in Rust or non-underscored def in Python). Confirm the working tree state with git status before starting.
Identify at least two high-quality API references for the relevant language, such as pandas, requests, or tokio. Document their patterns for namespacing, pagination, error handling, and structure to serve as a baseline for the audit.
Compare the project's API against the identified exemplar patterns. Analyze naming conventions, parameter ordering, return types, and error semantics. Identify duplication, leaky abstractions, missing feature gates, and documentation gaps.
Validate that documentation includes entry points, quickstarts, and a complete API reference. Verify that changelogs and migration notes are maintained. Check for SemVer compliance, stability promises, and clear deprecation timelines. Confirm that documentation is generated automatically using tools like rustdoc, Sphinx, or OpenAPI.
test cases passed, vs 3 / 16 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.