agentleFS
wxxb789wxxb789/hoa/skills/find-nearby/SKILL.md

find-nearby

Skill3 starsChanged 53 days agoMITView on GitHub

Find what is near a place with the bundled script: category search, distance sorting and a compact result list, without opening a map. Use when asked what is around an address, which option is closest, or for a shortlist of nearby places. Not for route planning or for reviewing a place in depth.

4 other projects use a version of this, 4 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 1 is common, 0 are distinctive, and 1 is very specific to this project.

  • 1

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Get the location: Look for coordinates (latitude: ...

    line 60
  2. Common:

    If results are sparse, widen the radius (1500 → 3000m)

    line 72

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

FlagDescriptionDefault
--lat, --lonExact coordinates—
--nearAddress, city, zip, or landmark (geocoded)—
--typePlace type (repeatable for multiple)restaurant
--radiusSearch radius in meters1500
--limitMax results15
--jsonMachine-readable JSON outputoff

Common Place Types

restaurant, cafe, bar, pub, fast_food, pharmacy, hospital, bank, atm, fuel, parking, supermarket, convenience, hotel

Workflow

  1. Get the location. Look for coordinates (latitude: ... / longitude: ...) from a Telegram pin, or ask the user for an address/city/zip.
  2. Ask for preferences (only if not already stated): place type, how far they're willing to go, any specifics (cuisine, "open now", etc.).
  3. Run the script with appropriate flags. Use --json if you need to process results programmatically.
  4. 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.
  5. For directions, use the directions_url from 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 hours field in results, cross-reference with web_search for 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.