smithery/gtmagents

signal-scoring

Use to design composite intent scoring models with decay, weighting, and governance.

Installation

$ npx skills add smithery/gtmagents --skill signal-scoring

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,353 B
  • docs SUMMARY.md 106 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

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.