Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Fetch upcoming events from Luma (lu.ma) for any city. Use when the user asks about tech events, startup meetups, networking events, conferences, or things happening in cities like Bangalore, Mumbai, Delhi, San Francisco, New York, etc.
Fetch upcoming events from Luma (lu.ma) for any city. Use when the user asks about tech events, startup meetups, networking events, conferences, or things happening in cities like Bangalore, Mumbai, Delhi, San Francisco, New York, etc.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Fetch structured event data from Luma (lu.ma) without authentication. Luma is a popular platform for tech meetups, startup events, conferences, and community gatherings.
Luma is a Next.js SSR app. All event data is embedded in the HTML as JSON inside a <script id="__NEXT_DATA__"> tag. The Python script extracts this data - no API key needed.
python3 scripts/fetch_events.py bengaluru mumbai --days 14
python3 scripts/fetch_events.py <city> [cities...] [--days N] [--max N] [--json]
city: City slug (bengaluru, mumbai, delhi, san-francisco, new-york, london, etc.) --days N: Only show events within N days (default: 30) --max N: Maximum events per city (default: 20) --json: Output raw JSON instead of formatted text
India: bengaluru, mumbai, delhi, hyderabad, pune USA: san-francisco, new-york, austin, seattle, boston Global: london, singapore, dubai, toronto, sydney
============================================================ ๐ BENGALURU โ 5 events ============================================================ ๐ฏ AI Engineers Day with OpenAI ๐ Whitefield, Bengaluru ๐ Jan 31, 2026 10:30 AM IST ๐ฅ OpenAI, Google AI ๐ค 1411 going ๐ซ Available (150 spots) ๐ https://lu.ma/57tarlkp ๐ฏ Startup Fundraising Masterclass ๐ Koramangala, Bengaluru ๐ Feb 02, 2026 06:00 PM IST ๐ข Free (50 spots) ๐ https://lu.ma/startup-funding
[ { "city": "bengaluru", "count": 5, "events": [ { "event": { "name": "AI Engineers Day", "start_at": "2026-01-31T05:00:00.000Z", "end_at": "2026-01-31T12:30:00.000Z", "url": "57tarlkp", "geo_address_info": { "city": "Bengaluru", "address": "Whitefield", "full_address": "..." } }, "hosts": [{"name": "OpenAI", "linkedin_handle": "/company/openai"}], "guest_count": 1411, "ticket_info": { "is_free": false, "is_sold_out": false, "spots_remaining": 150 } } ] } ]
Always save fetched events to ~/clawd/memory/luma-events.json for future reference. This allows you to: Answer questions about events without repeated fetches Track which events the user is interested in Compare events across cities Build context about upcoming plans When to save: After fetching events for any city Merge with existing data (by event URL) Keep events for next 60 days only Add lastFetched timestamp Format: [ { "city": "bengaluru", "name": "AI Engineers Day", "start": "2026-01-31T05:00:00.000Z", "end": "2026-01-31T12:30:00.000Z", "url": "https://lu.ma/57tarlkp", "venue": "Whitefield, Bengaluru", "hosts": ["OpenAI", "Google AI"], "guestCount": 1411, "ticketStatus": "available", "spotsRemaining": 150, "isFree": false, "lastFetched": "2026-01-29T12:54:00Z" } ]
python3 scripts/fetch_events.py bengaluru --days 7
python3 scripts/fetch_events.py bengaluru mumbai san-francisco --days 14 --json | jq '.[] | .events[] | select(.event.name | contains("AI"))'
python3 scripts/fetch_events.py new-york --max 5
User: "What tech events are happening in Bangalore this weekend?" โ Fetch Bengaluru events for next 7 days, save to memory User: "Any AI meetups in Mumbai next month?" โ Fetch Mumbai events for next 30 days, filter for AI-related, save to memory User: "Compare startup events in SF vs NYC" โ Fetch both cities, compare, save both to memory
No authentication: Luma event pages are public City slugs: Use lowercase, hyphenated slugs (san-francisco, not San Francisco) Rate limiting: Respectful fetching only (don't hammer the servers) Data freshness: Events are live data from the HTML, always current Timezone: Times are in the event's local timezone (extracted from start_at)
"Could not find NEXT_DATA" โ Luma changed their HTML structure, script needs updating "Unexpected data structure" โ The JSON path changed, check the latest HTML No events returned โ City slug might be wrong, or no upcoming events for that city Timeout errors โ Network issue, retry or check internet connection
Python 3.6+ (stdlib only - no external packages needed) urllib, json, re, argparse, datetime (all built-in)
Initial release Support for multiple cities Human-readable and JSON output Date filtering (--days) Event limit per city (--max) Event persistence to memory file
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Largest current source with strong distribution and engagement signals.