favcrm/mcp / skills/favcrm-team-onboarding
favcrm-team-onboarding
VerifiedUse when inviting a teammate to FavCRM, generating a one-time team invite token, accepting an invite, verifying an emailed invite OTP, or issuing an MCP API key for an invited team member.
FavCRM Team Onboarding
Use this skill when a merchant wants to add another human or agent-operated team member to a FavCRM workspace.
Operating Rules
- To invite a teammate, use
create_team_member_invitefrom an authenticated owner or manager context. - To accept an invite, use the no-auth pair
accept_team_invite_request->accept_team_invite_verify. - Never expose the full returned API key unless the user explicitly needs to configure a client. Prefer storing it in the MCP client, CLI config, or environment variable.
- Do not invent roles. Use
staffby default, ormanageronly when the user asks for elevated access.
CLI Flow
favcrm team invite create --email teammate@example.com --role staff
favcrm team invite accept-request --token <invite-token>
favcrm team invite accept-verify --token <invite-token> --code <code>
MCP Flow
- Call
create_team_member_invitewithemail, optionalname, androle. - Give the invite token or invite link to the invited user.
- Call
accept_team_invite_requestwithtoken. - Ask the invited user for the 6-digit code from email.
- Call
accept_team_invite_verifywithtoken,code, and optionalname. - Return secure key handling guidance. The API key is shown once.
Failure Handling
- Expired invite: ask an authenticated manager to create a new invite.
- Wrong code: retry
accept_team_invite_verifywith the corrected 6-digit code. - Role/permission denied: call
check_plan_operationor ask an owner/manager to perform the invite.
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: 471k | 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 |