Agent SkillsAgent Skills
gtmagents

signal-intel

@gtmagents/signal-intel
gtmagents
141
26 forks
Updated 4/7/2026
View on GitHub

Use when consolidating intent, product usage, and third-party signals to prioritize ABM actions.

Installation

$npx agent-skills-cli install @gtmagents/signal-intel
Claude Code
Cursor
Copilot
Codex
Antigravity

Details

Pathplugins/abm-orchestration/skills/signal-intel/SKILL.md
Branchmain
Scoped Name@gtmagents/signal-intel

Usage

After installing, this skill will be available to your AI coding assistant.

Verify installation:

npx agent-skills-cli list

Skill Instructions


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.