Help us improve
Share bugs, ideas, or general feedback.
From leisure-skills
Find nearby places (restaurants, cafes, bars, pharmacies, etc.) using OpenStreetMap. Works with coordinates, addresses, cities, zip codes, or Telegram location pins. No API keys needed.
npx claudepluginhub rnben/hermes-skills --plugin leisure-skillsHow this skill is triggered — by the user, by Claude, or both
Slash command
/leisure-skills:find-nearbyThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Find restaurants, cafes, bars, pharmacies, and other places near any location. Uses OpenStreetMap (free, no API keys). Works with:
Applies 10 pre-set color/font themes or generates custom ones for slides, documents, reports, and HTML landing pages.
Share bugs, ideas, or general feedback.
Find restaurants, cafes, bars, pharmacies, and other places near any location. Uses OpenStreetMap (free, no API keys). Works with:
# By coordinates (from Telegram location pin or user-provided)
python3 SKILL_DIR/scripts/find_nearby.py --lat <LAT> --lon <LON> --type restaurant --radius 1500
# By address, city, or landmark (auto-geocoded)
python3 SKILL_DIR/scripts/find_nearby.py --near "Times Square, New York" --type cafe
# Multiple place types
python3 SKILL_DIR/scripts/find_nearby.py --near "downtown austin" --type restaurant --type bar --limit 10
# JSON output
python3 SKILL_DIR/scripts/find_nearby.py --near "90210" --type pharmacy --json
| Flag | Description | Default |
|---|---|---|
--lat, --lon | Exact coordinates | — |
--near | Address, city, zip, or landmark (geocoded) | — |
--type | Place type (repeatable for multiple) | restaurant |
--radius | Search radius in meters | 1500 |
--limit | Max results | 15 |
--json | Machine-readable JSON output | off |
restaurant, cafe, bar, pub, fast_food, pharmacy, hospital, bank, atm, fuel, parking, supermarket, convenience, hotel
Get the location. Look for coordinates (latitude: ... / longitude: ...) from a Telegram pin, or ask the user for an address/city/zip.
Ask for preferences (only if not already stated): place type, how far they're willing to go, any specifics (cuisine, "open now", etc.).
Run the script with appropriate flags. Use --json if you need to process results programmatically.
Present results with names, distances, and Google Maps links. If the user asked about hours or "open now," check the hours field in results — if missing or unclear, verify with web_search.
For directions, use the directions_url from results, or construct: https://www.google.com/maps/dir/?api=1&origin=<LAT>,<LON>&destination=<LAT>,<LON>
hours field in results, cross-reference with web_search for accuracy since OSM hours aren't always complete