القائمة
Check Potato's Fi collar GPS location, battery, and connection status. Use when asked where Potato is, collar battery level, or whether Potato is at Crosstown or the Cabin.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Read upcoming OpenTable reservations or handle attended ad-hoc OpenTable availability and exact-approval booking. Use for OpenTable account reads, attended restaurant searches, or a user-confirmed one-off reservation; route canonical recurring date-night, double-date, and quarterly-group jobs to the restaurant-book skill instead.
Stage tightly scoped background reservation monitoring for OpenTable or Resy after explicit bounded preauthorization. Resy may auto-book after approval; OpenTable remains notification-only until this runtime adapter integrates the deployed live reservations reader. Not for one-shot search, attended booking, or cancellation.
Search Resy, inspect availability, and handle attended ad-hoc Resy booking. Route canonical recurring date-night, double-date, and quarterly-dinner jobs to restaurant-book, and use restaurant-snipe only for bounded cancellation monitoring. Never use this skill for unattended cancellation.
Safely plan or execute a canonical standing-authorized restaurant cron scope across both Resy and OpenTable. Use only for the tracked date-night, double-date, and quarterly-dinner jobs; use the provider skills for attended ad-hoc work and restaurant-snipe for bounded monitoring.
Safely use exact 1Password fields during attended interactive work and maintain the protected OpenClaw secrets cache. Use for passwords, API keys, credentials, payment data, cache refreshes, or diagnosing credential access. Never use `op` from a LaunchAgent or any child process it starts.
Diagnose and fix 1Password CLI hangs or repeated TCC prompts in macOS LaunchAgent and other unattended contexts by converting the complete process tree to a protected cache-only credential contract.
| name | fi-collar |
| description | Check Potato's Fi collar GPS location, battery, and connection status. Use when asked where Potato is, collar battery level, or whether Potato is at Crosstown or the Cabin. |
| allowed-tools | Bash(fi-collar:*) |
| metadata | {"openclaw":{"emoji":"F","requires":{"bins":["fi-collar"]}}} |
Check Potato's real-time GPS location, battery, and connection status via the Fi Series 3+ collar API.
fi-collar location
Returns JSON with GPS coordinates, nearest known location (crosstown/cabin), distance, and whether Potato is within the home geofence.
fi-collar status
Returns JSON with location + battery level, connection type (Base/User/Cellular), activity type (Rest/Walk), and Fi base station status.
fi-collar walk-path
Returns the dense GPS polyline from Fi's OngoingWalk — timestamped positions and path points. Returns {"walking": false} if not currently on a walk.
fi-collar set-mode NORMAL # standard GPS (~3-7min updates)
fi-collar set-mode LOST_DOG # high-frequency GPS (~15-30s updates)
LOST_DOG mode drains battery faster — used automatically by the dog walk listener during walks, then reset to NORMAL on return.
fi-collar login
{
"name": "Potato",
"activity": "Rest",
"latitude": ${CABIN_LAT},
"longitude": ${CABIN_LON},
"location": "cabin",
"distance_m": 26,
"at_location": true,
"battery": 97,
"connection": "User",
"connectionDetail": "Dylan",
"place": "Philly",
"address": "[private address]"
}
Fi GPS is polled every 60s during dog walk return monitoring. When Potato re-enters the home geofence, Roombas are docked automatically. This works at both Crosstown and Cabin locations.
${TRYFI_EMAIL} (password in TRYFI_PASSWORD env var)~/.config/fi-collar/session.json (12hr TTL, auto-re-login on 401)TRYFI_EMAIL + TRYFI_PASSWORD in ~/.openclaw/.secrets-cache${TRYFI_COLLAR_SERIAL}${TRYFI_PET_ID}Home locations loaded from env vars (CROSSTOWN_LAT/LON, CABIN_LAT/LON in secrets-cache):