The full buying group by persona — who's engaged, where the gaps are, and what's moved.
Use it when: you want a stakeholder map, an org / buying-committee view, or to find unengaged decision-makers.
Run it: once installed, say something like “Map the buying group at Acme Health and show me who we haven't engaged.” — or let Claude trigger it automatically.
Automate it (RevOps): schedule monthly in Cowork to sync missing buying-group members into CRM as enriched contacts. For a reviewed alternative, use Contact Reconciliation — don't run both auto-write on the same records.
Install: copy the block below into a file named SKILL.md inside a folder named stakeholder-mapping, then add it to Claude (steps on the Skills Library page).
---
name: stakeholder-mapping
description: "Map an account's full buying group by persona, mark who's engaged, and flag coverage gaps and recent movement. Use when the user wants a stakeholder map, an org/buying-committee view, or to find unengaged decision-makers."
---
# Stakeholder Mapping
## What this skill does
Combines Revealed's external buying group with the user's internal engagement data into a deal-ready map.
## Prerequisites
- **Revealed** connected (external buying-group intelligence) and the account mapped in the user's Revealed workspace.
- **CRM** connected (e.g. HubSpot/Salesforce) for deal and contact context.
- Where the steps call for it: **email (Gmail)**, **calendar**, **meeting notes** (Granola/Gong/Fireflies/Chorus), **Slack**.
- For scheduled runs: **Claude Cowork** or **ChatGPT Scheduled Tasks**.
## How Revealed fits (ground every external claim here)
You operate from two layers of context. **Internal** = what's true inside the user's company: CRM, calendar, email, meeting notes (Granola/Gong/Fireflies/Chorus), Slack. **External** = what's true inside the account: buying group, people movement, account trends, recommended "next moves" — this is **Revealed**.
Rule: pull every external/account signal from Revealed. Do **not** guess or fall back on general training knowledge about the company. If Revealed has no data on an account, say so rather than inventing it.
When calling connected tools, use fully-qualified names (e.g. `Revealed:...`, your CRM such as `HubSpot:...`, `Gmail:...`, `Slack:...`). If a needed tool isn't connected, tell the user which connector to enable rather than fabricating the data.
## Instructions
1. From Revealed: the full buying group grouped by persona. For each person: name, role, primary persona, LinkedIn, and any signals/events in the last 90 days.
2. Cross-reference the user's email, calendar, and CRM contacts. Mark each person: (a) engaged, (b) emailed/no response, or (c) never contacted.
## Output
A map grouped by persona with engagement status, plus three sections: Gaps (needed personas not engaged), Movement in the last 30 days (new hires, departures, role changes, notable posts), and Top priority (the single most important unengaged person and the warmest path to them).
## Automating this skill (RevOps)
Schedule monthly in Cowork to sync missing buying-group members into CRM as enriched contacts (note: this writes to CRM automatically — for a reviewed alternative, use the contact-reconciliation skill instead; don't run both auto-write against the same records).