@vruum/skills 0.4.1 → 0.4.3
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.
|
@@ -20,6 +20,8 @@ You are an engagement review agent with access to 5 Vruum MCP tools for engageme
|
|
|
20
20
|
|
|
21
21
|
The orchestrator will tell you which type and provide IDs.
|
|
22
22
|
|
|
23
|
+
If your dispatch prompt includes an instruction block about scoping MCP calls to a specific company, follow those instructions exactly.
|
|
24
|
+
|
|
23
25
|
---
|
|
24
26
|
|
|
25
27
|
# Engagement Review Instructions
|
|
@@ -20,6 +20,8 @@ You are an outreach review agent with access to 8 Vruum MCP tools for message re
|
|
|
20
20
|
|
|
21
21
|
You do NOT approve or send messages. You review, edit if needed, and return a structured summary.
|
|
22
22
|
|
|
23
|
+
If your dispatch prompt includes an instruction block about scoping MCP calls to a specific company, follow those instructions exactly.
|
|
24
|
+
|
|
23
25
|
## Step 1: Load your messages
|
|
24
26
|
|
|
25
27
|
Call `get_outreach_review` with your assigned `message_ids` and `content_length="full"`. This returns full context for each message including:
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@vruum/skills",
|
|
3
|
-
"version": "0.4.
|
|
3
|
+
"version": "0.4.3",
|
|
4
4
|
"description": "Vruum AI skills for Claude Code, Codex CLI, and any AI assistant with a skill directory. 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": "
|
|
39
|
+
"contentHash": "5cd9f12d62a025c0c17b3d68702df7e9f9a823e3217785ea070d6f5f6f6afa78"
|
|
40
40
|
}
|
|
@@ -6,6 +6,15 @@ description: >-
|
|
|
6
6
|
diagnosis, analyze this reply, what caused this reply, reply analysis.
|
|
7
7
|
---
|
|
8
8
|
|
|
9
|
+
## Auto-update check
|
|
10
|
+
|
|
11
|
+
Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
|
|
12
|
+
- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
|
|
13
|
+
- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
|
|
14
|
+
- Empty → proceed silently.
|
|
15
|
+
|
|
16
|
+
Never block skill execution on this check.
|
|
17
|
+
|
|
9
18
|
# /diagnose-reply
|
|
10
19
|
|
|
11
20
|
You diagnose individual replies to understand what worked (or didn't) in the outreach that preceded them. This turns every reply into a learning event.
|
|
@@ -7,6 +7,15 @@ description: >-
|
|
|
7
7
|
prospect briefing.
|
|
8
8
|
---
|
|
9
9
|
|
|
10
|
+
## Auto-update check
|
|
11
|
+
|
|
12
|
+
Before starting, run `~/.vruum/bin/vruum-skills-update-check` (path relative to this repo). Interpret output:
|
|
13
|
+
- `UPGRADE_AVAILABLE <old> <new>` → mention the available upgrade in one line and offer `/vruum-upgrade`. Then continue.
|
|
14
|
+
- `JUST_UPGRADED <old> <new>` → acknowledge in one line, then continue.
|
|
15
|
+
- Empty → proceed silently.
|
|
16
|
+
|
|
17
|
+
Never block skill execution on this check.
|
|
18
|
+
|
|
10
19
|
# /enrich-prospect
|
|
11
20
|
|
|
12
21
|
You diarize a prospect. Read everything available — LinkedIn, company research, match analysis, conversation history, knowledge base — and synthesize a one-page structured profile that reveals the gap between what the data says and what's actually going on.
|