Diagnose WhatsApp message delivery, webhook issues, and API errors in Kapso.
Works with
Investigate message delivery through phone number resolution, message listing, and conversation inspection using Kapso CLI or fallback Node scripts
Debug webhook deliveries and retries, inspect API logs, and triage message errors to identify root causes of production failures
Run health checks on projects and phone numbers to confirm configuration state and operational readiness
Includes reference guides
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionobserve-whatsappExecute the skills CLI command in your project's root directory to begin installation:
Fetches observe-whatsapp from gokapso/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate observe-whatsapp. Access via /observe-whatsapp in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
100
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
100
stars
Use this skill for operational diagnostics: message delivery investigation, webhook delivery debugging, error triage, and WhatsApp health checks.
Preferred path:
kapso login)kapso status to confirm project access and available WhatsApp numbersFallback path: Env vars:
KAPSO_API_BASE_URL (host only, no /platform/v1)KAPSO_API_KEYPreferred path:
kapso whatsapp numbers resolve --phone-number "<display-number>" --output jsonkapso whatsapp messages list --phone-number "<display-number>" --limit 50 --output jsonkapso whatsapp messages get <message-id> --phone-number-id <id> --output jsonkapso whatsapp conversations list --phone-number "<display-number>" --output jsonFallback path:
node scripts/messages.js --phone-number-id <id>node scripts/message-details.js --message-id <id>node scripts/lookup-conversation.js --phone-number <e164>Preferred path:
kapso statuskapso whatsapp numbers health --phone-number "<display-number>" --output humankapso whatsapp templates list --phone-number "<display-number>" --output jsonFallback path:
node scripts/errors.jsnode scripts/api-logs.jsnode scripts/webhook-deliveries.jsPreferred path:
kapso statuskapso whatsapp numbers health --phone-number "<display-number>" --output humanFallback path:
node scripts/overview.jsnode scripts/whatsapp-health.js --phone-number-id <id>| Script | Purpose |
|---|---|
messages.js |
List messages |
message-details.js |
Get message details |
lookup-conversation.js |
Find conversation by phone or ID |
| Script | Purpose |
|---|---|
errors.js |
List message errors |
api-logs.js |
List external API logs |
webhook-deliveries.js |
List webhook delivery attempts |
| Script | Purpose |
|---|---|
overview.js |
Project overview |
whatsapp-health.js |
Phone number health check |
| Script | Purpose |
|---|---|
openapi-explore.mjs |
Explore OpenAPI (search/op/schema/where) |
Install deps (once):
npm i
Examples:
node scripts/openapi-explore.mjs --spec platform search "webhook deliveries"
node scripts/openapi-explore.mjs --spec platform op listWebhookDeliveries
node scripts/openapi-explore.mjs --spec platform schema WebhookDelivery
integrate-whatsapp.phone_number_id before deep debugging.integrate-whatsapp - Onboarding, webhooks, messaging, templates, flowsautomate-whatsapp - Workflows, agents, and automations[observe-whatsapp file map]|root: .
|.:{package.json,SKILL.md}
|assets:{health-example.json,message-debugging-example.json,triage-example.json}
|references:{health-reference.md,message-debugging-reference.md,triage-reference.md}
|scripts:{api-logs.js,errors.js,lookup-conversation.js,message-details.js,messages.js,openapi-explore.mjs,overview.js,webhook-deliveries.js,whatsapp-health.js}
|scripts/lib/messages:{args.js,kapso-api.js}
|scripts/lib/status:{args.js,kapso-api.js}
|scripts/lib/triage:{args.js,kapso-api.js}
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
observe-whatsapp is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for observe-whatsapp matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: observe-whatsapp is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in observe-whatsapp — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend observe-whatsapp for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
observe-whatsapp is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
I recommend observe-whatsapp for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Useful defaults in observe-whatsapp — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: observe-whatsapp is the kind of skill you can hand to a new teammate without a long onboarding doc.
observe-whatsapp fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 64