🤖 docs: clarify goplaces directions + nearby usage

What:
- add guidance for closest-place queries
- document directions via Google Maps links (not Routes API)

Why:
- make behavior explicit for “closest X” and A→B requests
- avoid misleading ETA/distance guesses

Tests:
- go test ./...

tools/goplaces/skills/goplaces/SKILL.md

@@ -24,6 +24,20 @@ Common commands
 - Details: `goplaces details <place_id> --reviews`
 - JSON: `goplaces search "sushi" --json`
 
+Closest place to me
+- Get coordinates (prefer device location; otherwise ask for a location).
+- Use nearby search with a tight radius and limit:
+  - `goplaces nearby --lat <lat> --lng <lng> --radius-m 2000 --type cafe --limit 5`
+- Pick the top result as the closest match unless distance is explicitly returned in output.
+
+Directions (A → B)
+- goplaces does NOT provide directions or ETA between two points.
+- `goplaces route` finds places along a route (Routes API) — not a directions/ETA tool.
+- For directions, generate a Google Maps link (no guessing):
+  - Coordinates: `https://www.google.com/maps/dir/?api=1&origin=<lat>,<lng>&destination=<lat>,<lng>`
+  - Place IDs: `https://www.google.com/maps/dir/?api=1&origin_place_id=<id>&destination_place_id=<id>`
+- If the user asks for time/distance, provide the link and ask them to open it.
+
 Notes
 - `--no-color` or `NO_COLOR` disables ANSI color.
 - Price levels: 0..4 (free → very expensive).