用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/whopio/plugins --skill whop-connect命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Connect and verify this workspace's Whop account
The required protocol for any Whop MCP tool call that changes state: the prepare-and-confirm handshake with mcp_confirmation_token, the intent and intent_id attribution fields every operation tool demands, and idempotency_key rules for money movement. Read before the first create, update, delete, refund, payout, transfer, deposit, or formation call in a session, and whenever a Whop tool returns a confirmation token or rejects a call for a missing field.
Run a business on Whop: websites on *.whop.app, products, checkout, payments, payouts, memberships, ads, LLC/C-corp formation, bounties, and stats. Use when the user mentions Whop, whop.com, their store, a membership or product, checkout links, payouts or transfers, Meta/TikTok ads, forming a company, or anything the Whop MCP tools provide. Not for the internal `whopdev` local-dev CLI.
正在显示 SKILL.md
| name | whop-connect |
| description | Connect and verify this workspace's Whop account |
| disable-model-invocation | true |
Confirm the Whop MCP server is connected and report what the grant can reach. Do not skip ahead to a business action — this command's only job is the connection.
Call connection_status.
It works → report, in plain language: the authenticated user
(user_name), the permission profile, and how many tools are available.
Then handle the account:
account_id is set → name the account and its biz_… id.account_id is null → say plainly that no account is selected yet, then
call accounts_list. One account: name it and say it will be used when the
user passes its id. Several: list them and ask which. None: say the user has
no Whop business yet and point them at whop.com.Do not invent an account, and do not report a null account as if it were one. Then stop and ask what they want to do.
The tool is missing entirely → the MCP server has not loaded. Tell the user
to open /plugins and confirm the whop plugin is enabled, then /mcps to
check the whop server's state. grok mcp doctor whop diagnoses configuration
and connectivity, and takes --json.
It returns unauthenticated → the OAuth flow has not completed. Tell them to
open /mcps, select whop, and press i to authenticate. The browser opens to
Whop for sign-in and authorization. No API key is involved — if they are
reaching for one, that is the wrong path for this server. Grok also triggers
this flow automatically the first time it uses a Whop tool.
Say what they authorized. The hosted endpoint requests the MCP admin scope:
full administrative access to the reviewed MCP surface, across every business
the signed-in user manages — not scoped to one business. Worth one sentence so
they know what they granted, and that they can revoke it from /mcps later.