Find interesting art and food events in Berlin. Use when the user asks 'What events are happening in Berlin this week?' or 'Find me art exhibitions and food festivals in Berlin next weekend.' Ingest event sources into qurl, run semantic search, check against Google Calendar for conflicts, and produce a curated list of relevant events with location context.
Ingest Berlin event sources into qurl, run semantic search, check Google Calendar for conflicts, and produce a curated, relevance-ranked list.
Check .claude/berlin-events.local.md in the current project root first, then fall back to ~/.claude/berlin-events.local.md. Extract:
If no settings file exists, assume defaults: neighborhood=Mitte, interests=art+food, calendar=primary, lookahead=14 days.
Parse the optional argument for date range:
Calculate exact dates using today's date. Only include future events.
Scrape each priority source and ingest it into the local qurl database. Run in parallel where possible.
PLUGIN_ROOT="${CLAUDE_PLUGIN_ROOT:-plugins/berlin-events}"
ingest() {
local url="$1" tags="$2"
bun run "$PLUGIN_ROOT/scripts/extract-content.js" "$url" \
| qurl add "$url" --source berlin-events --tags "$tags"
}
# Art sources
ingest "https://www.indexberlin.com/events/list/" "art"
ingest "https://www.kw-berlin.de/en/events" "art"
ingest "https://berlinischegalerie.de/programme/kalender/" "art"
ingest "https://www.artatberlin.com/en/calendar-for-vernissagen-exhibitions-events/" "art"
ingest "https://co-berlin.org/de/programm/kalender" "art"
ingest "https://kunstleben-berlin.de/events/" "art"
# Food / broad sources
ingest "https://www.berlin.de/en/events/" "food"
ingest "https://www.visitberlin.de/en/event-calendar-berlin" "art,food"
qurl deduplicates by URL + content hash — re-running is safe.
Generate vector embeddings for any newly ingested documents:
qurl embed
Build a query from the user's settings and run semantic search:
# Build query from interests + neighborhood + current month
QUERY="$(date '+%B %Y') Berlin exhibition opening vernissage workshop event calendar art food"
qurl vsearch "$QUERY" \
--source berlin-events \
--limit 20
Relevance filter — a result counts as relevant if its snippet contains any of:
april, may, monday–sunday, vernissage, opening, exhibition, finissageausstellung, veranstaltung, führung, kalender, programm.04., .05. (adjust for current month)If vsearch returns fewer than 5 relevant results, fall back to web search (Step 5b).
"Berlin art events this week [date range]"
"Berlin food events this week [date range]"
"Berlin exhibition openings [date range]"
Check for scheduling conflicts:
gcalcli agenda --nocolor --details end "today" "+14 days"
If gcalcli is not installed: pip3 install gcalcli. If not authenticated, ask the user to run ! gcalcli agenda to complete OAuth.
Parse output to identify busy time slots. Flag events that overlap with existing entries.
For each event, note the neighborhood (e.g., "Kreuzberg", "Mitte", "Charlottenburg") and compare with the user's neighborhood:
Use general Berlin geography knowledge. Do not call external routing APIs.
Score events by:
Output a curated list grouped by date:
## [Day, Date]
### [Event Name]
- **What**: [Brief description]
- **Where**: [Venue, Neighborhood] — [travel context from your location]
- **When**: [Time]
- **Category**: Art | Food
- **Link**: [URL]
- **Calendar conflict**: None | "Conflicts with [existing event] at [time]"
- **Add to calendar**: [gcalcli command or Google Calendar link]
---
Google Calendar link format (compact ISO 8601 dates: YYYYMMDDTHHmmssZ):