mcpField
S
signal-scoring

signal-scoring

github.com/gtmagentsMarketing & growth42870 installsUpdated 30w ago
Repository

About signal-scoring

signal-scoring is a marketing skill for designing and reviewing multi-source signal scoring models, intended for RevOps, sales, and compliance stakeholders. It helps document signal weights, decay, tier thresholds, and governance.

Key features

  1. 01Inventory signal sources, freshness, and reliability
  2. 02Set weights and topic multipliers by relevance
  3. 03Define time decay for signal categories
  4. 04Set score thresholds and activation tiers
  5. 05Document ownership, reviews, and changes

Use cases

  1. 01Design or revise multi-source signal scoring models
  2. 02Investigate why accounts change tiers or remain suppressed
  3. 03Explain scoring logic to RevOps, sales, and compliance teams

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/gtmagents/gtm-agents --skill signal-scoring

After installing, type/signal-scoringin Claude Code to confirm it loaded.

Details

From the project README

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.

Comments

Markdown supported