event-signals
Extract leads from conferences, meetups, hackathons, and podcasts by analyzing speaker lists, sponsor lists, hackathon entries, and podcast guests. Discovers events via Sessionize, Confs.tech, Meetup, Luma, ListenNotes, and Devpost. Looks back 90 days and forward 180 days.
npx skills add gooseworks-ai/goose-skills --skill event-signals --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Event Signals Extract leads from the conference and events ecosystem. Events represent public declarations of priorities — a VP speaking about "scaling our infrastructure" is a stronger signal than a Reddit comment, and a company sponsoring a conference category has committed real budget. ## When to Use - User wants to find leads from conferences, meetups, or developer events - User wants speaker lists, sponsor lists, or attendee data from events - User mentions KubeCon, AWS re:Invent, DevOpsDays, or any industry conference - User wants to find people who spoke or presented about relevant topics - User asks about hackathon participants using relevant technologies - User wants podcast guests who discussed relevant challenges - User describes prospects who attend industry events or speak at conferences ## Prerequisites - Python 3.9+ with `requests` and optionally `python-dotenv` - Apify API token in `.env` (for Meetup and Luma — optional) - ListenNotes API key in `.env` as `LISTENNOTES_API_KEY` (for podcast search — optional, free tier gives 300 req/mo) - Working directory: the project root containing this skill ## Phase 1: Collect Context ### Step 1: Gather Product & ICP Informati
- When to Use
- Prerequisites
- Phase 1: Collect Context
- Step 1: Gather Product & ICP Information
- Phase 2: Discover Relevant Events
- Step 2: Discover Conferences
- Step 3: Discover Meetups and Local Events
- Step 4: Discover Podcasts
- Step 5: Discover Hackathons
- Step 6: Present Discovery Results
- Step 7: Scrape Conference Websites (Agent-Driven)
- Phase 3: Execute Scan
- Step 8: Save Config File
- Step 9: Run the Tool
cat > ${CLAUDE_SKILL_DIR}/../.tmp/event_signals_config.json << 'CONFIGEOF'
python3 ${CLAUDE_SKILL_DIR}/scripts/event_signals.py \What does the event-signals skill do?
Extract leads from conferences, meetups, hackathons, and podcasts by analyzing speaker lists, sponsor lists, hackathon entries, and podcast guests. Discovers events via Sessionize, Confs.tech, Meetup, Luma, ListenNotes, and Devpost. Looks back 90 days and forward 180 days.
How do I install it?
Run `npx skills add gooseworks-ai/goose-skills --skill event-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.