gtm-engineer-playbook: Skill for Claude Code

.claude/skills/gtm-playbook/signal-scanner/SKILL.md

signal-scanner is a skill for Claude Code from Othmane-Khadri/gtm-engineer-playbook. It costs 58 tokens per session (2,790 once invoked), scanned A, original, MIT.

A research helper that looks for signs a company may be ready to buy, such as new funding, hiring, or product launches.

In plain words
What is it for?
It searches for current buying signals, scores each target account by fit, timing, access, and intent, and saves company reports and a prioritized action list.
Why use it?
It reduces the manual work of checking many companies and helps sales teams decide which prospects to contact first.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is Othmane-Khadri/gtm-engineer-playbook's own configuration. It tells Claude Code how to work on gtm-engineer-playbook itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gtm-engineer-playbook configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Othmane-Khadri/gtm-engineer-playbook. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Othmane-Khadri/gtm-engineer-playbook/main/.claude/skills/gtm-playbook/signal-scanner/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Othmane-Khadri/gtm-engineer-playbook

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for signal-scanner

README.md
[![agentmods](https://agentmods.dev/badge/skills/othmane-khadri/gtm-engineer-playbook/signal-scanner/github.svg)](https://agentmods.dev/skills/othmane-khadri/gtm-engineer-playbook/signal-scanner)
Your own site
<a href="https://agentmods.dev/skills/othmane-khadri/gtm-engineer-playbook/signal-scanner"><img src="https://agentmods.dev/badge/skills/othmane-khadri/gtm-engineer-playbook/signal-scanner/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for signal-scanner

Your own site · 80×15
<a href="https://agentmods.dev/skills/othmane-khadri/gtm-engineer-playbook/signal-scanner"><img src="https://agentmods.dev/badge/skills/othmane-khadri/gtm-engineer-playbook/signal-scanner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,790 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00058 $0.02790
Opus 5 $0.00029 $0.01395
Sonnet 5 $0.00012 $0.00558
Haiku 4.5 $0.00006 $0.00279

Measured 12d ago against content hash f36dc09f1ba6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

signal-scanner scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/gtm-playbook/signal-scanner/SKILL.md · 243 lines

How it starts

The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Signal Scanner

Detect, score, and prioritize buying signals for target accounts. This skill searches for live signals using WebSearch, scores them on a Fit x Timing x Access x Intent framework, and produces a prioritized action list for GTM teams.

Tools Used

  • WebSearch — find real-time signals (funding, hiring, product launches, etc.)
  • Read — load docs/icp.md if it exists (output from the ICP Architect skill)
  • Write — save per-company signal reports and summary
  • Glob — check for existing signal files to avoid duplicate work

Methodology

Follow these steps in order. Do not skip steps. Do not fabricate data.

Step 1: Context Loading

Check if docs/icp.md exists using Glob.

If it exists: Read it. Extract ICP segments, buyer personas, and known buying signals. Summarize what you loaded so the user can confirm.

If it does not exist: Ask the user three questions before proceeding:

  1. What does your company sell? (one sentence)
  2. Who is your ideal buyer? (title, company size, industry)
  3. What signals indicate someone needs your solution? (list 3-5)

Wait for answers. Do not assume.

Step 2: Signal Taxonomy

Present the full taxonomy of 20 signal types across 4 categories. Ask the user to select 8-12 that are most relevant to their business. Only scan for the selected signal types in Step 3.

Company-Level Signals
  1. Fundraise announcement — Seed, Series A, B, C+ rounds
  2. Leadership change — New CXO, VP Sales, VP Marketing, Head of Growth
  3. Hiring pattern — SDR hiring spree, GTM engineering roles, marketing hires
  4. Product launch — Major feature release, new product line, GA announcement
  5. Partnership or integration — New tech partner, channel partner, integration announcement
  6. Tech stack change — Detected via job postings, BuiltWith, Wappalyzer, or press releases
  7. Office expansion — New market entry, new office location, international expansion
  8. Pricing change — New tier launch, pricing model shift, free tier added/removed

Read the full file on GitHub · 243 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 12d ago First seen · 243 lines · 58 tokens per session scan A f36dc09f1ba6

Subscribe to this mod's changes

signal-scanner is a skill published in the GitHub repository Othmane-Khadri/gtm-engineer-playbook (56 stars, last pushed 5mo ago), licensed MIT. It adds 58 tokens to every session and 2,790 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

go-to-market-playbook

A reusable Go-to-Market strategy template for both B2B and B2C launches. Covers positioning, messaging, ICP definition, channel selection, and competitive analysis frameworks. By @WeiYipei.

Gingiris-1031/gingiris-skills · 48 tokens

adoption-leaderboard

Scores a rep's or a team's recent sales calls against a fixed set of five winning-behavior checklists (rapport, upsell signals, renewal risk, customer experience, value realization), then ranks reps lowest-adoption-first so the highest-leverage coaching targets lead. Use when running a team calibration, prepping 1:1…

zime-ai/zime-gtm-skills · 96 tokens

challenger

Audits a B2B sales call transcript against the Challenger Sale framework (teach, tailor, take control, plus the commercial-teaching pitch arc), or sweeps a CRM export for deals with no teaching insight logged. Use when a rep leans on discovery-question skill but rarely brings a point of view, when prepping a rep for a…

zime-ai/zime-gtm-skills · 104 tokens

champion-tracker

Tracks champion strength across a deal's call(s) — builds an action ledger, one row per named contact per cited quote, tagging each as either an act of internal selling (looping in a stakeholder, pushing back for the rep in a room the rep wasn't in) or mere positive sentiment (encouraging words, no action), then reads…

zime-ai/zime-gtm-skills · 112 tokens

executive-briefing

Writes the short brief a rep sends upward out of one deal — to their own exec or the buyer's exec sponsor — covering deal snapshot, status, what's at risk, and the ask, each claim cited to a quote or a CSV column/cell. Use when someone who will never read the transcript needs to act on one deal, not a call-by-call…

zime-ai/zime-gtm-skills · 86 tokens

faint

Audits a B2B sales call transcript against the FAINT qualification framework (Funds, Authority, Interest, Need, Timing), or sweeps a CRM export for deals missing FAINT fields. Use when a prospect hasn't articulated a clear need yet but shows financial capacity and curiosity, or when deciding whether a demand-driven…

zime-ai/zime-gtm-skills · 78 tokens