Claude 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 scori

LLM Mart · 0 points · 15 5 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download getaero-io-gtm-eng-skills-skills_niche-signal-discovery-adf0f8f.zip · 1 KB

getaero-io/gtm-eng-skills 60 12 forks MIT Updated 2d ago

Part of getaero-io/gtm-eng-skills — 17 skills

Install

skills CLI npx skills add https://github.com/getaero-io/gtm-eng-skills/tree/main/skills/niche-signal-discovery

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install getaero-io-gtm-eng-skills@llmmart

Git git clone https://github.com/getaero-io/gtm-eng-skills.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole getaero-io/gtm-eng-skills collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

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

Quick Start

npm install -g deepline
# Fallback for secure sandboxes: mkdir -p "$HOME/.local" && npm config set prefix "$HOME/.local" && export PATH="$HOME/.local/bin:$PATH" && npm install -g deepline --registry https://code.deepline.com/api/v2/npm/
deepline auth register --wait auto
deepline auth wait --timeout 120 # completes Cowork/browser approval; no-op if already connected
deepline auth status
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.

Files (gtm-eng-skills)

skill-metadata.json 220 B

{
  "documents": {
    "SKILL.md": {
      "kind": "entrypoint",
      "title": "Niche Signal Discovery (renamed to deepline-scoring)",
      "tags": ["deprecated", "alias", "scoring"],
      "providers": []
    }
  }
}

SKILL.md 1.8 KB

---
name: niche-signal-discovery
disable-model-invocation: false
description: 'Deprecated alias. This skill was renamed to `deepline-scoring`. Use when a user or script still invokes `/niche-signal-discovery`: immediately load and follow the `deepline-scoring` skill instead. 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.'
---

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

## Quick Start

```bash
npm install -g deepline
# Fallback for secure sandboxes: mkdir -p "$HOME/.local" && npm config set prefix "$HOME/.local" && export PATH="$HOME/.local/bin:$PATH" && npm install -g deepline --registry https://code.deepline.com/api/v2/npm/
deepline auth register --wait auto
deepline auth wait --timeout 120 # completes Cowork/browser approval; no-op if already connected
deepline auth status
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:

```bash
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.