Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Location awareness via privacy-friendly GPS tracking (Home Assistant, OwnTracks, GPS Logger). Set location-based reminders and ask about movement history, travel time, and nearby POIs.
Location awareness via privacy-friendly GPS tracking (Home Assistant, OwnTracks, GPS Logger). Set location-based reminders and ask about movement history, travel time, and nearby POIs.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This skill provides commands to execute. When the user asks about location, RUN the appropriate command below.
Every command must be run via scripts/location.sh. Example: User asks: "How long to walk home?" You run: scripts/location.sh eta home --mode walk Output: 4.6 km, about 45 min walk You reply with the output directly. Do NOT run eta or other subcommands directly β they don't exist as standalone commands.
User saysRun this (copy exactly)Reply with"Where am I?"scripts/location.sh statusZone name only"Map" / "map link"scripts/location.sh herewegoJust the URL"What are my coordinates?"scripts/location.sh statusLat/lon from output"How long to walk home?"scripts/location.sh eta home --mode walkDistance + duration"How long to bike to X?"scripts/location.sh eta X --mode bikeDistance + duration"How far is X by car?"scripts/location.sh eta X --mode carDistance + duration"Remind me to X when I get to Y"scripts/location.sh remind "X" YBrief confirm"What reminders do I have?"scripts/location.sh remindersBullet list or "None""List my places"scripts/location.sh placesBullet list"List places nearby"scripts/location.sh places --nearSorted by distance"List my pubs downtown"scripts/location.sh places --region downtown --category pubFiltered list"Save this spot as X"scripts/location.sh addplace "X"Confirm"Delete place X"scripts/location.sh delplace XConfirm"Disable the grocery rule"scripts/location.sh disable groceryConfirm"List my geofence rules"scripts/location.sh geofencesBullet list"When was I last at X?"scripts/location.sh history XDate/time"Where have I been today?"scripts/location.sh history --days 1List of places"Find me a cafe nearby"scripts/location.sh nearby cafePOI list with distances"Any pubs within 1km?"scripts/location.sh nearby pub 1000Filtered POI list"How long was I at work this week?"scripts/location.sh stats --days 7Hours per place Response style: Terse. No preamble. No "Here's your location:". Just the answer.
All via scripts/location.sh <command>: CommandDescriptionstatusCurrent location, geofences inside, map linkherewegoJust the HERE WeGo map linkcheckCheck for triggered actions/reminders (used by cron)places [--near] [--region R] [--category C]List saved placesgeofencesList all geofences with full detailsremind <text> <place_id>Add one-shot location reminderremindersList pending remindersaddplace <name> [radius] [--region R] [--category C]Save current locationeditplace <id> [--name] [--radius] [--region] [--category] [--action] [--cooldown]Modify a placedelplace <id>Delete a placeenable <id> / disable <id>Toggle geofence on/offhistory [place] [--days N]When was I last at a place?nearby <category> [radius]Find nearby POIs (cafe, pub, restaurant, etc.)stats [--days N]Time spent at each place, visit countsproximity <text> <place/lat> [lon] [radius]Alert when approaching a locationeta <place> [--mode walk|bike|car]Travel time and distance to a place Note: eta accepts saved place names, coordinates (lat,lon), or any place name (geocoded via OpenStreetMap, biased to current location). Note: status returns the zone name if in a known place, otherwise reverse geocodes to a street address (e.g., "123 Main Street, Downtown").
Geofences β Saved places with lat/lon, radius, and optional action. Persistent. Reminders β One-shot alerts tied to a place. Deleted after delivery. Region/Category β Optional tags for filtering (e.g., "downtown", "pub").
Edit scripts/config.json: Home Assistant (default): { "provider": "homeassistant", "homeassistant": { "url": "https://your-ha.example.com", "token": "your-long-lived-token", "entity_id": "device_tracker.phone" } } OwnTracks: { "provider": "owntracks", "owntracks": { "url": "https://owntracks.example.com", "user": "username", "device": "phone" } } Generic HTTP: { "provider": "http", "http": { "url": "https://your-api.com/location", "headers": {"Authorization": "Bearer token"} } } GPSLogger (file-based): { "provider": "gpslogger", "gpslogger": { "file": "/path/to/location.json" } } Secrets support: "env:VAR_NAME" (reads from environment variable) or plain string. Alternative: Configure entirely via environment variables (no config.json needed): ProviderEnv variablesLOCATION_PROVIDERhomeassistant, owntracks, http, or gpslogger (default: homeassistant)Home AssistantHA_URL, HA_TOKEN, HA_ENTITY_IDOwnTracksOWNTRACKS_URL, OWNTRACKS_USER, OWNTRACKS_DEVICE, OWNTRACKS_TOKENHTTPLOCATION_HTTP_URLGPSLoggerGPSLOGGER_FILE Env vars take precedence over config.json values. Set them in ~/.openclaw/.env or your shell environment. Output format: Most query commands output human-readable text by default. Add --json for JSON output (useful for scripting).
Customize walking/biking speeds for ETA calculations in scripts/config.json: { "speeds_kmh": { "walk": 6, "bike": 15 } }
Edit scripts/geofences.json: { "geofences": [ { "id": "grocery", "name": "Grocery Store", "lat": 40.7128, "lon": -74.0060, "radius_m": 30, "action": "shopping_tasks", "cooldown_hours": 4, "enabled": true, "region": "downtown", "category": "shop" } ], "location_reminders": [], "proximity_alerts": [] }
Use OpenClaw's built-in cron to run periodic location checks. Add a job to ~/.openclaw/cron/jobs.json: { "name": "Location Check", "schedule": "*/5 * * * *", "prompt": "Run scripts/location.sh check --json and notify me of any triggered actions, reminders, or proximity alerts.", "channel": "signal", "to": "+1234567890", "wakeMode": "now" } This keeps scheduling within OpenClaw rather than requiring external systemd services.
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.