← Back to skills
Skill

niche-signal-discovery

Discover niche first-party signals that differentiate Closed Won vs Closed Lost accounts for ICP analysis. Use when the user provides won/lost customer domain lists and wants differential signals (website content, job listings, tech stack, maturity markers) to build account scoring models and prospecting criteria. Triggers: ICP analysis, niche signals, won vs lost analysis, differential signals, signal discovery, ICP signal report, account scoring signals, lead scoring, first-party signals, buyer signals. Before reading this file, first read deepline-gtm to understand the Deepline CLI tool and how to use it. Then read this file for guidance on the task.

Instructions

niche-signal-discovery (renamed to deepline-scoring)

Quick Start

npm install -g deepline
deepline auth register --wait auto
deepline -h

This skill was renamed. niche-signal-discovery is a temporary alias kept so existing prompts, scripts, and saved commands keep working. It will be removed.

What to do

Load the deepline-scoring skill and follow it for this request. Do not answer from this file; it contains no instructions of its own.

If the skill loader supports names, invoke deepline-scoring. Otherwise read the entrypoint directly, trying these roots in order and using the first that exists:

for candidate in \
  "$PWD/.skills/deepline-scoring" \
  "$HOME/.claude/skills/deepline-scoring" \
  "$HOME/.agents/skills/deepline-scoring"; do
  [ -d "$candidate" ] && { echo "$candidate/SKILL.md"; break; }
done

Then tell the user once, in a single line, that /niche-signal-discovery is now /deepline-scoring, and continue with the actual request.