@vruum/skills 0.6.53 → 0.6.55

package/skills/winback-fill/SKILL.md

@@ -84,7 +84,7 @@ If no hook can be generated → defer the row. Warm via marketing/content first,
 
 Step 6 — Hand off. Two options:
 - **Option A (recommended)**: Approve the list; run `/pipeline-fill` with the prospect_list for harness deep research + outreach. Plans get `outreach_plans.tag = bowtie_pilot:winback`.
-- **Option B**: Direct `manage_outreach` action=start with a winback-flavored campaign (pre-create a `winback_<your-tenant>` campaign — tone: empathetic, no apology, lead with what changed since last conversation).
+- **Option B**: Direct `manage_outreach` action=start with a winback-flavored objective (pre-create a `winback_<your-tenant>` objective — tone: empathetic, no apology, lead with what changed since last conversation).
 
 Step 7 — Success tracking (auto). The calendar webhook records the impact event, equivalent to:
 ```

package/skills/yc-pipeline-fill/SKILL.md

@@ -10,11 +10,11 @@ description: >-
 
 You are the YCombinator harness-mode source for `/pipeline-fill`. You scrape YC's public directory, extract founder LinkedIn URLs, dedup, and hand a candidate list to the orchestrator. No deep research, no harness gate, no save chain in this skill — that's all in `pipeline-fill/RESEARCH-ENGINE.md`.
 
-This is the answer to "DFW CFOs Sales Nav is dead, what now?" — pivot to YC, get 30 founders into the campaign in ~15 minutes.
+This is the answer to "DFW CFOs Sales Nav is dead, what now?" — pivot to YC, get 30 founders into the objective in ~15 minutes.
 
 ## Inputs
 
-- `campaign`: target campaign (single)
+- `objective`: target objective (single)
 - `count`: target number of imports (default 50)
 - `filters` (REQUIRED — no defaults; operator must specify at least one):
   - `team_size_min` / `team_size_max` (proxy for funding stage)
@@ -27,9 +27,9 @@ If the operator runs the skill without filters, prompt: "YC has 5K+ companies
 
 ## Workflow
 
-### Step 1: Load campaign ICP
+### Step 1: Load objective ICP
 
-Call `fetch` type=research_playbook id=<campaign_id> to load ICP context. The downstream subagents need it for classification; capture it now to pass forward.
+Call `fetch` type=research_playbook id=<objective_id> to load ICP context. The downstream subagents need it for classification; capture it now to pass forward.
 
 ### Step 2: Algolia connectivity precheck
 
@@ -153,7 +153,7 @@ Emit the canonical handoff prompt (defined in `pipeline-fill/RESEARCH-ENGINE.md`
 ```
 Candidate list ready: {N} prospects from yc.
 
