Agent skill · writing content · sundial-org

event-planner

Plan events (night out, weekend, date night, team outing, meals, trips) by searching venues via Google Places API. Auto-selects best restaurants, bars, activities based on location, budget, party size, and preferences. Generates detailed itinerary with timing and Google Maps link. Use when asked to plan an outing, create an itinerary, find places for events, or organize activities.

Why this skill is useful

Adds executable scripts for planning events with Google Places API that automate venue selection and itinerary generation.

What it needs

Requires uv installed locally. Requires google account access. About 2k tokens when loaded. Last updated 2026-03-07. 639 stars on the source repository.

What this skill does

Event Planner Plan events by searching venues and generating itineraries with Google Maps links. Quick Start Plan a night out: Plan a weekend day: Plan a date night: Event Types night-out: Dinner + 1-2 bars/lounges (3-4 hours) weekend-day: Brunch/lunch + activity + dinner (6-8 hours) date-night: Romantic restaurant + dessert/drinks spot (2-3 hours) team-event: Group activity + dinner venue (3-5 hours) lunch: Single restaurant recommendation dinner: Single restaurant recommendation trip: Multi-day itinerary with daily plans Parameters --location: City, address, or landmark (required) --party-size: Number of people (default: 2) --budget: "low/medium/high" or "$X per person" (default: medium) --duration: Hours available (e.g., "3h", "full day") --preferences: Comma-separated (e.g., "vegetarian, outdoor seating, live music") --start-time: When to start (default: inferred from event type) --output: text json (default: text) --date: Target date in YYYY-MM-DD format for day-specific checks (default: today) Output Format Default (text): Markdown itinerary with timeline, venue details, travel info, and Google Maps link JSON: Structured data with all venue details, coordinates, and parsed metadata Limitations API limits: Google Places API has usage quotas (check your billing) Real-time data: Venue hours may change; always confirm before going Budget estimates: Based on Google's price level (0-4), not exact costs Travel times: Uses Google Directions API when available; falls back to distance-based estimates with 30% buffer Opening hours: Places without verified hours will show warnings; do not assume availability Event venues: Cultural centers, theaters, and event spaces may have variable hours depending on scheduled events API Requirements The event planner uses: Google Places API (New): Required for venue search Google Directions API: Optional but recommended for accurate travel times Both APIs can use the same GOOGLEPLACESAPIKEY if enabled in Google Cloud Console. …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills sundial-org/event-planner

View the source on GitHub

Browse the @skills marketplace