@apex-inc/mcp-server 0.41.0 → 0.41.1

package/skills/apex-setup/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: apex-setup
-description: Set up Apex in a repo from the editor. Sign in by browser approval, find or create the shop this repo belongs to, name it, install and wire events, pick the conversion, work the Set up Apex checklist, stop for browser steps, and end on a first experiment or message. Use when someone says "set up Apex", "install Apex", "connect Apex", or runs /setup-apex.
+description: Set up Apex in a repo from the editor. Sign in by browser approval, find or create the workspace this repo belongs to, name it, install and wire events, pick the conversion, work the Set up Apex checklist, stop for browser steps, and end on a first experiment or message. Use when someone says "set up Apex", "install Apex", "connect Apex", or runs /setup-apex.
 ---
 
 # Set up Apex in this repo
@@ -11,21 +11,21 @@ Three rules hold the whole way:
 
 - **No tool marks a step done.** Steps finish when the real thing happens: the name is saved, events arrive, the domain verifies. If a step looks stuck, the thing it waits on has not happened.
 - **The owner's "no" is theirs.** Record a skip or decline only after they say so, in their words.
-- **Every setup reply names the shop it wrote to** (`shop`). If it is not this repo's shop, stop and switch before the next write.
+- **Every setup reply names the workspace it wrote to** (`workspace`). If it is not this repo's workspace, stop and switch before the next write.
 
 The same steps run as the `/setup-apex` prompt.
 
 ## 1. Sign in
 Call get_setup_state. If Apex is not connected yet, the reply carries an approval link: show it, call wait_for_apex_approval, then carry on. Sign-in is browser approval only. Never ask for, paste, or save an API key to set up. If a reply starts with APEX_WAITING_FOR_ACCESS, say so in one sentence, give the link it names, and stop.
 
-## 2. Which shop is this repo
-Read .apex/workspace.json. If it exists, switch_workspace to its workspace_key. If not, look for an Apex snippet or SDK workspace key in the code; that key is the shop, and you write the file. If neither, ask the owner once: one of their workspaces (list_orgs shows them by organization), a new workspace in one of their organizations (create_workspace), or a separate company (create_organization). Ask "separate company, or another site of the same business?" before creating either. Write and commit the file. Every setup reply names the shop it wrote to; if it is not this repo's shop, stop and switch.
+## 2. Which workspace is this repo
+Read .apex/workspace.json. If it exists, switch_workspace to its workspace_key. If not, look for an Apex snippet or SDK workspace key in the code; that key is the workspace, and you write the file. If neither, ask the owner once: one of their workspaces (list_orgs shows them by organization), a new workspace in one of their organizations (create_workspace), or a separate company (create_organization). Ask "separate company, or another site of the same business?" before creating either. Write and commit the file. Every setup reply names the workspace it wrote to; if it is not this repo's workspace, stop and switch.
 
-## 3. Name the shop from the repo
-If get_setup_state shows first-run incomplete, name the merchant before inventing events. Read the repo (package name, README, site config) and propose the organization name, workspace name, what the shop does, how people convert, and the website. Confirm with the owner, then save with update_organization and update_workspace. Set site_install to codebase when you install from this repo.
+## 3. Name the workspace from the repo
+If get_setup_state shows first-run incomplete, name the merchant before inventing events. Read the repo (package name, README, site config) and propose the organization name, workspace name, what the organization does, how people convert, and the website. Confirm with the owner, then save with update_organization and update_workspace. Set site_install to codebase when you install from this repo.
 
 ## 4. Install and wire events
-Install the SDK or snippet the checklist names. Read get_event_spec before writing track calls, scan the code for what the shop actually does, and report it with propose_wiring_plan. Wire those events. Do not invent event names to make a step look done. Then watch them arrive with apex_recent_events and get_wiring_status before moving on.
+Install the SDK or snippet the checklist names. Read get_event_spec before writing track calls, scan the code for what the site actually does, and report it with propose_wiring_plan. Wire those events. Do not invent event names to make a step look done. Then watch them arrive with apex_recent_events and get_wiring_status before moving on.
 
 ## 5. Pick what counts as a conversion
 Ask the owner which event is the sale, signup, or lead that matters. Save it with create_conversion and set_primary_conversion.
@@ -37,7 +37,7 @@ Call get_setup_state after every write and work the next step with the tool it n
 When the next step needs a person (payment, an ad or app store console, DNS, legal acknowledgements), give the link and the reason from the checklist and wait. Use start_integration_install for GitHub, Stripe, ad platforms, and Google Analytics; it polls until connected. After ads are connected, make a paid Apex Link before inventing UTMs.
 
 ## 8. First value
-Once events are live, show the owner what arrived with apex_recent_events, and give them the live stream link it returns so they can watch their own site talk to Apex. Then propose exactly one first step from what you learned about the shop: one experiment with plan_experiment, or one message with recommend_communications. Say why it fits this shop in a sentence. Create nothing live without the owner's yes; a draft they can open is fine.
+Once events are live, show the owner what arrived with apex_recent_events, and give them the live stream link it returns so they can watch their own site talk to Apex. Then propose exactly one first step from what you learned about the organization: one experiment with plan_experiment, or one message with recommend_communications. Say why it fits this workspace in a sentence. Create nothing live without the owner's yes; a draft they can open is fine.
 
 ## Things that look done and are not
 
@@ -52,17 +52,17 @@ Once events are live, show the owner what arrived with apex_recent_events, and g
 
 ```json
 {
-  "workspace_key": "acme-shop-x1",
-  "workspace_name": "Acme Shop",
+  "workspace_key": "atlas-provisions-x1",
+  "workspace_name": "Atlas Provisions",
   "org_name": "Acme Co"
 }
 ```
 
-The workspace key is not a secret; it already ships in the site's snippet. One editor install serves every shop the person can reach, and each repo's file decides which one it is. `create_workspace` and `create_organization` return this file's contents in `repo_binding`.
+The workspace key is not a secret; it already ships in the site's snippet. One editor install serves every workspace the person can reach, and each repo's file decides which one it is. `create_workspace` and `create_organization` return this file's contents in `repo_binding`.
 
 ## Example: two companies, one person
 
-Noah is signed in with his personal workspace. He opens his company's repo and says "set up Apex in this repo." There is no binding file and no snippet, so the agent asks which shop. He picks "a separate company". The agent creates the "Acme Co" organization, switches to its workspace, writes `.apex/workspace.json`, and runs setup. Back in his personal repo, that repo's file sends the agent to his personal workspace with no question asked.
+Noah is signed in with his personal workspace. He opens his company's repo and says "set up Apex in this repo." There is no binding file and no snippet, so the agent asks which workspace. He picks "a separate company". The agent creates the "Acme Co" organization, switches to its workspace, writes `.apex/workspace.json`, and runs setup. Back in his personal repo, that repo's file sends the agent to his personal workspace with no question asked.
 
 ## Keys are for servers