afrotools

Use when adding a new API provider to the Afro.tools registry. Point it at the provider's documentation URL (or a local file) and it will: discover all API endpoints, create provider.json, generate schema.json + canonical_example.ts for every capability, run validation, and optionally verify response schemas against the live API. Invoke with: /afrotools:new <docs_url> [category] [provider_slug]. Manual invocation only.

List all available specs in the Afro.tools registry, optionally filtered by category or provider. Manual invocation only.

Use this skill whenever the user wants to integrate, implement, or test a payment API from an African provider — including Paycard, LengoPay, Wave, Djomy, Bictorys, or any provider in the Afro.tools registry. Activate even if the user only says "add payment", "connect to Paycard", or "implement a checkout flow" — always fetch the exact spec before writing any code.

Use this skill whenever the user wants to send SMS messages, OTPs, or bulk notifications via an African SMS provider — including NimbaSMS or any provider in the Afro.tools registry. Activate even for "send a verification code" or "add SMS notifications", not just explicit mentions of a provider name.

Use this skill ONLY when the user has a failing integration that is specifically based on an Afro.tools spec — the user is integrating a provider whose spec exists in the Afro.tools registry (Paycard, LengoPay, Djomy, Wave, NimbaSMS, etc.) and encounters wrong status codes, auth errors, webhook failures, unexpected response fields, or runtime errors. Do NOT activate for generic debugging, non-afrotools providers, or integrations not based on an Afro.tools spec. This skill diagnoses whether the problem is a spec error, a missing gotcha, or an undocumented API change.

Fetch and display the full ATSS spec for a specific provider and capability. Use this to inspect a spec before implementing, review field rules, or check gotchas. Manual invocation only.