-NEXT: invoke /pipeline-fill Step 3 onward (deep research → harness gate → save) with this list and campaign {campaign_id}.
+NEXT: invoke /pipeline-fill Step 3 onward (deep research → harness gate → save) with this list and objective {objective_id}.
 
 Continue automatically? (y/n)
 ```

package/skills/campaign-doctor/SKILL.md

@@ -1,121 +0,0 @@
----
-name: campaign-doctor
-description: >-
-  Diagnose and fix struggling outreach campaigns. Use when: fix a campaign,
-  diagnose campaign, why is my campaign not working, campaign health, low reply
-  rate, check campaigns, which campaigns need help.
----
-# Campaign Doctor
-
-You are a campaign diagnostics and optimization agent. Your job is to identify struggling campaigns, diagnose root causes, and recommend (or apply) fixes.
-
-## Workflow
-
-### Step 1: Triage — health + trends
-
-Call `search` with type=campaigns to list all campaigns. For each campaign, dispatch three calls in parallel:
-- `manage_campaign` with action=diagnose and id=<campaign uuid> — returns `health_score` (0–100), reply-rate vs company average, and ranked root causes (targeting, messaging, channel, saturation, cadence, timing).
-- `get_performance_metrics(view='funnel', campaign_id=X, start_date=<today_utc - 6d>, end_date=<today_utc + 1d>)` — current 7-day window (7 full days ending today, inclusive).
-- `get_performance_metrics(view='funnel', campaign_id=X, start_date=<today_utc - 13d>, end_date=<today_utc - 7d>)` — prior 7-day window (7 full days ending the day before current starts — no shared days).
-
-Use **UTC** dates in `YYYY-MM-DD` format. The backend filters use inclusive `gte(start_date)` + `lte(end_date)` against timestamp columns — so passing `end_date = today_utc + 1d` captures all of today's activity (timestamps < tomorrow 00:00 UTC), and the current/prior windows share no days. Example: if today (UTC) is 2026-04-22, current = `(2026-04-16, 2026-04-23)`, prior = `(2026-04-09, 2026-04-15)`.
-
-If the campaign `search` returns no campaigns, tell the user "No campaigns yet — create one in the Vruum app before running diagnosis" and stop.
-
-Classify each campaign by reply rate (from the diagnose output). Reply rate is a **diagnostic triage proxy** here — it cheaply flags which campaigns to look at. It is not campaign health itself: the objective is client revenue, and a campaign can post a strong reply rate while producing no deals (or a weak one while closing). Treat the band as "where to point the diagnosis," and in the operator flow always reconcile it against meetings and the downstream signal (Block 14 below) before calling a campaign healthy.
-
-- **CRITICAL** — 30-day reply rate < 5% with ≥20 sent
-- **WARNING** — 30-day reply rate 5–10% with ≥20 sent
-- **HEALTHY** — 30-day reply rate ≥ 10% (reply-rate-healthy — confirm it also produces meetings/deals before treating it as truly healthy)
-- **INSUFFICIENT DATA** — the diagnose call returned `insufficient_data: true` (fewer than 20 sent in 30d)
-
-For WoW delta, compute `(current_reply_rate - prior_reply_rate) / prior_reply_rate`. Guards:
-- **Brand-new campaign** (prior window sent = 0): show "new campaign, WoW N/A".
-- **Low-volume** (prior window sent < 5): show "low volume — WoW unreliable" instead of a percentage.
-- **Zero-baseline** (prior sent ≥ 5 but prior reply_rate = 0, so denominator would be 0): show the absolute change as percentage points, e.g. "0% → 3.2% (first replies this week)" instead of dividing.
-
-Present results grouped by urgency:
-
-"Campaign health across N campaigns:
-
-CRITICAL:
-- 'IT Directors' — 2.1% reply rate (30d), 145 sent, 1 reply — WoW: -18%
-- 'CFO Northeast' — 3.5% reply rate (30d), 28 sent, 1 reply — new campaign, WoW N/A
-
-WARNING:
-- 'VP Engineering' — 7.2% reply rate (30d), trending down from 11% (WoW -34%)
-
-INSUFFICIENT DATA (< 20 sends in 30d):
-- 'New Campaign' — only 8 sends. Need 20+ for diagnosis. Run /pipeline-fill to add volume, check back in a few days.
-
-HEALTHY:
-- 'DFW CFOs' — 14.3% reply rate (WoW +4%)
-- 'Startup Founders' — 18.1% reply rate (low volume — WoW unreliable)
-
-Want me to diagnose the critical and warning campaigns?"
-
-Key behaviors:
-- Never auto-diagnose `insufficient_data` campaigns. They need more volume first.
-- If `get_performance_metrics` returns an empty funnel for the prior window, treat it as "new campaign, WoW N/A" (not -100%).
-- If the funnel is empty for the current window too, fall back to the 30-day reply rate from the diagnose output — don't show a fake zero.
-
-### Step 2: Diagnose root causes
-
-For each campaign the user wants to diagnose, you already have the diagnose output from Step 1's parallel calls. Present the findings:
-
-"**'IT Directors'** — Health score: 25/100
-
-Root causes (ranked):
-1. **TARGETING (high)**: Average match score 58/100. Replied prospects average 82. Targeting is too broad.
-   → Recommendation: Tighten target titles, add industry filters
-
-2. **MESSAGING (high)**: Reply rate 2.1% vs company average 9.4% — campaign performing at 22% of baseline.
-   → Recommendation: Review tone instructions, consider A/B test
-
-3. **CHANNEL (medium)**: Email 1.2%, LinkedIn 4.8% — LinkedIn is 4x more effective.
-   → Recommendation: Shift channel mix to prioritize LinkedIn
-
-4. **SATURATION (high)**: Pipeline source has 0 profiles available vs 15/day target.
-   → Recommendation: Broaden your Sales Navigator saved search criteria, then run `/pipeline-fill` to add volume. (`/pipeline-fill` is the source-agnostic orchestrator — if Sales Nav is dry, pick `yc` / `csv` / `list` at the source picker instead.)
-
-Want me to apply any of these fixes?"
-
-Key behaviors:
-- If the diagnose call returned `insufficient_data`, surface the tool's own `message` field verbatim. Don't re-derive the threshold logic.
-- When multiple campaigns share the same root cause dimension (e.g., all have messaging issues), recommend a cross-campaign fix first.
-
-### Step 3: Apply fixes (with approval)
-
-For each recommended fix the user approves:
-
-- **Targeting fix**: Suggest specific ICP field changes and call `manage_campaign` with action=update, the campaign id, and a payload of new `target_titles`, `target_industries`, or `positioning_angle`.
-
-- **Messaging fix**: Suggest revised `ai_tone_instructions` or `ai_selling_strategy` and apply them via `manage_campaign` action=update.
-
-- **Channel fix**: Call `manage_campaign` with action=update and a payload of adjusted `allowed_channels`.
-
-- **Saturation fix (recommend only)**: The client flow doesn't manage pipeline sources directly. Instead:
-  1. Explain the saturation issue in plain terms ("your saved search is drying up — fewer new profiles available each day than your target").
-  2. Recommend broadening the Sales Navigator saved search (wider titles, more industries, bigger geography).
-  3. Tell the user to run `/pipeline-fill` to import prospects once they've adjusted the search.
-
-Always confirm before applying. Show the exact fields that will change.
-
-### Step 4: Summary
-
-After all fixes are applied:
-
-"Campaign doctor complete:
-- 'IT Directors': Tightened target titles (removed 3 generic titles), shifted to LinkedIn-first channel mix
-- 'VP Engineering': Updated tone instructions
-- 'CFO Northeast': Suggested broader saved search; run /pipeline-fill once updated
-
-Monitor results over the next 7 days. Run /campaign-doctor again next week to check progress."
-
-## Notes
-
-- Campaign diagnosis (`manage_campaign` action=diagnose) requires 20+ sent touches in 30 days for meaningful analysis. For newer campaigns, wait — do not attempt diagnosis.
-- Reply-rate thresholds for health bands match the diagnose output's `health_score`: <30 ≈ CRITICAL, 30–75 ≈ WARNING, ≥75 ≈ HEALTHY (see `health_score` field).
-- WoW comparison uses two `get_performance_metrics(view='funnel', campaign_id=X)` calls — **always UTC dates in YYYY-MM-DD**, current = `(today-7d, today)`, prior = `(today-14d, today-7d)`. If prior-window sent < 5, show "low volume — WoW unreliable" instead of a percentage.
-- Root causes are ranked by severity. Focus on the highest-severity issues first.
-- Saturation fixes in the client flow are text recommendations only — clients cannot manage pipeline sources directly via MCP; they adjust Sales Nav and run `/pipeline-fill`.