Loading the registry…
Wire contract design — REST, GraphQL, RPC, gRPC choice, versioning strategy, breaking-change discipline, error envelope schemas, pagination patterns, idempotency keys, rate-limit semantics, webhook contracts (signing / retry / ordering), authentication on the wire, SDK ergonomics, and API documentation as the developer entry point. Use when the user mentions: API design, API contract, REST API, GraphQL, gRPC, RPC, OpenAPI, Swagger, JSON Schema, AsyncAPI, problem+json, RFC 9457, RFC 7807, error envelope, error code, pagination, cursor pagination, offset pagination, idempotency, idempotency key, rate limit, rate limiting, 429, X-RateLimit, Retry-After, webhook, webhook signing, HMAC, retry policy, dead-letter, exponential backoff, jitter, API versioning, semantic versioning, breaking change, deprecation, Sunset header, content negotiation, API authentication, Bearer token, API key, OAuth scopes, mTLS, SDK design, API SDK, API docs, developer experience, DX, contract testing, Pact, Spectral, OpenAPI lint. Pair with fullstack-engineer / cloudflare for handler implementation, supabase for data layer, auth0 for auth provider config. Do NOT trigger for: handler implementation (use fullstack-engineer / cloudflare); database schema design (use supabase); auth provider configuration (use auth0 / supabase); UI work consuming an API (use frontend-craft).
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'blaze-sports-intel/blaze-craft (api-craft)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'blaze-sports-intel/blaze-craft (api-craft)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v2.0.11
12 findings · 8.3s
v0.3.74
1 finding · 1.2s
v0.1.0
0 findings · 3.3s
v0.1.0
0 findings · 3.3s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.3s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.0s
v0.71.0
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v2.3.8
No dependency manifest or lockfile was found in this artifact. What each scanner covers
0 findings · 0.2s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 18, 2026 | Caution93 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy ·n/a: not applicableosv-scanner ·n/a: not applicabletrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Caution badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 13 findings above stand exactly as their scanners reported them, at full severity.