@apex-inc/mcp-server 0.20.0 → 0.22.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@apex-inc/mcp-server",
-  "version": "0.20.0",
+  "version": "0.22.0",
   "description": "MCP server for Apex — currently in private beta.",
   "type": "module",
   "main": "dist/index.js",

package/skills/apex-adoption/SKILL.md

@@ -12,6 +12,10 @@ The Adoption Engine tracks whether each end-user has adopted each feature, nudge
 - A **milestone** = "has this end-user adopted feature X?" — defined by an event they fire (`report_run`) or a trait (`plan = pro`). It is per-user and per-feature. It is **not** a goal (goals are workspace/experiment/journey success).
 - Apex ranks a user's unmet milestones by priority and sends the single top nudge per cadence — so nobody gets spammed.
 - A ~10% deterministic holdout is kept automatically; the report shows lift vs that holdout, not last-touch attribution. Users in an active experiment are never nudged.
+- A milestone has **two possible journeys**, and they are opposites:
+  - **Nudge** (audience-entry): fires when a user *hasn't* adopted within the gap window. Drives them toward the feature.
+  - **Celebration** (fires once on adoption): congratulates the user the moment they *do* reach the milestone, and tells them what's next. Scaffold both legs in one call with `compose_adoption_milestone` + `scaffold: "both"` (this mirrors the dashboard sentence on-ramp).
+- Milestones can be given a sequence **order** (which one accounts reach first). Ordering the full set unlocks the account-view "Path" funnel (a step-by-step drop-off chart). Unordered milestones are treated as independent (order-agnostic coverage).
 
 ## When to Activate
 
@@ -26,7 +30,9 @@ The Adoption Engine tracks whether each end-user has adopted each feature, nudge
 | `list_adoption_milestones` | See the workspace's current milestones |
 | `get_adoption_milestone` | Inspect one milestone |
 | `create_adoption_milestone` | Define a new "adopted feature" milestone |
-| `update_adoption_milestone` | Change priority / gap window / turn on/off |
+| `compose_adoption_milestone` | Create a milestone AND scaffold its journey legs (`scaffold: "both" \| "celebration" \| "nudge" \| "none"`) in one call |
+| `update_adoption_milestone` | Change priority / order / gap window / turn on/off |
+| `reorder_adoption_milestones` | Set the sequence order of the whole set (unlocks the Path funnel) |
 | `delete_adoption_milestone` | Remove a milestone |
 | `get_adoption_metrics` | Per-milestone funnel + lift-vs-holdout + workspace health |
 | `list_adoption_features` / `create_adoption_feature` | Tenant-owned feature groupings (group your own events) |
@@ -75,6 +81,21 @@ raw `predicate`:
 3. Tell the user it's created as a draft, and that turning it on (`update_adoption_milestone` with `active: true`) starts nudging through their journeys (opt-out + caps respected).
 4. Later: `get_adoption_metrics` → report the lift-vs-holdout so they know whether it worked.
 
+### "Congratulate users when they start their first experiment"
+1. `compose_adoption_milestone` with `name: "Started first experiment"`, `featureKey: "experiments"`, `adoptedWhenKind: "event"`, `eventName: "experiment_started"`, `scaffold: "celebration"`. This creates the milestone AND a draft celebration journey wired to fire once, the moment the user reaches it.
+2. Tell the user the celebration journey is a **draft** — they edit the congratulatory message in the canvas (Communications composer), then publish it.
+3. Turning the milestone on is separate from publishing the journey; both must be live for the celebration to send.
+
+### "Set up a full milestone — nudge the ones who don't, celebrate the ones who do"
+1. `compose_adoption_milestone` with `scaffold: "both"` (e.g. `name: "Started first experiment"`, `featureKey: "experiments"`, `adoptedWhenKind: "event"`, `eventName: "experiment_started"`, `gapDays: 7`). One call creates the milestone plus BOTH draft journeys: the nudge (for users who haven't started an experiment within 7 days) and the celebration (for the moment they do). This is exactly what the dashboard sentence on-ramp produces.
+2. The response carries `nudgeJourneyId` and `celebrationJourneyId` — both are **drafts**. Edit copy in the canvas and publish each.
+3. Turn the milestone on (`update_adoption_milestone` `active: true`) once its nudge is published, so it can measure lift vs the holdout.
+
+### "Put my milestones in the order accounts should hit them"
+1. `list_adoption_milestones` → get the ids.
+2. `reorder_adoption_milestones` with `orderedIds` in the intended sequence (activation before depth).
+3. Tell the user the account view's "Path" funnel is now unlocked — it shows drop-off between consecutive milestones. Without a full order it stays on the order-agnostic "Coverage" view.
+
 ## Guardrails
 
 - Milestones start OFF. Only set `active: true` when the user confirms they want to start sending.

package/skills/apex-communications/SKILL.md

@@ -62,6 +62,24 @@ Read these resources before suggesting communications-related actions to underst
 
 ## Common Patterns
 
+### "Which template should I attach to this journey send step / broadcast?"
+
+`list_communications` IS the picker — use its filters instead of dumping every comm and eyeballing it:
+
+```
+1. list_communications(pipeline="transactional", channel="email")
+   → narrow to the pipeline + channel the step needs. 'transactional'
+     bypasses opt-out and is ONLY valid after a recipient-initiated trigger
+     (user_signup, password_reset_requested). 'marketing' is consent-gated.
+2. Read each row's subject + one-line body preview to disambiguate similar
+   titles — you do NOT need to preview_communication every candidate.
+3. Pick by `id` (+ its version) and attach it to the send step.
+```
+
+Pipeline is load-bearing: attaching a `transactional` comm to a passive-trigger
+journey (schedule / audience-entry / passive event) is a **publish-time
+hard-block**. For those journeys, filter to `pipeline="marketing"`.
+
 ### "I need to send a welcome email"
 ```
 1. recommend_communications → look for "welcome" in results