favcrm/mcp / skills/favcrm-channel-setup
favcrm-channel-setup
VerifiedUse when checking or connecting FavCRM communication channels, especially WhatsApp Business Embedded Signup from an MCP client or the favcrm CLI.
FavCRM Channel Setup
Use this skill when a merchant asks to connect WhatsApp Business or diagnose whether a communication channel is ready.
Operating Rules
- Check current state first with
get_whatsapp_connection_status. - Create a browser handoff only when WhatsApp is not connected or the user explicitly wants to reconnect.
- Use
create_whatsapp_connect_linkfor Meta Embedded Signup. Meta requires a browser interaction; the agent cannot complete this fully headlessly. - After the user finishes the browser flow, call
get_whatsapp_connection_statusagain. - For plan or module blockers, call
check_plan_operationand show any returned upgrade action.
CLI Flow
favcrm whatsapp status
favcrm whatsapp connect --mode cloud-api
favcrm whatsapp status
Use --mode coexistence only when the user is connecting a WhatsApp Business App number that should coexist with Cloud API.
MCP Flow
- Call
get_whatsapp_connection_status. - If not connected, call
create_whatsapp_connect_linkwithonboardingMode. - Ask the user to open the returned
urlin a browser. - When they confirm completion, call
get_whatsapp_connection_status. - Report WABA ID, phone number ID, verified name, and any pending session state.
Failure Handling
- Expired session: create a new connect link.
- Browser flow abandoned: keep the pending session visible and ask the user to retry.
- Plan/module blocked: call
check_plan_operationfor modulewhatsappand surface upgrade instructions.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 470k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |