メニュー
Scans territory for buying signals, weights by ICP tier, and surfaces a prioritized action list. Trigger with "score my territory", "territory health", "what's hot this week", "prioritize my accounts", "rank my accounts", or "where should I focus".
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Post-call debrief. Captures notes, maps to qualification framework, flags gaps, drafts follow-up email. Use when: just got off a call, have call notes to process, need to capture discovery output, want to update qualification status, need a follow-up email, or want to update CRM notes. Triggers: debrief, call notes, just got off, post call, call recap, capture notes, what happened, update MEDDPICC, follow up email after call, notes from meeting, call summary, discovery notes, I just spoke with.
Diagnoses stuck deals and builds a 3-move recovery strategy using MEDDPICC scoring and targeted frameworks. Use when: deal is stalled, competitive threat identified, single-threaded, or process has stopped. Triggers: deal strategy, deal review, stuck deal, advance this deal, competitive play, challenger approach, deal health, how do I win this, competitive strategy, how to advance, deal blocked, reframe strategy.
Builds a complete meeting brief before any discovery, intro, or follow-up call. Never walk in blind. Use when: preparing for a discovery call, intro meeting, follow-up, or AE-led meeting. Includes: exec summary, agenda, qualification gap analysis, key questions, objections, proof points. Triggers: prep, meeting prep, discovery prep, prepare for, call prep, before meeting, discovery call, intro meeting, meeting brief, what should I know, going into a call, prep me.
Reviews full pipeline, assigns forecast categories by MEDDPICC score, calculates coverage and velocity. Use when: doing a pipeline review, preparing a forecast, checking territory health, or finding at-risk deals. Triggers: pipeline review, forecast review, pipeline health, deal health check, commit list, best case list, forecast, coverage analysis, what's my number, pipeline at risk, inspect pipeline, weekly forecast.
Builds a three-act proposal narrative with win themes and executive summary from discovery notes. Use when: deal is qualified (MEDDPICC 20+) and seller needs to write a formal proposal or business case. Triggers: proposal, write proposal, build proposal, proposal narrative, executive summary, business case, win themes, three-act proposal, proposal strategy, proposal draft, write the business case.
Drafts hyper-personalized outreach across all 4 channels. Always reads research file first. Never generic. Use when: writing LinkedIn connection requests, InMail, cold emails, cold call scripts, follow-up messages, or any outreach for a specific contact at an account. Triggers: write outreach, draft message, cold call, cold email, LinkedIn message, InMail, email sequence, follow up, outreach for, message to, reach out to, contact script, call script, sequence.
| name | signal-scoring |
| description | Scans territory for buying signals, weights by ICP tier, and surfaces a prioritized action list. Trigger with "score my territory", "territory health", "what's hot this week", "prioritize my accounts", "rank my accounts", or "where should I focus". |
| version | 1.0.0 |
Purpose: Surface the right accounts at the right time. Not all signals are equal. ICP tier × signal urgency = prioritization.
Input: memory/icp-matrix.md (tier weights) + web research per account + existing research files
Output: memory/territory-signals.md — overwrite with each run
Read memory/icp-matrix.md → extract the Account Tiers table.
If icp-matrix.md doesn't exist → run icp-matrix-builder first, then return here.
Tier weighting for signal priority:
For Tier 1 and Tier 2 accounts, run fresh web research.
If ~~web research is connected, per account run:
"{Company} news announcement 2026"
"{Company} hiring {seller's solution category} engineer 2026"
"{Company} funding investment 2026"
"{Company} leadership change CTO VP 2026"
If not: use built-in web search with the same queries.
Also check existing research files:
accounts/{account}/research/ → read latest file for signals already captured.
For each signal found, score it:
| Signal Type | Base Score | Urgency Window | Why It Matters |
|---|---|---|---|
| Funding round (Series A+) | 22 | 0–60 days | New budget, new mandate |
| Leadership change (CTO/VP/Architect hired) | 20 | 0–90 days | New leader evaluates everything in first 90 days |
| Active hiring surge (5+ relevant roles) | 18 | 0–60 days | Growth = new projects = new spend |
| Product launch announced | 18 | 0–30 days | Creates immediate tech decisions |
| Contract renewal timing (if known) | 20 | 60–90 days before | Evaluation window |
| Competitor product gap announced | 17 | 0–45 days | Window to position |
| Reorg / restructuring news | 15 | 0–60 days | Change = evaluation opportunities |
| Conference speaking appearance | 14 | 0–30 days before | Warm outreach referencing their talk |
| Engineering blog post about relevant pain | 14 | 0–21 days | Author = warm outreach target |
| Job posting mentioning pain/competitor tool | 13 | While posting exists | Architecture decision in progress |
| Expansion to new market / geo | 12 | 0–90 days | New operations = new systems |
| New partnership announced | 10 | 0–60 days | May change stack |
Apply ICP tier multiplier:
Final signal score = base × tier multiplier
# Territory Signals — {YYYY-MM-DD}
## Priority Queue (score 18+, Tier 1-2 accounts)
| Account | Tier | Signal | Signal Score | Urgency Window | Recommended Action |
|---------|------|--------|-------------|----------------|-------------------|
## Watch List (score 12–17)
| Account | Tier | Signal | Score | Window | Notes |
|---------|------|--------|-------|--------|-------|
## Territory Health
| Metric | Count |
|--------|-------|
| Total accounts tracked | |
| Tier 1 accounts | |
| Tier 2 accounts | |
| Active signals (score 12+) | |
| Hot signals (score 18+) | |
| Accounts with no recent signal | |
## Recommended Focus This Week
1. [Account — Signal — Specific action]
2. [Account — Signal — Action]
3. [Account — Signal — Action]
Save to: memory/territory-signals.md (overwrite — current-state snapshot)