Agent skill
competitor-signals
Competitor engagement signal tracking for B2B outbound.
Filed under Prospecting and list building and Positioning and messaging.
From Frontal-so/outbound-skills · 73 skills · 4 · pushed 2026-07-14
What it does when it runs
Competitor engagement signal tracking for B2B outbound. Use when the user asks about competitor signals, bad review targeting, G2/Capterra scraping, LinkedIn follower scraping from competitors, battle cards, competitor customer targeting, or churned competitor customers. Do NOT use for tech stack changes broadly (use tech-changes skill) or general content engagement (use content-engagement skill).
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 "master-skills/signal-sourcer/.claude/skills/competitor-signals" mkdir -p ~/.claude/skills/competitor-signals cp -R "/tmp/outbound-skills/master-skills/signal-sourcer/.claude/skills/competitor-signals/." ~/.claude/skills/competitor-signals/
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/master-skills/signal-sourcer/.claude/skills/competitor-signals/SKILL.md, which is licensed MIT (repository). 632 words, 9 headings.
Competitor Signals
Competitor signals come from Category III of the signal taxonomy (Based on Likely "In Market"). They reveal prospects actively evaluating alternatives, unhappy with current vendors, or engaging with competitor content. G2 comparison activity = 60 points (Tier 1).
Reference Files
- Read
{SKILL_BASE}/resources/signal-taxonomy.mdfor Category III: Competitors (triggers 8-16) - Read
{SKILL_BASE}/resources/examples/signal-campaigns/gtm-plays.mdfor Play 8 (Bad Reviews) and Play 11 (Inbound Followers)
9 Competitor Triggers (from Taxonomy)
- Churned customers (negative review) - Left competitor, left a bad review
- Churned customers (disintegration) - Integration broke, product sunset
- Current customers (website activity) - Competitor users visiting your site
- Current customers (integration use) - Using a tool that integrates with yours
- In-cycle customers - Actively evaluating competitors now
- Engaged with competitor content - Liking/commenting on competitor posts
- Followers of competitor page - Brand-aware of the category
- Mutual connections with competitor - Network proximity
- G2/Capterra comparison activity - Active vendor comparison
Scoring by Signal Type
| Competitor Signal | Points | SLA | Rationale |
|---|---|---|---|
| G2 comparison (your product vs competitor) | 60 | < 24h | Active vendor comparison |
| Churned competitor customer (bad review) | 50 | < 24h | Pain is documented and public |
| Competitor user visiting your website | 50 | < 1h | Cross-shopping actively |
| In-cycle evaluation | 45 | < 24h | Buying window open |
| Engaged with competitor LinkedIn content | 25 | < 72h | Category interest |
| Follower of competitor page | 15 | This week | Passive awareness |
Play: Bad Reviews Targeting (Play 8)
- Scrape G2/Capterra for negative reviews of competitors (identifiable reviewers)
- Match reviewers to LinkedIn profiles via Clay
- Reference their specific pain point from the review
- Offer an alternative comparison
Template:
Just saw your review of {{competitor}}...
We researched and tested 3 alternatives (that do not suck).
Shall I send the report to you?
Cheers,
[Name]
Play: Competitor LinkedIn Followers
- Scrape competitor LinkedIn company page followers via Clay/Phantombuster
- Filter to ICP contacts (title, company size, industry)
- They are category-aware - position your differentiator
Template:
Hey {{first_name}}, noticed you follow {{competitor}}.
Most {{title}}s I talk to chose us over them because of {{key_differentiator}}.
Worth a quick look? Here is a 2-min comparison: [link]
Play: Competitor Customer Targeting
- Identify competitor customers via BuiltWith, LinkedIn, G2 profiles
- Look for renewal timing (annual contracts = predictable switch windows)
- Time outreach 60-90 days before likely renewal
Key Rules
- Bad reviews are public data - ethical to reference
- Do NOT trash-talk the competitor - position as an alternative, not a replacement
- G2 comparison activity is a Tier 1 signal (60pts) - send competitive battlecard within 24h
- Competitor users on your website = cross-shopping, highest urgency
- Stack with intent data: competitor follower (15pts) + Bombora surge (40pts) + website visit (50pts) = 105pts Hot
Examples
Example 1: "Target unhappy users of our competitor" -> Scrape G2/Capterra negative reviews, match to LinkedIn profiles in Clay, filter to ICP, reference their specific pain point. 50pts signal, SDR personalized outreach within 24h
Example 2: "Someone from a competitor customer just visited our pricing page" -> Compound signal: competitor customer (implied) + pricing visit (80pts). Tier 1 response within 1 hour. They are actively cross-shopping. AE or senior SDR outreach
Example 3: "Scrape our competitor LinkedIn followers for outreach" -> Clay/Phantombuster to scrape followers, enrich with company data, filter ICP, score at 15pts base. Personalized outreach referencing category interest and your key differentiator. Stack with other signals to prioritize
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.
- competitor-profiling by coreyhaines31 · 45,947
- competitor-analysis by OpenClaudia · 664
- competitor-monitoring by shawnpang · 308
- competitor-alternatives by louisblythe · 136
- competitor-mention-handling by louisblythe · 136
- competitor-ads-analyst by thatrebeccarae · 119
- competitor-analysis by manojbajaj95 · 92
- intent-signals by kenny589 · 63
Need help setting it up?
This page tells you what competitor-signals 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.