venue-watch
Monitor your favorite venues and artists for upcoming events
What this skill does
# Venue Watch Skill
Monitor your favorite venues and artists for upcoming events.
## Usage
- `/venue-watch` - Check all watched venues for upcoming events
- `/venue-watch add [name]` - Add a venue to watchlist
- `/venue-watch add-artist [name]` - Add an artist to watchlist
- `/venue-watch remove [slug]` - Remove venue from watchlist
- `/venue-watch remove-artist [name]` - Remove artist from watchlist
- `/venue-watch list` - Show current watchlist
## Data Files
- **Watchlist**: `data/watchlist.json` — venues and artists being monitored
- **Venue DB**: `data/venues.json` — full venue database with metadata
## Workflow
### Step 0: Setup Check
Read `data/preferences.json`. If `metadata.setup_complete` is false, say:
> "Run `/date-plan setup` first to set your city and preferences!"
### `/venue-watch` — Check for Events
1. Read `data/watchlist.json` for watched venues and artists
2. Read `data/venues.json` for venue metadata
3. Read city from `data/preferences.json`
4. **For each watched venue with a ticketmaster_venue_id** (if Ticketmaster API available):
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/fetch_events.py --venue <slug> --days 30 --format json
```
5. **For watched venues WITHOUT Ticketmaster ID:**
WebSearch: "[venue name] [city] upcoming shows schedule"
6. **For watched artists:**
- WebSearch: "[artist name] concert [city] 2026"
- If Ticketmaster available: `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/fetch_events.py --city "{city}" --artist "<name>" --format json`
7. Display results grouped by venue:
```
## Venue Watch Report
*Last checked: [date]*
### [Venue Name] (category)
1. **[Event]** — [Date] — $XX-XX — [Tickets](url)
2. **[Event]** — [Date] — $XX-XX — [Tickets](url)
### [Venue Name] (category)
No upcoming events found. Check website: [url]
---
### Artist Alerts
No watched artists currently. Add with `/venue-watch add-artist [name]`
```
### `/venue-watch add [name]` — Add a Venue
This is the key flow that builds the venue database organically:
1. Read `data/venues.json` — check if venue already exists (match on name)
2. If not found, **discover the venue via WebSearch**:
- WebSearch: "[name] [city] venue"
- Extract: name, address, neighborhood, category, website
3. Create a venue entry:
```json
{
"slug": "name-slugified",
"name": "Full Venue Name",
"category": "music|comedy|theater|museum|food",
"subcategory": "",
"neighborhood": "Neighborhood",
"address": "Address",
"website": "URL",
"ticketing_platform": "ticketmaster|axs|direct",
"ticketmaster_venue_id": null,
"notes": ""
}
```
4. Add to `data/venues.json`
5. Add slug to `data/watchlist.json` `watched_venues`
6. If Ticketmaster API available, search for venue ID:
```bash
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/fetch_venues.py --venue "[name]"
```
Update the entry if found.
7. Confirm: "Added **[Venue Name]** to your watchlist! ([category], [neighborhood])"
8. Git commit: `git add data/venues.json data/watchlist.json && git commit -m "date-planner: watch [venue-name]"`
### `/venue-watch add-artist [name]`
1. Add to `data/watchlist.json` `watched_artists` array
2. Immediately search:
- WebSearch: "[artist name] concert [city] 2026 tour dates"
- If Ticketmaster available: `python3 ${CLAUDE_PLUGIN_ROOT}/scripts/fetch_events.py --city "{city}" --artist "<name>" --format json`
3. Show results or: "No upcoming dates for [artist] in [city]. I'll flag them when they're announced."
4. Git commit
### `/venue-watch remove [slug]`
1. Remove from `data/watchlist.json` `watched_venues`
2. Confirm and git commit
### `/venue-watch remove-artist [name]`
1. Remove from `data/watchlist.json` `watched_artists`
2. Confirm and git commit
### `/venue-watch list`
Display current watchlist with venue details:
```
## Your Watchlist
### Venues ([count])
**Music:**
- [Venue Name] ([subcategory], [neighborhood])
**Comedy:**
- [Venue Name] ([neighborhood])
**Museums:**
- [Venue Name] ([neighborhood])
### Artists ([count])
- [Artist Name]
---
*[N] venues in database total. Add more with `/venue-watch add [name]`*
```
## Notes
- Ticketmaster API: 5000 calls/day limit. Checking venues = 1 call each.
- Comedy venues often don't have Ticketmaster listings → WebSearch fills the gap
- Museums don't have "events" in Ticketmaster → WebSearch for exhibitions
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.