Public API contracts, their first shape and their evolution: REST, GraphQL or gRPC style choice, resource and error models, RFC 9457 problem details, pagination, idempotency keys, OpenAPI specs, breaking-change judgement, versioning schemes, Deprecation and Sunset headers. Use when asking "design this endpoint", "REST or GraphQL or gRPC", "what should the error response look like", "add pagination", "make this POST safe to retry", "write the OpenAPI spec", "is this a breaking change", "do we need v2", "add a Sunset header", "deprecate this endpoint". Not for internal module boundaries or retiring a whole feature or system; those sit outside this skill.
cp -r cryptoskill/skills/exchanges/anoscranel-ac-api-design .claude/skills/clawhub install anoscranel-ac-api-designCapabilities below are detected automatically by an open-source scanner that reads the skill's text and scripts (see how this is computed). Not measured means the scanner couldn't make a confident call — it is NOT a green check, and you should treat it as a possible red flag until a human or a stronger scanner has measured it.
unknown
We did not find any well-known hosted services in this skill's text or scripts. This does NOT mean the skill is local-only — it might use services we don't yet recognize, or talk to them through code paths our scanner can't reach. A complete dependency list (every package, library, and binary, with integrity hashes) is on the roadmap; today we only show recognized hosts.
No one has audited this skill yet. That is different from “audited and clean” — it just means no professional reviewer (a security firm, the CryptoSkill team, or a verified independent researcher) has signed off on it. There are no audit reports to read. How reviewer levels work →
SKILL.md → SOURCE.md → TRUST.auto.yaml → Browse directory →
Auto-generated by cryptoskill/extract-capabilities/0.3.1 · hosted-service list version 2026-09-06 · how this is computed