@whop/cli 0.18.1 → 0.18.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@whop/cli",
-  "version": "0.18.1",
+  "version": "0.18.3",
   "description": "The Whop CLI — build and manage Whop apps from your terminal. Human and agent friendly.",
   "keywords": [
     "agent",

package/skills/whop/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: whop
-description: "Run a business on Whop from the `whop` CLI: websites on *.whop.site, products, checkout, payments, ads, LLC/C-corp formation, hiring, and stats. Use when the user mentions Whop, whop.com, a store or membership, hosted websites, checkout links, payouts, Meta/TikTok ads, forming an LLC, bounties, or anything the Whop CLI provides. Do not use for the internal `whopdev` local-dev CLI."
+description: "Run a business on Whop from the `whop` CLI: economic intelligence for business next steps, websites on *.whop.site, products, checkout, payments, ads, LLC/C-corp formation, hiring, and stats. Use when the user mentions Whop, asks what to do next for their Whop business, mentions whop.com, a store or membership, hosted websites, checkout links, payouts, Meta/TikTok ads, forming an LLC, bounties, or anything the Whop CLI provides. Do not use for the internal `whopdev` local-dev CLI."
 requires_bin: whop
 command: whop
 ---
@@ -17,6 +17,17 @@ The `whop` CLI is the business: ship websites, sell, take payment, run ads, form
 
 Account-scoped commands use the selected business. Pass `--account_id` (`biz_…` or the public route) to target another.
 
+## Find the best next steps
+
+When the caller asks how to grow, improve their business, or decide what to do next, use `whop economic-intelligence` as the source of the recommended actions. Present the actions it returns, preserving any priority it supplies. Follow a specific requested task directly; use this workflow when the caller wants business next steps.
+
+1. Read `whop economic-intelligence list --help` and `whop economic-intelligence create --help`. Target the caller's named or selected business with its `biz_…` account ID. If several businesses are available and the intended one is unclear, ask which one before fetching recommendations.
+2. List existing recommendations with `whop economic-intelligence list --account_id biz_… --format json`. Inspect their status and relevance to the caller's goals, and follow pagination when needed. Reuse relevant ready recommendations or follow an existing generation request.
+3. When fresh recommendations are needed, run `whop economic-intelligence create --account_id biz_… --input 'What should I do next to grow this business?' --idempotency-key <unique-key> --format json`. Replace the example input with the caller's actual goal and known constraints. Reuse the same key if retrying an uncertain request.
+4. Generation is asynchronous. Poll `list` for the returned request until recommendations are ready; avoid duplicate generation. Stop on a reported failure and surface the reason. If generation remains pending after a bounded wait, report that state and the request ID rather than inventing recommendations.
+5. Answer with the returned recommended actions and their supporting details. Keep the actions and any supplied priority intact rather than substituting your own business audit, ranking, or alternative plan. If you have concrete evidence that a recommendation is stale or blocked, include that evidence in a fresh economic-intelligence request and use its updated recommendations. Check execution prerequisites when carrying out a chosen action.
+6. Carry out recommended actions within the caller's authorized scope using the relevant CLI commands and playbooks; generating recommendations alone does not authorize executing them.
+
 ## Working agreement
 
 - Prefer `WHOP_API_KEY` in the environment over `--api-key`. Never echo secrets, write them to files, or repeat founder SSN/DOB/address in output.
@@ -30,6 +41,7 @@ Account-scoped commands use the selected business. Pass `--account_id` (`biz_…
 | Job | Start here | Playbook |
 | --- | --- | --- |
 | Sign in / pick a business | `whop login`, `whop quickstart`, `whop auth account` | — |
+| Find or generate business next steps | `whop economic-intelligence list`, `whop economic-intelligence create` | Find the best next steps above |
 | Ship a website (`*.whop.site`) | `whop apps init --app_type website`, then `whop apps deploy` | [references/websites.md](references/websites.md) |
 | Sell | `whop products create`, `whop plans create`, `whop checkout-configurations create` | — |
 | Customers | `whop members`, `whop memberships` | — |

package/skills/whop/references/websites.md

@@ -46,6 +46,23 @@ The app must use the `whop()` Vite plugin (`@whop/cli/vite`). Missing it fails w
 
 Preview output is a build id. The production URL exists only after promote. `hosted_url` on `whop apps get` is the live app URL — display it; do not treat it as a "complete this step" action link.
 
+## Experimentation
+
+Split traffic between the live production build and one next build of the same app. Whop hosting assigns visitors, serves the bound build, and records exposures. Always this flow — never a client-side test, never `whop experiments exposures`, never promote the treatment. One active experiment per app.
+
+```sh
+whop experiments list --account_id biz_xxx --related_resource '{"object":"app","id":"app_xxx"}' --status active
+whop apps deploy --preview
+whop experiments create --account_id biz_xxx --flag_key xxxxxxxx --bucket_by anonymous \
+  --hypothesis "If we xxxxxxxx for xxxxxxxx, then xxxxxxxx will xxxxxxxx, resulting in xxxxxxxx, because xxxxxxxx. Created by xxxxxxxx." \
+  --related_resource '{"object":"app","id":"app_xxx"}' \
+  --control '{"related_resource":{"object":"app_build","id":"apbu_xxxxxxxx"}}' \
+  --variants '[{"name":"xxxxxxxx","weight":50,"related_resource":{"object":"app_build","id":"apbu_yyyyyyyy"}}]'
+whop experiments activate expt_xxx
+```
+
+`--preview` is the next version. Control is `production_web_build.id` from `whop apps get`. Related resource is the app. Each arm must bind a different build. If the list is non-empty, pause or end that experiment first — do not start a second. Then activate. Hosting does the rest. Flags: `whop experiments create --help`.
+
 ## Dev, secrets, logs
 
 ```sh