npx claudepluginhub tonyyont/date-planner --plugin date-plannerThis skill uses the workspace's default tool permissions.
Monitor your favorite venues and artists for upcoming events.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Analyzes competition with Porter's Five Forces, Blue Ocean Strategy, and positioning maps to identify differentiation opportunities and market positioning for startups and pitches.
Monitor your favorite venues and artists for upcoming events.
/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 watchlistdata/watchlist.json — venues and artists being monitoreddata/venues.json — full venue database with metadataRead data/preferences.json. If metadata.setup_complete is false, say:
"Run
/date-plan setupfirst to set your city and preferences!"
/venue-watch — Check for EventsRead data/watchlist.json for watched venues and artists
Read data/venues.json for venue metadata
Read city from data/preferences.json
For each watched venue with a ticketmaster_venue_id (if Ticketmaster API available):
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/fetch_events.py --venue <slug> --days 30 --format json
For watched venues WITHOUT Ticketmaster ID: WebSearch: "[venue name] [city] upcoming shows schedule"
For watched artists:
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/fetch_events.py --city "{city}" --artist "<name>" --format jsonDisplay 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 VenueThis is the key flow that builds the venue database organically:
data/venues.json — check if venue already exists (match on name){
"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": ""
}
data/venues.jsondata/watchlist.json watched_venuespython3 ${CLAUDE_PLUGIN_ROOT}/scripts/fetch_venues.py --venue "[name]"
Update the entry if found.git add data/venues.json data/watchlist.json && git commit -m "date-planner: watch [venue-name]"/venue-watch add-artist [name]data/watchlist.json watched_artists arraypython3 ${CLAUDE_PLUGIN_ROOT}/scripts/fetch_events.py --city "{city}" --artist "<name>" --format json/venue-watch remove [slug]data/watchlist.json watched_venues/venue-watch remove-artist [name]data/watchlist.json watched_artists/venue-watch listDisplay 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]`*