signal-intel — Claude Code skill for ABM signals
signal-intel is a Claude Code skill that combines account intent, product usage, and engagement signals to prioritize ABM actions. It supports account monitoring and signal-driven sales workflows.
Apache-2.0 ★ 450 updated 2026-04-03
npx skills add gtmagents/gtm-agents --skill signal-intel -a claude-codeWhat signal-intel does
signal-intel turns account signals into inputs for ABM prioritization. Its scope covers buyer intent, product activity, engagement, commercial events, and external changes such as hiring or shifts in a company’s tech stack.
The workflow aligns account identifiers across sources, scores signals with rules that account for freshness, and routes alerts through Slack, email, CRM tasks, or MAP triggers. Prioritized accounts then feed into plays; recorded outcomes can inform later changes to signal weights and ROI tracking.
The skill includes templates for scoring, alert ownership and delivery, and data dictionaries. It recommends combining at least two signal categories before launching high-effort plays. Historical snapshots and privacy flags are also part of the process, alongside CRM and marketing-automation suppression rules.
What it helps with
- combine account signals from separate sources
- rank accounts for SDR and AE follow-up
- route alerts when engagement or commercial status changes
- connect account signals to nurture and ad-suppression workflows
- score signals with freshness in mind
Example prompts for the agent
- Combine account signals and rank accounts for ABM actions.
- Set up signal scoring and sales alerts based on current account engagement.
- Draft an alert matrix with signal, delivery channel, owner, and SLA.
How to install signal-intel
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill signal-intel -a claude-code2Manually: put the files in place
~/.claude/skills/signal-intel/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/signal-intel/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill signal-intel -a codex2Manually: put the files in place
.agents/skills/signal-intel/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill signal-intel -a cursor2Manually: put the files in place
.cursor/skills/signal-intel/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install gtmagents/gtm-agents plugins/abm-orchestration/skills/signal-intel2Manually: put the files in place
.github/skills/signal-intel/SKILL.md1Skills CLI (Vercel)
npx skills add gtmagents/gtm-agents --skill signal-intel -a gemini-cli2Platform CLI
gemini skills install https://github.com/gtmagents/gtm-agents --path plugins/abm-orchestration/skills/signal-intelManually: put the files in place
.devin/skills/signal-intel/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about signal-intel
How do I install signal-intel in Claude Code?
Run npx skills add gtmagents/gtm-agents --skill signal-intel -a claude-code. The skill file is at ~/.claude/skills/signal-intel/SKILL.md.
What does signal-intel do?
It brings together account intent, product activity, engagement, commercial events, and external changes, then helps score accounts and route priorities into ABM plays.
Which signals can signal-intel combine?
Its signal categories include intent-platform data, product usage, engagement, commercial details, and external events such as hiring or technology changes.
Source text
SKILL.md · Apache-2.0
--- name: signal-intel description: Use when consolidating intent, product usage, and third-party signals to prioritize ABM actions. --- # Signal Intelligence Systems Skill ## When to Use - Monitoring account readiness for ABM plays. - Prioritizing SDR/AE follow-up based on live engagement. - Coordinating signal-based automations (ads suppression, nurture routing, sales alerts). ## Signal Sources 1. **Intent Platforms** – Bombora, 6sense, ZoomInfo (topics, spike scores, recency). 2. **Product Usage** – PQL metrics, feature adoption, seat utilization, idle license detection. 3. **Engagement** – email/web activity, event attendance, community participation, SDR/AE touchpoints. 4. **Commercial** – opp stages, renewal windows, open tickets, expansion likelihood. 5. **External Events** – hiring, funding, tech stack changes, executive moves, news. ## Framework 1. Normalize identifiers (domain, account ID) across sources. 2. Define scoring rules per signal category with decay functions. 3. Build alerts/automations (Slack, email, CRM tasks, MAP triggers). 4. Feed prioritized lists into plays (target-accounts, plan-plays, monitor-abm). 5. Log outcomes to refine weighting and ROI. ## Templates - Signal scoring worksheet (source, weight, freshness, trigger threshold). - Alert matrix (signal → delivery channel → owner → SLA). - Data dictionary for dashboards/warehouse models. ## Tips - Combine at least two signal types before triggering high-effort plays. - Store historical signal snapshots to correlate with pipeline impact. - Align privacy/compliance flags with marketing automation + CRM suppression rules. ---
© gtmagents · Apache-2.0 · gtmagents/gtm-agents