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
- ashleysbrain/skillsedited, first seen Nov 8, 2026
- RedWoodOG/Hermes-Desktopedited, first seen Oct 8, 2026
- math-inc/OpenGaussedited, first seen Oct 8, 2026
- Martin-Hausleitner/martins-awesome-skillsedited, first seen May 24, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 4
- math-inc/OpenGauss★ 1.3k89% same
- RedWoodOG/Hermes-Desktop★ 17789% same
- Martin-Hausleitner/martins-awesome-skills★ 389% same
- ashleysbrain/skills★ 189% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- agent-harness-settings-paritySkill
- agent-operating-contract-evolutionSkill
- ai-coding-agent-delegationSkill
- arch-improvement-planSkill
- contract-bound-deliverablesSkill
- cross-agent-repair-routingSkill
- define-goalSkill
- delegated-work-acceptanceSkill
- design-an-interfaceSkill
- design-mdSkill
- discord-rich-messageSkill
- dotnet-repo-workflowSkill
- evidence-backed-analytical-writingSkill
- evidence-boundary-disciplineSkill
- gddSkill
- generated-runtime-repairsSkill
- ghc-searchSkill
- git-auto-sync-pipelinesSkill
- github-code-reviewSkill
- github-repo-managementSkill
- grounded-citationsSkill
- harness-engineeringSkill
- hermes-context-file-loadingSkill
- hermes-modelsSkill
- hermes-updatesSkill
- hoa-introspect-distillSkill
- hoa-introspectSkill
- hoa-skill-reviewSkill
- hoa-skill-workSkill
- html-artifactSkill
- jupyter-live-kernelSkill
- kanban-workflowsSkill
- m365-copilot-cdpSkill
- measurement-campaign-evidenceSkill
- microsoft-officeSkill
- notes-to-prdSkill
- ocr-and-documentsSkill
- official-document-verificationSkill
- omp-headless-orchestrationSkill
- ops-claim-verificationSkill
- package-release-verificationSkill
- plan-to-issuesSkill
- project-phase-closeoutSkill
- report-claim-auditSkill
- research-stream-consolidationSkill
- review-revision-candidatesSkill
- rss-feedsSkill
- skill-library-curationSkill
- skill-porting-and-publishingSkill
- spec-convergenceSkill
- structural-validity-gatesSkill
- subagent-driven-developmentSkill
- systematic-debuggingSkill
- teams-cdpSkill
- tmux-agent-controlSkill
- whisperSkill
- writing-plansSkill
- writingSkill
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
- Very specific: line 60
Get the location: Look for coordinates (latitude: ...
- Common: line 72
If results are sparse, widen the radius (1500 → 3000m)
“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.
Files
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 --jsonParameters
| 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
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
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.

