helix4u/find-nearby
skills/leisure/find-nearby/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add helix4u/hermes-agent find-nearbyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 27, 2026, 11:24 PM154.6s1 file scanned
SKILL.md
- name:
- find-nearby
- description:
- 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.
- version:
- 1.0.0
- tags:
- [location, maps, nearby, places, restaurants, local]
- related_skills:
- []
Find Nearby — Local Place Discovery
Find restaurants, cafes, bars, pharmacies, and other places near any location. Uses OpenStreetMap (free, no API keys). Works with:
- Coordinates from Telegram location pins (latitude/longitude in conversation)
- Addresses ("near 123 Main St, Springfield")
- Cities ("restaurants in downtown Austin")
- Zip codes ("pharmacies near 90210")
- Landmarks ("cafes near Times Square")
Quick Reference
# 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
Parameters
| 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 |
Common Place Types
restaurant, cafe, bar, pub, fast_food, pharmacy, hospital, bank, atm, fuel, parking, supermarket, convenience, hotel
Workflow
-
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
--jsonif 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
hoursfield in results — if missing or unclear, verify withweb_search. -
For directions, use the
directions_urlfrom results, or construct:https://www.google.com/maps/dir/?api=1&origin=<LAT>,<LON>&destination=<LAT>,<LON>
Tips
- If results are sparse, widen the radius (1500 → 3000m)
- For "open now" requests: check the
hoursfield in results, cross-reference withweb_searchfor accuracy since OSM hours aren't always complete - Zip codes alone can be ambiguous globally — prompt the user for country/state if results look wrong
- The script uses OpenStreetMap data which is community-maintained; coverage varies by region
Related Skills
helix4u/writing-plans
development
VerifiedTrustedCommunity
Use when you have a spec or requirements for a multi-step task. Creates comprehensive implementation plans with bite-sized tasks, exact file paths, and complete code examples.
4SKILL.mdUpdated Apr 18, 2026
helix4u/test-driven-development
development
VerifiedTrustedCommunity
Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle with test-first approach.
4SKILL.mdUpdated Apr 18, 2026
helix4u/systematic-debugging
development
VerifiedTrustedCommunity
Use when encountering any bug, test failure, or unexpected behavior. 4-phase root cause investigation — NO fixes without understanding the problem first.
4SKILL.mdUpdated Apr 18, 2026
helix4u/subagent-driven-development
development
VerifiedTrustedCommunity
Use when executing implementation plans with independent tasks. Dispatches fresh delegate_task per task with two-stage review (spec compliance then code quality).
4SKILL.mdUpdated Apr 18, 2026