Systems Lab

Agent skill

signal-detection-pipeline

Detect buying signals from multiple sources, qualify leads, and generate outreach context

dormantSelf-containedInstructions only314 words

Filed under Prospecting and list building.

From edupegoretti/fluidz-skills · 116 skills · 0 · pushed 2026-03-11

What it does when it runs

Detect buying signals from multiple sources, qualify leads, and generate outreach context

Read from the skill and the 1 file bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply
None found.
Hosts it reaches
No third-party host appears in the skill or its bundled files.
Tool permissions it declares
No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files
None. Instructions only.

Ask about signal-detection-pipeline

Opens your assistant with this page's verified links already in the prompt.

Is this safe to install?ClaudeChatGPT
Adapt it to my stackClaudeChatGPT
What else do I need for it to workClaudeChatGPT
Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗
git clone --depth 1 --filter=blob:none --sparse https://github.com/edupegoretti/fluidz-skills.git /tmp/fluidz-skills
git -C /tmp/fluidz-skills sparse-checkout set "skills/playbooks/signal-detection-pipeline"
mkdir -p ~/.claude/skills/signal-detection-pipeline
cp -R "/tmp/fluidz-skills/skills/playbooks/signal-detection-pipeline/." ~/.claude/skills/signal-detection-pipeline/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

The skill

Source on GitHub ↗

Reproduced in full from edupegoretti/fluidz-skills/blob/a2cf697e2e8ec2ea517d85496e2d5c7f5dc44cd3/skills/playbooks/signal-detection-pipeline/SKILL.md, which is licensed MIT (repository). 314 words, 10 headings.

Signal Detection Pipeline

Monitor multiple signal sources to find companies actively in-market for your client's solution. Combine signals for higher-confidence leads.

When to Use

  • "Find companies that might need [our product]"
  • "Run signal detection for [problem area]"
  • "Find buying signals in [industry/topic]"

Signal Sources

Run the sources relevant to the client's ICP. Each is independent — run in parallel.

Job Posting Signals (Strongest)

Skill: job-posting-intent

Companies hiring for roles in the problem area = budget allocated and pain acknowledged.

  • Input: Job keywords, ICP criteria
  • Output: Qualified companies with outreach angles

Funding Signals

Skill: funding-signal-monitor

Recently funded companies = budget available, growth mandate.

  • Input: Industry, funding stage filter
  • Output: Funded companies with timing context

Conference Attendance Signals

Skill: luma-event-attendees

People attending events in the problem space = actively engaged.

  • Input: Event URLs or topic search
  • Output: Person/company list

Reddit Pain Signals

Skill: reddit-scraper

People complaining about or discussing the problem = experiencing the pain.

  • Input: Keywords, relevant subreddits
  • Output: Posts with authors, context

LinkedIn Content Signals

Skill: linkedin-post-research + linkedin-commenter-extractor

People posting about or engaging with the problem = thought leaders or practitioners.

  • Input: Keywords, time frame
  • Output: Posters and commenters with engagement data

Combining Signals

After running relevant sources:

  1. Deduplicate companies appearing across multiple signals (multi-signal = strongest leads)
  2. Score each lead: assign signal strength based on source quality and recency
    • Job posting + funding = highest intent
    • LinkedIn post + Reddit complaint = validated pain
    • Single conference attendance = lowest (awareness only)
  3. Enrich top leads with web search for company details
  4. Consolidate into a single Google Sheet: Company, Signal Sources, Signal Strength, Context, Outreach Angle
  5. Prioritize companies with multiple signal types

Human Checkpoints

  • After combining signals: Review consolidated list before outreach

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

Need help setting it up?

This page tells you what signal-detection-pipeline does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.