菜单
Live firm-wide sales pulse from the Epiphan CRM — revenue vs pace, pipeline by stage, won/lost, BDR activity, with coaching takeaways. Use when: business pulse, how are we doing, pipeline health, revenue pace, weekly numbers, standup brief, are we on track, sales snapshot.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Relationship intelligence graph for GTM work. Reads and writes Contact/Account/Deal/Outcome nodes in Neo4j Aura. Syncs contacts/accounts from HubSpot MCP and imports call outcomes from Nooks MCP automatically. Surfaces what messaging, sequences, and personas worked across verticals. Use when: relationship graph, gtm brain, log outcome, what worked with, account map, sync from hubspot, import nooks calls, contact history, sequence performance.
Identify stalled and dying deals, run structured disqualification or recovery workflows, and clean pipeline of dead weight. Finds deals stuck 60+ days, with no champion, no activity, or overdue close dates and prescribes either a final re-engagement campaign or formal disqualification. Keeps pipeline honest and frees mental bandwidth. Use when: 'dead deals', 'stalled deals', 'clean pipeline', 'pipeline cleanup', 'disqualify deals', 'deal graveyard', 'zombie deals', 'which deals should I kill', 'pipeline hygiene', 'deal recovery', 'win back', 'lost deal review', 'close out stale deals'.
Chris Orlob's 5-step discovery framework applied to Epiphan — business problem → cause analysis → negative impact → future state → close. Per-vertical root causes, calibrated question bank, MEDDIC integration, and the 0-3 discovery scoring rubric used by sdr-call-coaching. Use when: discovery framework, orlob discovery, discovery questions, cause analysis, business problem discovery, how to run discovery.
Epiphan Video B2B sales - video capture/streaming lead qualification, pipeline metrics, MEDDIC discovery, and demo execution for Pearl devices, EC20 PTZ, and Epiphan Connect. Use for lead scoring, cold outreach to Higher Ed/Government/Corporate AV, and pipeline reviews.
5-touch email/SMS cadence for Epiphan BDR outreach. Full templates for Higher Ed, Courts, Gov, Healthcare by touch. Companion to epiphan-call-playbook (phone). Writing rules, subject line patterns, and SMS guidelines. Use when: email playbook, email template, outreach email, sdr email, cold email template, sms outreach, follow up email, 5 touch cadence.
Review and batch-send staged Gmail BDR outreach drafts. Lists all queued drafts, shows a prioritized review table (recipient / subject / vertical), and generates one-click Gmail send links so Tim can flush the outreach queue in under 2 minutes. Trigger: send staged drafts, flush draft queue, batch send drafts, review my drafts, what drafts do I have.
| name | business-pulse |
| description | Live firm-wide sales pulse from the Epiphan CRM — revenue vs pace, pipeline by stage, won/lost, BDR activity, with coaching takeaways. Use when: business pulse, how are we doing, pipeline health, revenue pace, weekly numbers, standup brief, are we on track, sales snapshot. |
<quick_start> Trigger: "business pulse", "how are we doing", "weekly numbers", "standup brief". One call gets you 90% of it:
weekly_brief({})
Then synthesize into the Output shape below (never dump raw JSON). For the new SDR cohort or deeper
cuts, use the query_dataset calls in "How to run it". Reference material: reference/ in this skill
epiphan-ai-mcp-guide-skill (golden defaults, owner IDs, verticals pack).
</quick_start>One-shot brief (start here):
weekly_brief({})
Returns revenue (week/MTD/QTD/YTD + prior-year), deals won/lost, new contacts by lifecycle + source, BDR activity, and AE pipeline by stage — already tuned to FY2026 (start 2025-11-01), $19.5M target, BDR IDs 87486452 (Tim) / 423155215 (Ron).
Track the new SDR cohort (Edgar / Vasil / Nyasha — onboarded June 2026) explicitly:
weekly_brief({ bdr_owner_ids: ["93367782","93782443","94135434"] })
query_dataset({ dataset: "rep_activity", group_by: ["owner"],
filters: { owner_ids: ["93367782","93782443","94135434"] } })
(IDs + Nooks mapping live in epiphan-ai-mcp-guide-skill golden defaults.)
Deeper cuts as needed:
query_dataset({ dataset: "pipeline_open", group_by: ["owner","stage"] })
query_dataset({ dataset: "revenue", group_by: ["period_month"], date_from: "2025-11-01", date_to: "2026-11-01" })
query_dataset({ dataset: "deals_closed", group_by: ["outcome"], date_from: <quarter start>, date_to: <quarter end> })
Synthesize into the output shape below — never just dump JSON.
BUSINESS PULSE — week ending <date>
PACE YTD $<x> of $19.5M target → <n>% of FY pace [On / Behind / Ahead]
REVENUE Week $<x> · MTD $<x> · QTD $<x> · YoY <±%>
PIPELINE $<x> open across <n> deals
by stage: Discovery $<x> · … · Commit $<x>
WON / LOST Won <n> ($<x>) · Lost <n> ($<x>) this period
BDR Tim: <dials/connects/meetings> · Ron: <…>
TOP MOVERS <2-3 notable deals advancing or slipping>
SO WHAT (coaching)
1. <where the gap is, and the single highest-leverage action>
2. <a stage with stalled volume → who multi-threads it>
3. <a vertical/segment signal worth a play this week>
There is no native vertical/industry dimension in the datasets (group_by =
period/owner/stage/outcome/country/pipeline/lifecycle/source). So any HigherEd / Community College
/ Live Events / Corporate / Broadcast split is derived — proxy via source/pipeline/country,
or enrich the top open deals account-by-account (sales_brief). Always label a vertical breakdown as
approximate; never present a fabricated clean split. (Vertical pack: epiphan-ai-mcp-guide-skill/reference/verticals.md.)
Output is internal. Naming partners/competitors here is fine; anything buyer-facing must stay clean
(no AV-matrix mechanism, no third-party brand names — "your CMS / LMS"). The pooled figure is "a more
affordable path, a starting point, not a quote." See epiphan-ai-mcp-guide-skill.
<success_criteria>
weekly_brief / query_dataset this run — no stale or fabricated numbers