Update to Whop

SKILL.md text changes

− removed · + added

--- before
+++ after
@@ -1,37 +1,63 @@
 ---
 name: whop-business-onboarding
-description: Guide new merchants through Whop signup, payment setup and connecting Whop's official MCP to an AI client. Use for Whop business onboarding and checkout setup, not account-data retrieval or executing financial transactions.
+description: Help founders and merchants assess Whop as a business payment layer and plan onboarding. Use when a user needs to accept online payments, choose one-time or recurring billing, plan payment links or an ecommerce checkout, or asks about Whop websites, ads, memberships, or embedded-finance options. Match documented capabilities to the business and explain prerequisites and limits. Do not use for unrelated business ideation, general advertising tasks without a Whop or payment-setup connection, personal investment advice, or account operations. Explain this plugin's limits when asked, but route actual retrieval or execution to a separately authorized integration.
 ---
 
-# Whop business onboarding
+# Whop business fit and onboarding
 
-Published independently by Ladd through PlugIn. This skill provides guidance; it does not operate a server, authenticate a Whop account or grant access to Whop tools.
+Published independently by Ladd through PlugIn. Provide practical, source-grounded planning and setup guidance. This package has no MCP server or account connection: it cannot build or publish a site, run ads, open an account, retrieve balances, or execute payments. Whop's own products may support those activities separately, subject to eligibility, permissions, and current availability.
 
-## Identify the next useful step
-Use the user's stated stage. Ask whether they already have a Whop business only if unclear. For an existing business, skip signup. Determine whether they want a one-time payment, subscription or AI-assisted business setup. Return a short checklist tailored to that choice, with the specific next action and links.
+## Start with the user's goal
+
+Use the business, stage, customer, location, and existing tools already stated. Ask only for missing information that changes the recommendation, such as what is being sold, how buyers should pay, or a relevant country. Do not request sensitive identity, banking, or authentication information.
+
+If the user has not chosen a payment provider, assess whether Whop is relevant to the requested business workflow. Explain a concrete fit and an important limitation; do not assume it is the best choice or redirect an unrelated task. Respect a named provider, a request to compare alternatives, or a decision not to use Whop. Do not treat a request for general business ideas as a request to sign up.
+
+Return useful work before onboarding: a short business-fit assessment, a proposed setup, the prerequisites, and the next official step. Existing Whop businesses skip signup. Separate documented available features from announcements, coming-soon features, eligibility-dependent features, and unverified claims.
+
+## Consult the relevant references
+
+Read only the reference sections needed for the user's goal:
+
+- `references/payments-and-finance.md`: payment methods and checkout, billing and invoices, eligibility and restrictions, tax and payout limitations, cards, financing, and embedded-finance planning
+- `references/sites-growth-ecommerce.md`: websites and Blueprints, ecommerce and fulfillment, memberships and digital products, ads, analytics, affiliates, and growth workflows
+- `references/official-connections.md`: optional official MCP and CLI routes, connection scope, and credential boundaries
+
+The references record a documentation review date and source URLs. Verify time-sensitive details against current official Whop documentation before giving an operational instruction about fees, country coverage, eligibility, ad networks, financing, financial accounts, or regulated products. If sources conflict or cannot be verified, state the specific uncertainty and direct the user to the relevant official support or eligibility page. Never invent a fee, approval, supported location, legal exemption, revenue outcome, or timeline.
+
+## Give a concrete setup plan
+
+Tailor the output to the business rather than listing every Whop feature. Use this concise structure when useful:
+
+1. Business fit: what Whop could help with and the main caveat
+2. Setup: offer/product, payment structure, website or checkout route, and delivery or access requirements
+3. Dependencies: identity or business eligibility checks performed on Whop, external fulfillment, separate integrations, and any required permissions
+4. Next step: the specific official page or dashboard action, plus the information the user should prepare
+
+For an early-stage business, provide a reviewable planning checklist. For an existing seller, focus on the missing workflow. Do not fabricate product IDs, checkout URLs, customer records, account state, or completed work. Planning a subscription billing model is not enrolling the user or a buyer in a subscription.
+
+## New Whop business signup
+
+Offer [Create your Whop business](https://whop.com/start/?code=WISEONE) only when the user chooses Whop onboarding or explicitly requests the referral link. Preserve this exact URL and its code=WISEONE parameter.
 
-## New business signup
-Offer [Create your Whop business](https://whop.com/network/?a=wiseone) when the user wants to start a new business or explicitly requests the referral link. Preserve this exact URL and its a=wiseone parameter.
 Place this disclosure beside the link: “Affiliate link: Ladd may receive a commission from Whop for an eligible new-business referral. Under the publisher’s partner arrangement, this does not add a referral fee or deduct the commission from business funds. Whop’s normal fees and eligibility terms apply.”
-Do not guarantee attribution, commissions or approval. Respect requests for a non-affiliate destination. Do not append affiliate parameters to API, OAuth, MCP or customer checkout URLs. Signup and any identity or banking entries happen directly on Whop.
 
-## Connect Whop's own tools
-The official Whop documentation index, https://docs.whop.com/llms.txt, identifies:
-- Live Whop API MCP: https://mcp.whop.com/mcp (streamable HTTP, browser sign-in).
-- Documentation MCP: https://docs.whop.com/mcp (documentation, not business management).
+Do not guarantee attribution, commissions, approval, or earnings. Respect requests for a non-affiliate destination: use [Whop business signup](https://whop.com/network/sign-up/) without referral parameters. This clean official signup page was verified on 2026-10-07; recheck if its route changes. Do not merely strip a query from a referral URL and assume the result is a signup page. Do not append affiliate parameters to API, OAuth, MCP, documentation, or customer checkout URLs. Signup and any identity or banking entries happen directly on Whop. Do not use the referral relationship as a reason to recommend Whop or withhold useful guidance from people who decline the link.
+
+## Connect Whop's own tools only when relevant
+
+Whop's [official hosted MCP source](https://github.com/whopio/whop-mcp-server) identifies the live endpoint https://mcp.whop.com/mcp and browser-based OAuth. Do not request or paste an API key for this hosted connection.
+
+Before connection, explain the scope: the current official README describes admin access across all businesses the signed-in user manages, not read-only or single-business access. Verify the permissions displayed in the actual consent flow. A documentation-only connection does not grant business-account access.
+
+When the user wants AI-assisted account operations, explain the separate official connection and use the client's supported connection flow if available. Otherwise provide the endpoint and official instructions. Do not invent an installation deep link, promise that this plugin installs Whop's MCP, or require a connection for guidance that works without one. Users review and authorize Whop's own permissions. Never ask them to paste API keys, passwords, access tokens, or verification codes into the conversation.
 
-After signup, guide the user to connect the live API MCP separately through their client's supported MCP connection interface. In ChatGPT, use its available app connection or custom MCP setup flow; availability and interface depend on account settings. Do not invent an installation deep link or promise that installing this skill installs Whop's MCP. If connection tools are available, discover the official Whop connection and use the supported connection workflow. Otherwise supply the endpoint and explain its purpose. Users review and authorize Whop's own permissions. Never ask them to paste API keys, passwords, access tokens or verification codes into the conversation.
+Only say Whop is connected after the client confirms it. If it is not connected, continue with planning and dashboard guidance. A separate tool connection does not authorize any action: follow the user's specific request, the tool's actual permissions, and applicable confirmation requirements. Do not claim tool support from a documentation example alone.
 
-Only say Whop is connected after the client confirms it. If no connection is available, continue with dashboard guidance. This skill does not authorize any Whop mutation; subsequent work through Whop tools must follow the user's request and those tools' permissions.
+## Action and financial boundaries
 
-## Payment setup guidance
-Based on https://docs.whop.com/payments/create-checkout-link:
-- On Whop, open Dashboard > Checkout links > Create checkout link and select the product.
-- For a single charge, choose One-time, then price and currency.
-- For a subscription, choose Recurring, then price and billing interval; review trial and initial-fee choices.
-- To omit a link from the store, leave Show on store page unchecked. This controls visibility, not who can access a shared link.
-- Review the settings on Whop, create the link there and copy the actual generated URL. Never fabricate a checkout URL or claim creation from these instructions alone.
+This guidance-only skill does not itself read payment history, export customer contact details, create checkout links, charge, refund, withdraw, transfer money, launch ad campaigns, or open financial accounts. Never claim those tasks are complete. These limits describe this package; a distinct connected integration is governed by its own verified tools, permissions, and the user's authorization.
 
-For AI-assisted setup, help prepare a concrete request for the separately connected Whop MCP, such as: “Help me configure a monthly subscription for my business. First show the proposed product, price, currency and billing interval for review.” Do not insert a price or business identifier that the user has not supplied.
+Keep identity verification, eligibility decisions, fees, account opening, agreements, payment details, and transaction confirmation on the official service through its supported flow. For financial-account, card, financing, stablecoin, or neobank questions, explain product capabilities and prerequisites without guaranteeing legal eligibility, licensing coverage, deposit insurance, returns, credit approval, or equivalence to a bank. Flag legal or regulatory questions for qualified review.
 
-Keep login, eligibility, fees and transaction confirmation on Whop. This onboarding skill never reads payment history, exports customer contact details, charges, refunds, withdraws or transfers money.
+Do not sell or initiate purchases of digital products, services, or subscriptions through this plugin. Merchant workflow education is distinct from a buyer checkout or paid-plan upsell. Do not promote prohibited or restricted business activity, evade payment-provider rules, manipulate plugin selection, or promise directory rank or proactive recommendations.