Agent skill
clay-buying-signals-5
5 buying signals for Clay workflows with performance benchmarks and workflow tips.
Filed under Prospecting and list building.
From Frontal-so/outbound-skills · 73 skills · 4 · pushed 2026-07-14
What it does when it runs
5 buying signals for Clay workflows with performance benchmarks and workflow tips. Use when setting up signal-based Clay tables, prioritizing outreach triggers, or building intent-based campaigns.
Read from the skill and the 0 files 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
- frontal.so
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It only issues instructions, so there is nothing to bound. - Actions present in the files
- None. Instructions only.
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/Frontal-so/outbound-skills.git /tmp/outbound-skills git -C /tmp/outbound-skills sparse-checkout set "skills/clay-buying-signals-5" mkdir -p ~/.claude/skills/clay-buying-signals-5 cp -R "/tmp/outbound-skills/skills/clay-buying-signals-5/." ~/.claude/skills/clay-buying-signals-5/
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 Frontal-so/outbound-skills/blob/27cd847be5ce7e9b749b1d672cbfb29935d911db/skills/clay-buying-signals-5/SKILL.md, which is licensed MIT (repository). 485 words, 14 headings.
5 Buying Signals for Clay Workflows
1. Recent Job Changes (0-90 days)
Why it works:
- 3x higher response rate
- Peak engagement: days 14-45
- They're actively building their stack
Clay setup:
- Track LinkedIn job changes
- Filter by title/seniority
- Alert within 24 hours of detection
2. Company Hiring for Specific Roles
Why it works:
- Signals budget allocation
- Shows growth trajectory
- Indicates priority areas
Clay setup:
- Monitor job postings (LinkedIn, Indeed)
- Filter by relevant roles
- Track posting volume/velocity
3. Website Visitors
Why it works:
- 25-30% reply rate (they know you)
- Highest intent signal
- Act within 24-48 hours
Clay setup:
- Integrate RB2B or similar
- Enrich visitor data
- Auto-route to outreach sequence
4. Funding Announcements
Why it works:
- New budget available
- Mandate for growth spending
- Reach out 2-4 weeks after
Clay setup:
- Crunchbase integration
- Filter by round size
- Delay outreach 2-4 weeks
5. Technology Changes
Why it works:
- Active buying window
- Fresh pain from transition
- Open to new solutions
Clay setup:
- BuiltWith integration
- Track additions/removals
- Filter by relevant tech
Performance Benchmarks
| Outreach Type | Reply Rate |
|---|---|
| Cold outreach | 6-8% |
| Signal-based | 18-22% |
| Multi-signal stacked | 35-40% |
Signal Workflow Tips
Don't Mention Signal Explicitly
- Prospects get these constantly
- Instead, use signal to inform timing and angle
- Reference the underlying pain, not the trigger
Act Fast
- Hot signals expire in 3-7 days
- Job changes: days 14-45 optimal
- Website visitors: within 24-48 hours
Stack Signals for Heat Scoring
- 1 signal = Standard priority
- 2 signals = High priority
- 3+ signals = Reach out same day
Signal Priority Matrix
| Signal | Priority | Timing | Reply Rate |
|---|---|---|---|
| Website visitor | Highest | <24 hours | 25-30% |
| Job change | High | Days 14-45 | 20-25% |
| Funding | Medium-High | 2-4 weeks | 18-22% |
| Hiring | Medium | 1-2 weeks | 15-20% |
| Tech change | Medium | 1-2 weeks | 15-18% |
Combines with
| Skill | Why |
|---|---|
buying-signals-6 | Strategic view of all signals |
clay-enrichment-9step | Integrate signals into workflow |
gtm-plays-11 | Match signals to specific plays |
cold-email-templates-34 | Get templates for each signal |
Example prompts
Set up Clay to detect job changes and auto-route to outreach.
How do I stack multiple signals for heat scoring in Clay?
Create a workflow that detects funding + hiring signals together.
Part of Frontal — free, open GTM skills for your AI agent. Browse the library →
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.
- buying-signal-amplification by louisblythe · 136
- clay by clay-run · 108
- intent-signals by kenny589 · 63
- clay-gtm-outbound by realjaymes · 55
- clay-to-deepline by getaero-io · 54
- clay-claude-code-skill-pack by forma-norden · 12
- signals by octavehq · 11
- community-signals by taizen-ai · 8
Need help setting it up?
This page tells you what clay-buying-signals-5 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.