← ClaudeAtlas

apify-google-events-ailisted

Give an AI agent live local event data from Google Events with the Apify Google Events Scraper Actor (johnvc/google-events-api---access-google-events-data). One bounded call takes a query like events in Austin this weekend and returns structured listings, title, start_date, when, address, venue name and rating, and ticket_info seller links, ready for an agent to rank, summarize, or drop into a calendar. Use when the user wants google events ai, an events feed for an AI agent or assistant, event discovery inside Claude, a what is happening this weekend helper, a calendar copilot that suggests concerts or conferences, or wants to wire local events into an app or agent workflow. Pay-per-page billing, MCP-ready for Claude and other AI agents.
johnisanerd/claude-skill-google-events-ai · ★ 0 · AI & Automation · score 66
Install: claude install-skill johnisanerd/claude-skill-google-events-ai
# Google Events AI: A Local Events Feed for Agents Wire Google Events into an AI agent. One bounded call takes a natural ask like "what is happening in Austin this weekend" and returns structured listings with dates, venues, and ticket links, ready for the agent to rank, summarize, or push into a calendar or app. ## When to use this skill - The user wants google events ai: live local event data inside Claude or another agent. - They are building an event-discovery assistant, calendar copilot, or a "what is happening this weekend" helper. - They want an events feed for an app, bot, or agent workflow, refreshed on demand or on a schedule. - They ask "how do I get local events into my AI agent" or "events data for an assistant". Not for: diffing event listings across runs over time (use the google-events-tracking skill), ticket price comparison (`ticket_info` carries seller links, not numeric prices), or attendance and RSVP data (the source does not publish it). ## What the feed returns (one row per results page) Each dataset row is one page of results with a nested `events` array, about 10 events per page. Per event: `title`, `date` (`start_date` and `when` display strings), `address` (venue and city lines), `link`, `description`, `ticket_info` (per-seller `source`, `link`, `link_type`, `source_icon`), `venue` (`name`, `rating`, `reviews`, `link`, when present), and `image`. Page level: `search_parameters`, `search_metadata` (`events_count`, `pages_processed`, `pagination