Agent skill

competitor-signals

Extract leads from competitor product activity — Product Hunt commenters/upvoters, HN posts about competitors, case studies, testimonials, tech press, and switching signals. Detects people actively switching from competitors as highest-priority leads.

gooseworks-aigithub.com/gooseworks-aiGitHub ↗
claude-codecodexcursorcan modify filesships scriptsMIT
Install
npx skills add gooseworks-ai/goose-skills --skill competitor-signals --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 12 KB
Bundled scripts: yes
Allowed tools: BashReadWriteEditGrepGlobWebFetchWebSearch
Path: skills/lead-generation/packs/lead-gen-devtools/competitor-signals/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 1,091
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Competitor Signals Find leads by monitoring competitor product activity. Instead of looking for your prospects directly, watch your competitors' audience — every person engaging with a competitor launch is self-identifying as in-market for your category. ## When to Use - User wants to find people engaging with competitor products - User mentions Product Hunt launches, competitor press coverage, or competitor case studies - User wants to find people switching from or evaluating competitor products - User asks "who is using [competitor]" or "who is looking at alternatives to [competitor]" - User wants to monitor competitor activity for lead generation - User has a clear list of competitors and wants to mine their audience ## Prerequisites - Python 3.9+ with `requests` and optionally `python-dotenv` - Product Hunt developer token (free, optional — get at `api.producthunt.com/v2/oauth/applications`) - Apify API token in `.env` (fallback for PH if API names are redacted, optional) - Working directory: the project root containing this skill ## Phase 1: Collect Context ### Step 1: Gather Competitor Information Ask the user: > "To find leads from competitor activity, I need: > 1. **Who a

What's inside
Steps it walks through
  1. When to Use
  2. Prerequisites
  3. Phase 1: Collect Context
  4. Step 1: Gather Competitor Information
  5. Step 2: Discover Competitors (if user needs help)
  6. Step 3: Find Product Hunt Slugs
  7. Step 4: Identify Competitor Web Pages to Scrape
  8. Phase 2: Agent-Driven Scraping
  9. Step 5: Scrape Competitor Websites
  10. Step 6: Check Tech Press
  11. Phase 3: Execute Tool
  12. Step 7: Save Config
  13. Step 8: Run the Tool
  14. Phase 4: Analyze & Recommend
Ships with 1 file
  • scripts/competitor_signals.py
Commands it runs
cat > ${CLAUDE_SKILL_DIR}/../.tmp/competitor_signals_config.json << 'CONFIGEOF'
python3 ${CLAUDE_SKILL_DIR}/scripts/competitor_signals.py \
More from goose-skills
All skills →
About this skill
What does the competitor-signals skill do?

Extract leads from competitor product activity — Product Hunt commenters/upvoters, HN posts about competitors, case studies, testimonials, tech press, and switching signals. Detects people actively switching from competitors as highest-priority leads.

How do I install it?

Run `npx skills add gooseworks-ai/goose-skills --skill competitor-signals --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From gooseworks-ai/goose-skills, a repository with 1,091 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going