@vruum/skills 0.4.11 → 0.4.12

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vruum/skills",
3
- "version": "0.4.11",
3
+ "version": "0.4.12",
4
4
  "description": "Vruum AI skills for Claude Code, Claude Desktop, Codex CLI, and any AI assistant with a skill directory. Slash commands for outreach triage, engagement triage, pipeline filling, prospect enrichment, and reply diagnosis. Pairs with the Vruum MCP server at https://api.vruum.ai/mcp.",
5
5
  "license": "MIT",
6
6
  "repository": {
@@ -36,5 +36,5 @@
36
36
  "outreach",
37
37
  "gtm"
38
38
  ],
39
- "contentHash": "e97fce36e8e7631ac79518a817736db2ecca21a991ac08fd9a03264e7c494a9e"
39
+ "contentHash": "3fe3df6fd585a85791c3192124b8122e31ee0be8b035f161f9859981314a4695"
40
40
  }
@@ -32,10 +32,11 @@ Use **UTC** dates in `YYYY-MM-DD` format. The backend filters use inclusive `gte
32
32
 
33
33
  If `get_segments` returns no segments, tell the user "No segments yet — create one in the Vruum app before running diagnosis" and stop.
34
34
 
35
- Classify each segment by reply rate (from `diagnose_segment` output):
35
+ Classify each segment by reply rate (from `diagnose_segment` output). Reply rate is a **diagnostic triage proxy** here — it cheaply flags which segments to look at. It is not segment health itself: the objective is client revenue, and a segment 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 segment healthy.
36
+
36
37
  - **CRITICAL** — 30-day reply rate < 5% with ≥20 sent
37
38
  - **WARNING** — 30-day reply rate 5–10% with ≥20 sent
38
- - **HEALTHY** — 30-day reply rate ≥ 10%
39
+ - **HEALTHY** — 30-day reply rate ≥ 10% (reply-rate-healthy — confirm it also produces meetings/deals before treating it as truly healthy)
39
40
  - **INSUFFICIENT DATA** — `diagnose_segment` returned `insufficient_data: true` (fewer than 20 sent in 30d)
40
41
 
41
42
  For WoW delta, compute `(current_reply_rate - prior_reply_rate) / prior_reply_rate`. Guards: