@vruum/skills 0.6.68 → 0.6.69
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.
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "vruum",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.69",
|
|
4
4
|
"description": "Vruum AI skills + remote MCP server for B2B GTM teams. Slash commands for outreach triage, engagement triage, pipeline filling, prospect enrichment, and reply diagnosis, paired with the full Vruum MCP tool surface over OAuth 2.1.",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Vruum AI",
|
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "vruum",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.69",
|
|
4
4
|
"description": "Connect your Vruum workspace to review revenue priorities, manage deals, research prospects, and prepare outreach through guided skills and authenticated MCP tools.",
|
|
5
5
|
"author": {
|
|
6
6
|
"name": "Vruum",
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vruum/skills",
|
|
3
|
-
"version": "0.6.
|
|
3
|
+
"version": "0.6.69",
|
|
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": {
|
|
@@ -42,5 +42,5 @@
|
|
|
42
42
|
"outreach",
|
|
43
43
|
"gtm"
|
|
44
44
|
],
|
|
45
|
-
"contentHash": "
|
|
45
|
+
"contentHash": "5255b1b8673371f30f2ce8e0d1e4ccb9ece26a22c5b9b2516c07bbe8f1f43446"
|
|
46
46
|
}
|
|
@@ -11,12 +11,12 @@ tenant bind to choose.
|
|
|
11
11
|
# Step 1: pull closed-lost deals (scoped to your session's tenant)
|
|
12
12
|
lost = search(type="deals", filters={"outcome": "lost"}, limit=200)
|
|
13
13
|
|
|
14
|
-
# Step 2: keep deals lost between 90 days and
|
|
14
|
+
# Step 2: keep deals lost between 90 days and 365 days ago
|
|
15
15
|
ninety_days_ago = now() - 90 days
|
|
16
|
-
|
|
16
|
+
oldest_eligible = now() - 365 days
|
|
17
17
|
revival_window = [
|
|
18
18
|
d for d in lost.deals
|
|
19
|
-
if
|
|
19
|
+
if oldest_eligible < parse(d.stage_changed_at) < ninety_days_ago
|
|
20
20
|
]
|
|
21
21
|
|
|
22
22
|
# Step 3: drop terminal loss reasons — these are NOT revivable
|
|
@@ -34,7 +34,7 @@ candidates = [d for d in revivable if d.person_id not in open_person_ids]
|
|
|
34
34
|
Cap the candidate list to the 50 most-recently-lost (sort by
|
|
35
35
|
`stage_changed_at DESC`) before per-account enrichment.
|
|
36
36
|
|
|
37
|
-
The
|
|
37
|
+
The 365-day upper bound prevents revival of ancient conversations the
|
|
38
38
|
buyer has forgotten. The 90-day lower bound prevents the "thanks but no
|
|
39
39
|
thanks" buyer from being re-pitched while the rejection is still fresh.
|
|
40
40
|
|
|
@@ -13,7 +13,7 @@ You are a winback-side pipeline filler. While `/expansion-fill` targets won-and-
|
|
|
13
13
|
|
|
14
14
|
## Why this skill exists
|
|
15
15
|
|
|
16
|
-
A closed-lost deal is not a closed door. Most "lost" deals had a real conversation, a fit signal, and a circumstantial blocker — wrong timing, wrong champion, wrong budget cycle. Within
|
|
16
|
+
A closed-lost deal is not a closed door. Most "lost" deals had a real conversation, a fit signal, and a circumstantial blocker — wrong timing, wrong champion, wrong budget cycle. Within 3-12 months, those circumstances change. The data points worth revisiting:
|
|
17
17
|
- The person is still at the same company (relationship intact)
|
|
18
18
|
- The original loss_reason was NOT `no_fit` or `no_budget_permanent` (the deal was lose-able, not unwinnable)
|
|
19
19
|
- Their company has had a recent trigger (new exec, funding, news event)
|
|
@@ -46,7 +46,7 @@ is automatic from your authenticated session. Pick a variant per your intent
|
|
|
46
46
|
|
|
47
47
|
For variant 1 (silent-deal revival), the cohort criteria:
|
|
48
48
|
- `outcome == 'lost'`
|
|
49
|
-
- `stage_changed_at` between 90 days ago and
|
|
49
|
+
- `stage_changed_at` between 90 days ago and 365 days ago
|
|
50
50
|
- `loss_reason NOT IN ('no_fit', 'no_budget_permanent')` (these are terminal — don't re-pitch)
|
|
51
51
|
- Person is still surfaceable via `get_person_360` (still at company)
|
|
52
52
|
- No open deal currently exists on that person (post-filter against
|