@vruum/skills 0.4.9 → 0.4.10

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vruum/skills",
-  "version": "0.4.9",
+  "version": "0.4.10",
   "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.",
   "license": "MIT",
   "repository": {
@@ -36,5 +36,5 @@
     "outreach",
     "gtm"
   ],
-  "contentHash": "fe89953973a2a52b8a68248751cb90fa8beb8d71fa74c6b0c365798e78d154b5"
+  "contentHash": "34fbd7484c6c20bd09f477dd3e78ab1ef04f41d1b263690006fcff16429b5bbc"
 }

package/skills/pipeline-fill/RESEARCH-ENGINE.md

@@ -188,7 +188,27 @@ If the prospect's company isn't already cached and Phase A produced fresh resear
    - Last-space heuristic: split on the last space. `Jane Smith` → first=`Jane`, last=`Smith`. `Jane van der Merwe` → first=`Jane`, last=`van der Merwe`.
    - **Override with Phase B canonical names** if `fetch_linkedin_data` returned them. LinkedIn's `first_name`/`last_name` fields are authoritative; the heuristic is a fallback for candidates without `linkedin_url`.
 
-2. **Call `save_person_research(first_name=..., last_name=..., company=..., linkedin_url=..., email=..., topics_of_interest=..., recent_posts=..., opening_hooks=..., role_start_date=...)`.**
+2. **Call `save_person_research(...)`.** The backend now requires you to identify the company unambiguously — pick ONE of these two paths:
+
+   **Path A (preferred): pass `company_id`.** Run `save_company_research(...)` first, capture the returned `company_id`, then pass it here.
+
+   **Path B (when Path A isn't done yet): pass `company_name` + at least one anchor.** Required anchors are any of `company_domain`, `company_website`, or `company_linkedin_url`. The data is in the LinkedIn payload you already fetched. The prospect's CURRENT employer is the entry in `work_experience[]` with `end_date: null` — that entry has `company_linkedin_url` (e.g. `https://linkedin.com/company/microsoft`). If you ran `fetch_linkedin_data(include_company=true)`, the separate company response carries `website` and `industry`. Domain can be derived from website (e.g. `microsoft.com` from `https://microsoft.com`) or from the prospect's verified work email.
+
+   **Anchor-less name-only saves are rejected with HTTP 422.** This was hardened to stop orphan stub creation in the companies table — name-only saves were silently producing duplicate rows for common names like Microsoft.
+
+   Example call:
+   ```
+   save_person_research(
+     first_name=..., last_name=...,
+     email=..., linkedin_url=...,
+     # ONE of:
+     company_id=<from save_company_research>
+     # OR:
+     company_name=..., company_linkedin_url=...,  # at least one anchor
+     # ...rest of research fields
+   )
+   ```
+
    - If the prospect already had `person_id` set on the candidate (e.g. operator pasted a Vruum person UUID), pass it explicitly: `save_person_research(person_id=..., ...)` — backend updates rather than creating a new record.
    - The response includes the `person_id`. Capture it for step c.