@feastalytics/cli 0.1.17 → 0.1.18

package/README.md

@@ -6,6 +6,15 @@ Ships with an [agent skill](#agent-skill) so Claude Code, Codex, and other agent
 
 ## Install
 
+Feastalytics ships as a plugin (the `feast` skill plus the hosted MCP server at `https://mcp.feast-api.com/mcp`), as a standalone skill, and as this CLI. The MCP server signs you in with OAuth the first time you connect; there is no client id or API key to enter.
+
+- **Claude Code**: `/plugin marketplace add feastalytics/cli`, then `/plugin install feastalytics@feast`.
+- **claude.ai and Claude Desktop**: add a custom connector with the URL `https://mcp.feast-api.com/mcp`. A directory listing is to follow.
+- **ChatGPT**: `npm run build:chatgpt` writes `dist/feastalytics-chatgpt.zip` (the root `plugin.json`, `mcp.json` and `skills/`).
+- **Skill only** (Claude Code, Codex, Cursor and other agents): `npx skills add feastalytics/cli`.
+
+### CLI
+
 ```bash
 npm install -g @feastalytics/cli
 ```
@@ -66,7 +75,7 @@ Mutations additionally require `--org` and print the server-resolved org before
 
 ## Agent skill
 
-The `feast/` directory is an [agent skill](https://www.skills.sh) that teaches an agent to operate Feastalytics through its tools, either this CLI or the hosted MCP server at `https://mcp.feast-api.com/mcp` (same tools, same names). Install it into your agent(s):
+The `skills/feast/` directory is an [agent skill](https://www.skills.sh) that teaches an agent to operate Feastalytics through its tools, either this CLI or the hosted MCP server at `https://mcp.feast-api.com/mcp` (same tools, same names). Install it into your agent(s):
 
 ```bash
 npx skills add feastalytics/cli
@@ -86,7 +95,7 @@ npx skills add feastalytics/cli -g -a '*' -y
 - `-a '*'` re-links **all** agents (Claude Code, Codex, …) so each picks up the new version.
 - `-y` skips the confirmation prompts.
 
-To refresh from a local checkout instead of GitHub, run `npx skills add ./feast -g -a '*' -y` from the repo root.
+To refresh from a local checkout instead of GitHub, run `npx skills add . -g -a '*' -y` from the repo root.
 
 ### Playbook skills from Feastalytics
 

package/dist/cli.js

@@ -15545,30 +15545,6 @@ var CLI_MANIFEST = {
         "$schema": "http://json-schema.org/draft-07/schema#"
       }
     },
-    {
-      "id": "purchaseAndConfigurePhoneNumber",
-      "domain": "core",
-      "description": "Buys a real number from Twilio for the organization and bills the account. Nothing here undoes that. Pick a number geographically close to the restaurant: guests answer a local area code and read a distant one as spam, so search by the restaurant's own postal code or coordinates, never a guessed area code. If you don't know where the restaurant is, establish it first from its POS location, its Google Place, or by asking. Don't buy until you do.",
-      "type": "mutation",
-      "path": [
-        "api",
-        "onboarding",
-        "purchaseAndConfigurePhoneNumber"
-      ],
-      "inputJsonSchema": {
-        "type": "object",
-        "properties": {
-          "phoneNumber": {
-            "type": "string"
-          }
-        },
-        "required": [
-          "phoneNumber"
-        ],
-        "additionalProperties": false,
-        "$schema": "http://json-schema.org/draft-07/schema#"
-      }
-    },
     {
       "id": "queryData",
       "domain": "data",
@@ -15783,62 +15759,6 @@ var CLI_MANIFEST = {
         "$schema": "http://json-schema.org/draft-07/schema#"
       }
     },
-    {
-      "id": "searchAvailablePhoneNumbers",
-      "domain": "core",
-      "description": "Lists Twilio numbers available to buy for texting guests. Free and read-only. Search by the restaurant's own postal code or latitude/longitude: proximity matters, and a guessed area code lands a number in the wrong town.",
-      "type": "query",
-      "path": [
-        "api",
-        "onboarding",
-        "searchAvailablePhoneNumbers"
-      ],
-      "inputJsonSchema": {
-        "anyOf": [
-          {
-            "type": "object",
-            "properties": {
-              "areaCode": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "areaCode"
-            ],
-            "additionalProperties": false
-          },
-          {
-            "type": "object",
-            "properties": {
-              "postalCode": {
-                "type": "string"
-              }
-            },
-            "required": [
-              "postalCode"
-            ],
-            "additionalProperties": false
-          },
-          {
-            "type": "object",
-            "properties": {
-              "latitude": {
-                "type": "number"
-              },
-              "longitude": {
-                "type": "number"
-              }
-            },
-            "required": [
-              "latitude",
-              "longitude"
-            ],
-            "additionalProperties": false
-          }
-        ],
-        "$schema": "http://json-schema.org/draft-07/schema#"
-      }
-    },
     {
       "id": "searchGooglePlaces",
       "domain": "core",
@@ -23914,9 +23834,6 @@ var CLI_MANIFEST = {
           "completionStatus": {
             "type": "object",
             "properties": {
-              "preProductOnboardingComplete": {
-                "type": "boolean"
-              },
               "postProductOnboardingComplete": {
                 "type": "boolean"
               }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@feastalytics/cli",
-  "version": "0.1.17",
+  "version": "0.1.18",
   "description": "Command-line client for the Feastalytics platform — list, create, and update campaigns, automations, offers, and members-program rewards from the terminal.",
   "type": "module",
   "bin": {
@@ -8,7 +8,8 @@
   },
   "files": [
     "dist",
-    "feast"
+    "!dist/*.zip",
+    "skills"
   ],
   "author": "Feastalytics",
   "license": "UNLICENSED",
@@ -28,7 +29,9 @@
     "dev": "tsx src/cli.ts",
     "feast": "tsx src/cli.ts",
     "typecheck": "tsc --noEmit",
-    "prepublishOnly": "npm run build"
+    "prepublishOnly": "npm run build",
+    "version": "node scripts/sync-plugin-version.mjs && git add .claude-plugin/plugin.json plugin.json",
+    "build:chatgpt": "sh scripts/build-chatgpt-zip.sh"
   },
   "devDependencies": {
     "@trpc/client": "^10.45.2",

package/{feast → skills/feast}/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: feast
-description: Operate a Feastalytics organization (campaigns, automations, funnels, members-program rewards, the wallet pass, creator sourcing, Meta ads, texting, onboarding, and read-only data queries) through the Feastalytics tools, either the `feast` CLI or the Feastalytics MCP server. Use this skill whenever the user wants to inspect or change Feastalytics data outside the dashboard: "list my campaigns", "create an automation for org X", "approve this creator", "publish the recruitment ad", "text this guest back", "query my guests", "update the members program", or any request to script, batch or automate Feastalytics operations. Reach for it even when the user doesn't name the CLI or the MCP server: if the task is reading or changing Feastalytics data, these are the tools.
+description: >-
+  Operate a Feastalytics organization (campaigns, automations, funnels, members-program rewards, the wallet pass, creator sourcing, Meta ads, texting, onboarding, and read-only data queries) through the Feastalytics tools, either the `feast` CLI or the Feastalytics MCP server. Use this skill whenever the user wants to inspect or change Feastalytics data outside the dashboard: "list my campaigns", "create an automation for org X", "approve this creator", "publish the recruitment ad", "text this guest back", "query my guests", "update the members program", or any request to script, batch or automate Feastalytics operations. Reach for it even when the user doesn't name the CLI or the MCP server: if the task is reading or changing Feastalytics data, these are the tools.
 ---
 
 # Feast
@@ -53,10 +54,9 @@ That last point matters most for the tools that reach the real world rather than
 
 - `sendText` texts a guest or creator immediately, one person per call, with no scheduling and no undo.
 - Approving or denying a creator visit (`updateCreatorVisit`) or deciding a submission (`decideCreatorSubmission`) texts that person. `updateCreatorVisit` can preview its texts with `dryRun: true` or skip them with `sideEffects: false`; `decideCreatorSubmission` can skip its text with `skipApprovalText`.
-- Paying a creator's bonus (`createInfluencerPayout`) charges the organization's card.
+- Paying a creator's bonus (`createInfluencerPayout`, on the CLI) charges the organization's card. Over the MCP server that tool is not available, so the client pays bonuses in the dashboard.
 - `awardReward` puts a real reward in a member's wallet pass, and a retried call grants a second one.
 - `inviteUser` sends a real email.
-- Buying a phone number bills the account.
 - Publishing a campaign puts it live, and pricing a recurring promotion creates real Stripe products.
 - Activating a Meta campaign spends real ad budget.
 - Saving automation edits changes what guests receive.

package/{feast → skills/feast}/references/workflows/creators.md

@@ -73,6 +73,8 @@ The ads that bring applicants in are tool-drivable end to end:
 
 ### Paying the bonus
 
+Over the MCP server `createInfluencerPayout` is not available: the client pays creator bonuses in the dashboard, so point them there. On the CLI it remains available, as follows.
+
 `createInfluencerPayout` with `{ "eventId": "..." }` charges the organization's card and starts the creator's bonus on its way. **Never call it on your own initiative**: every call needs the client's explicit, fresh approval to pay this specific creator; a standing instruction doesn't count. The endpoint enforces its own preconditions (a submission approved with `approvalType: "ad"`, no payout already active for the visit: one per visit). The amount defaults to the bonus stamped on the submission when it was approved (falling back to the board config), grossed up to cover the Stripe fee; pass `amountCents` only when the client explicitly asks to pay this one creator a different amount. It applies to this payout only, is written back to the submission so reporting matches what was paid, and leaves the board config unchanged. A visit whose only attempts are FAILED or REFUNDED may be retried, which voids the earlier attempt's open invoice first. After the charge, Stripe webhooks carry it to the creator with no further action from you. Follow progress in `queryData` `creators.creatorPayout`, joined to the visit on `visitEventId`.
 
 ### Reimbursing boards

package/{feast → skills/feast}/references/workflows/onboarding.md

@@ -5,7 +5,7 @@
 `getTaskboard` is the single "what needs fixing or finishing" surface: one `entries` list discriminated by `kind`. `task` entries are the org's onboarding tasks; `issue` entries are live-computed misconfigurations (placeholder content, inactive automations, a missing "Text STOP" opt-out, unawarded rewards, wallet pass and pixel problems), each with a `severity`, a human `message` and a `fixHint`. Funnel checks cover only screens reachable from the funnel's start screen, so an orphaned screen raises no issue. Scope with `{"scope":{"type":"onboarding"}}` for tasks only, `{"type":"task","task":{"taskId":"..."}}` for one task, or leave the default `all`.
 
 - **Start from `completionInstructions`, not guesswork.** Every task entry says exactly what completes it and whether it needs a human in a browser. Trust it over inferring from the task name.
-- **Split the work accordingly.** Campaigns, automations, funnel fixes, rewards, brand identity, the phone number, image uploads and the onboarding form are all completable through the tools, so do them. Tasks that need OAuth (Facebook, POS), physical device setup, or in-restaurant staff training cannot be: hand the user that task's **`completionUrl`**, a page where they complete exactly that task. Paste the URL directly in your reply so the user can open it.
+- **Split the work accordingly.** Campaigns, automations, funnel fixes, rewards, brand identity, image uploads and the onboarding form are all completable through the tools, so do them. Tasks that need OAuth (Facebook, POS), physical device setup, or in-restaurant staff training cannot be: hand the user that task's **`completionUrl`**, a page where they complete exactly that task. Paste the URL directly in your reply so the user can open it.
 - **Never claim a task complete or try to mark one.** Statuses are derived from live data by a recompute (triggered by every taskboard read, ~30s lag). Do the underlying work, then re-read the taskboard to confirm the checkmark flipped.
 - Working through onboarding = repeat: `getTaskboard` (scope `onboarding`) → do the tool-doable incomplete required tasks → hand over completionUrls for the rest → re-read to verify.
 
@@ -27,7 +27,7 @@ Browser-only: the brand *import* intelligence (auto-extracting a usable palette
 
 ## Plumbing the taskboard leans on
 
-- **Phone number**: `searchAvailablePhoneNumbers` (free; search by the restaurant's own postal code or coordinates, since proximity beats a memorable area code) then `purchaseAndConfigurePhoneNumber`, which **bills the account irreversibly**. Establish where the restaurant actually is before buying.
+- **Texting number**: there is no tool to search for or buy one. The restaurant's texting number is bought automatically from its location when its Google place is set (see `updateBrandIdentity` above), or the client chooses one in the dashboard's "Choose texting number" task. If neither has happened, hand the user that task's `completionUrl`.
 - **Media**: `getMediaUploadUrl` (PUT the bytes to the presigned URL, then reference the returned key), `listMedia`, `deleteMedia`. This is how logos and offer images get in through the tools.
 - **Team**: `inviteUser` sends a real email immediately and **defaults to OWNER** (full billing access), so always pass `role` explicitly; VIEWER is read-only, SCANNER is for staff running the scanner app. A new person gets an invitation valid for 14 days; someone with a Feast account gets a login reminder and is added right away. Re-inviting an email cancels its pending invites and sends a fresh one. Only an OWNER can invite.
 - **Billing**: `getBillingStatus`, read-only: `hasAccess` answers "can they use the product," `needsPayment` flags the states worth acting on and is what the dashboard reads to put the app behind a payment form. `currentTier` and `subscriptionStatus` describe the plan. `existingOrganizations` lists every organization billed under the same billing admin's subscription (this one included when it is on that subscription), with names and tiers; it is absent for per-organization billing. Every billing write stays in the dashboard.