Agent Skill

If you build with an AI coding agent - Claude Code, Cursor, Codex, Gemini CLI - you can install the official notify-africa-integration skill so the agent already knows how to integrate Notify Africa correctly the first time.

No more pasting docs into the chat or re-explaining endpoint paths, bearer-token authentication, request payloads, or message status handling. The skill lives in this documentation repository and ships as procedural knowledge: the agent loads it on demand and writes correct integrations from there.

• Source: github.com/iPFSoftwares/notify-africa-docs

What the skill does

Once installed, your agent can:

• Write correct API calls for sending single and batch SMS messages.
• Check delivery status with the message status endpoint.
• Build WhatsApp Business text-message and approved-template sends, plus webhook setup, with the WABA API.
• Apply Notify Africa-specific rules around bearer-token authentication, base URLs, phone-number formatting, sender IDs, and recipient batching.
• Choose and wire up the official SDKs for Node.js, Go, Python, or PHP when an SDK is the better path.

The skill triggers automatically on prompts mentioning Notify Africa, SMS, WABA, WhatsApp Business messaging, sender IDs, Tanzanian phone numbers, or delivery-status checks - you do not have to invoke it by name.

Install

npx skills add iPFSoftwares/notify-africa-docs --skill notify-africa-integration

The skills CLI reads the skill from this documentation repository, auto-detects your agent, and writes it into the right directory for that tool.

Update

npx skills update notify-africa-integration

Run after major Notify Africa API or SDK releases so your agent keeps using the latest integration guidance.

When you would use this

• You are prototyping a Notify Africa integration in a coding agent and want correct first-shot output.
• You are onboarding a new engineer who uses Cursor, Claude Code, Codex, or Gemini CLI.
• You are building an agent-driven workflow that needs to create Notify Africa requests from application context.
• You want the agent to pick between direct HTTP calls and the official SDKs without re-reading the docs every time.

If you would rather write the integration yourself, use one of the SDKs or call the HTTP APIs directly.