identify-advocates — Claude Code command: what it does, how to install
identify-advocates scores customers on how ready they are to speak for you in public, then hands back an outreach roster with scores, consent status and next steps.
Apache-2.0 ★ 450 updated 2026-04-03
.claude/commands/identify-advocates.mdWhat identify-advocates does
The command picks customers who could back your product in public and sorts them by the program that fits: a reference call, a webinar slot, a written story, a council seat. Scoring draws on health scores, usage telemetry, NPS/CSAT, deal history and community activity. Value delivered, relationship strength and risk factors are weighed together.
Flags set the bounds. --goal states the ask, such as "enterprise references". --segments narrows by industry or region, --limit caps the list, --signals tells the model which metrics to favour. advocacy-strategist checks the scoring, the advocate-sourcing skill supplies the framework and data templates, and top reference opportunities go to reference-manager.
What comes back: a scored roster with fit notes and suggested asks, a consent status per account, and an outreach plan carrying owner, channel and timing that lands as CRM tasks. Set --exclusions for open escalations and NDA accounts up front.
What it helps with
- pick customers who will agree to a reference call
- match each advocate to a webinar, a story or a council seat
- check consent and NDA limits before anyone reaches out
- give account owners a contact plan wired into CRM tasks
- keep the shortlist inside a set limit and the right segments
Example prompts for the agent
/customer-advocacy-orchestration:identify-advocates --goal "enterprise references" --segments "healthcare,finance" --limit 20/customer-advocacy-orchestration:identify-advocates --goal "webinar speakers" --signals "product usage,NPS"- Run
/customer-advocacy-orchestration:identify-advocates --goal "case studies"and flag every account whose consent status is still open.
How to install identify-advocates
Manually: put the files in place
.claude/commands/identify-advocates.mdCall it with /identify-advocates. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/identify-advocates.mdCall it with /prompts:identify-advocates. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/identify-advocates.prompt.mdManually: put the files in place
.gemini/commands/identify-advocates.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about identify-advocates
How to install identify-advocates in Claude Code?
Copy the command file into your project at .claude/commands/identify-advocates.md.
What does identify-advocates do?
It rates customers on advocacy readiness using delivered value, relationship strength and risk, then returns a candidate roster with scores, consent status and an outreach plan.
What data does the scoring need?
Health scores, usage telemetry, NPS/CSAT, deal history and community activity. The advocate-sourcing skill provides the scoring framework and data templates, while advocacy-strategist validates priorities.
Source text
identify-advocates.md · Apache-2.0
--- name: identify-advocates description: Scores customers for advocacy readiness and produces outreach roster. usage: /customer-advocacy-orchestration:identify-advocates --goal "enterprise references" --segments "healthcare,finance" --limit 20 --- # Command: identify-advocates ## Inputs - **goal** – advocacy need (references, case studies, speakers, advisory board). - **segments** – optional list of industries, regions, or tiers to prioritize. - **limit** – max number of candidates to surface. - **exclusions** – optional filters (active escalations, NDA restrictions). - **signals** – optional metrics to emphasize (product usage, NPS, expansion, community activity). ## Workflow 1. **Data Aggregation** – pull health scores, usage telemetry, NPS/CSAT, deal history, and community participation. 2. **Scoring Model** – apply readiness model (value delivered × relationship strength × risk factors). 3. **Opportunity Tagging** – classify advocates by potential program (reference call, webinar, story, council). 4. **Consent & Risk Review** – check existing permissions, legal constraints, and account escalations. 5. **Output Packaging** – generate roster with recommended outreach scripts and owners. ## Outputs - Candidate list with score, fit notes, and suggested asks. - Consent/compliance status per account. - Outreach plan (owner, channel, timing) tied to CRM tasks. ## Agent/Skill Invocations - `advocacy-strategist` – validates scoring and prioritization. - `advocate-sourcing` skill – provides scoring framework + data templates. - `reference-manager` – receives high-priority reference opportunities. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents