From afrotools
Use this skill when the user has a failing or broken Afro.tools integration — wrong status codes, auth errors, webhook not firing, unexpected response fields, or any runtime error from a Paycard, LengoPay, NimbaSMS, or other Afro.tools provider. Activate even if the user just pastes an error without context.
How this skill is triggered — by the user, by Claude, or both
Slash command
/afrotools:debugThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
When this skill activates, fetch the spec for the affected provider and capability,
When this skill activates, fetch the spec for the affected provider and capability, then systematically compare it against the user's implementation to find the gap.
Identify the provider slug and capability from the error, code snippet, or user description. Ask if unclear — don't guess.
Fetch the spec:
afrotools.get_spec({ provider: "<slug>", capability: "<capability>" })
Check gotchas first. Most integration failures map directly to a documented gotcha. Read every entry before looking elsewhere.
Cross-check the implementation against the spec:
paycard-amount,
not amount); compare the user's payload against input_schemaSUCCESS,
not success); code: 0 on Paycard means "found", not "paid"Surface the diagnosis clearly:
Creates, edits, and optimizes skills for Claude Code, including drafting, evaluating with test prompts, iterating on performance, and improving skill descriptions for better triggering accuracy.
npx claudepluginhub afrotools/afrotools --plugin afrotools