Skip to content

■ SKILLS // SKILL SPECS

intent-signal-orchestration

Intent signal orchestration covering ingestion, prioritization, and activation plays

■ [!] ON THIS PAGE ▼
■ INSTALL // npx @self.md/cli install intent-signal-orchestration
AuthorGTM Agents
Namespace@gtmagents/gtm-agents
Category#agents
Version1.0.0
Stars★ 64
Downloads↓ 3
Verification[ ✓ ] self.md verified

Intent signal orchestration covering ingestion, prioritization, and activation plays

Installation

npx claude-plugins install @gtmagents/gtm-agents/intent-signal-orchestration

Contents

Folders: agents, commands, skills

Included Skills

This plugin includes 3 skill definitions:

outbound-plays

Use to craft channel-specific outreach sequences that tie directly to

View skill definition

Signal-Aligned Outbound Plays Skill

When to Use

  • Launching targeted SDR/AE campaigns triggered by specific topics or product usage events.
  • Coordinating multi-channel waves (email, phone, social, executive outreach) rooted in current buying triggers.
  • Ensuring messaging references the exact signals that activated the play.

Framework

  1. Trigger Mapping – list top signals/topics and the matched play archetype (e.g., “security spike → exec briefing”).
  2. Persona Customization – define copy blocks, value props, and proof points per persona activated by the signal.
  3. Channel Sequencing – outline cadence (email → call → social) with timing guidelines based on signal freshness.
  4. Measurement Plan – capture metrics per channel (reply rate, meeting rate, pipeline impact) and feedback loops.
  5. Escalation Paths – specify when to escalate to exec sponsor, ABM pod, or customer marketing for references.

Templates

  • Trigger-to-play matrix (signal, persona, playbook, assets needed).
  • Outreach sequence script referencing signal language and talk tracks.
  • Retro doc capturing performance vs control cohorts.

Tips

  • Reference the exact topic or behavior detected in the first touch to prove relevance.
  • Pair with suppression-logic to avoid conflicting outreach when customer success or support is active.
  • Refresh playbooks quarterly to align with evolving product stories and personas.

signal-scoring

Use to design composite intent scoring models with decay, weighting,

View skill definition

Signal Scoring Blueprint Skill

When to Use

  • Designing or revising multi-source signal scoring models.
  • Auditing why certain accounts jump tiers or stay suppressed.
  • Communicating scoring logic to RevOps, sales, and compliance stakeholders.

Framework

  1. Source Inventory – list each signal type, freshness cadence, coverage %, and reliability.
  2. Weighting Model – assign base weights, adjust for persona relevance, and define topic multipliers.
  3. Decay Curves – set time-based decay (hours/days/weeks) per signal category with thresholds for expiration.
  4. Thresholds & Tiers – document what scores map to activation tiers, nurture status, or executive escalation.
  5. Governance – outline ownership, review cadence, and change management triggers.

Templates

  • Scoring worksheet (source, weight, decay, threshold, notes).
  • Tier definition matrix with recommended plays.
  • Change log template capturing rationale, data evidence, and approvals.

Tips

  • Blend at least two independent signals before green-lighting high-effort plays.
  • Version control your scoring logic and share diffs in RevOps channels.
  • Pair with suppression-logic to avoid conflicting triggers.

suppression-logic

Use to define guardrails that pause signal-driven plays when accounts

View skill definition

Suppression Logic Playbook Skill

When to Use

  • Building global do-not-touch rules shared across marketing, sales, and success workflows.
  • Investigating why an account never triggers despite strong intent scores.
  • Coordinating with legal, finance, or product teams on sensitive outreach windows.

Framework

  1. Reason Taxonomy – categorize suppression triggers (legal/compliance, commercial conflicts, lifecycle constraints, technical issues).
  2. Detection Methods – outline data sources and queries that flag each trigger (support tickets, security incidents, open opps, payment status).
  3. Routing & Ownership – assign who can override or expire each suppression (CSM, legal, exec sponsor).
  4. Duration Logic – define cooling periods, review cadences, and auto-expiration rules.
  5. Audit Trail – log change history, approvals, and tie-ins to automation or orchestrator commands.

Templates

  • Suppression matrix (reason, trigger condition, owner, duration, override path).
  • Compliance checklist for regulated industries (financial services, healthcare).
  • Alert + reporting format for surfaced conflicts.

Tips

  • Mirror CRM/MAP suppression lists to prevent channel drift.
  • Create heartbeat alerts when suppression counts spike unexpectedly.
  • Pair with signal-scoring adjustments so suppressed accounts stop draining rep capacity.

Source

View on GitHub