Menu

Individual skill

event-radar

0upvotes

Turns event attendance into pipeline. Use when prospects attend a webinar, conference, dinner, booth, or monitored industry event and need qualification plus contextual follow-up.

skills/ido-goldberg/event-radar/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Instructions

**Setup state.** Not yet configured for this org. Load the `Setup` sub-page and walk the user through wiring the event-radar trigger (event-platform `WEBHOOK`, `SCHEDULE` + Apify scrape for public attendee lists, or the CRM's attendance workflow) with the right monitored event sources and follow-up sequence before running this play. (After setup is performed, rewrite this paragraph via `swan-update-skill` to describe the current state — trigger source(s) chosen, monitored events by class (owned / exhibited / industry / competitor), ICP filter, sequence wired, success metric, and last-refreshed date — so future runs see the current configuration without re-checking.)

### When this fires

Most commonly `WEBHOOK` from an event platform (Goldcast, Hopin, Splash, Bizzabo, or a manually-uploaded attendee list), `SCHEDULE` + Apify (for public attendee lists of competitor / industry events that the user wants to scrape post-event), the CRM's workflow trigger (if attendance is stored in CRM — discover via `swan-get-available-triggers`), or `WEBSITE_VISIT` as a proxy for post-event landing-page visits.

The 48-72 hour window after an event is the highest-converting time to reach out.

### Step 1 — Classify the event type

The play differs sharply by event class:
Back to top