Results for “location-tracking”

Track and visualize ML training experiments with Trackio, including logging metrics, firing alerts, and retrieving data via CLI. Supports real-time dashboards, webhook alerts, and HF Space syncing.

Location intelligence — geocode a place, reverse-geocode coordinates, find nearby places (44 POI categories), driving/walking/cycling distance + time, turn-by-turn directions, timezone lookup, bounding box + area for a named place, and POI search within a rectangle. Uses OpenStreetMap + Overpass + OSRM. Free, no API key.

User Request

Progress Tracking

Search for places (restaurants, cafes, etc.) via Google Places API proxy on localhost.

Track Apple devices and AirTags via FindMy.app on macOS using AppleScript and screen capture.

Audit server-side paid-media measurement, including tag management, conversion APIs, event taxonomy, deduplication, consent, hashing, data quality, and observability.

Set up, audit, and debug analytics tracking implementations including GA4, Google Tag Manager, event taxonomy, and conversion tracking.

从本地成本追踪数据库追踪并报告 Claude Code 的 Token 用量、花费与预算

Track Apple devices/AirTags via FindMy.app on macOS.

Implementation and taxonomy skill for analytics tracking — event naming, properties, tracking plans, GA4/GTM/Amplitude setup, and debugging. Use this for the "how do we actually wire this up" layer, not the "what should we measure and why" layer (that's `product-analytics` — use this skill alongside it, after the metrics/tracking-plan decisions are made). Use this — without waiting to be asked — whenever the user mentions "set up tracking," "GA4," "Google Analytics," "Amplitude," "event tracking," "UTM parameters," "tag manager," "GTM," "tracking plan," "event taxonomy," "are my events firing," "why isn't this event showing up," "naming convention for events," or "instrument this feature." Produces a concrete tracking plan (event names, properties, triggers) plus implementation and debugging steps for the tools actually in use.

Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.

Configure, deploy, and manage Senpi Trading Runtime (OpenClaw plugin @senpi-ai/runtime) for automated on-chain position tracking with DSL trailing stop-loss protection. Use when a user needs to create or modify runtime YAML files, configure DSL (Dynamic Stop-Loss) exit engine parameters (phases, tiers, time-based cuts), set up the position_tracker scanner to monitor a wallet's positions on Hyperliquid, install/list/delete runtimes via CLI, or inspect DSL-tracked positions. The runtime does NOT create strategy wallets; create/get the strategy wallet via Senpi MCP first, then link that existing wallet in runtime YAML. Triggers on mentions of senpi, Senpi runtime, DSL exit, stop-loss tiers, position tracker, trailing stop, openclaw senpi, dsl_preset, or strategy YAML configuration."

Geocode places, find nearby points of interest, calculate routes and travel times, and look up timezones using free OpenStreetMap, OSRM, and TimeAPI.io data sources.

Set up, audit, and improve analytics tracking so marketing data is trustworthy.

Tracks crypto and AI narratives with mindshare scores, velocity arrows, phase labels, named drivers, and position calls. Detects phase transitions and reflexivity signals.

Tracks RSS/Atom feeds and blogs using blogwatcher-cli, with feed discovery, HTML scraping fallback, OPML import, and read/unread article management.

Track ML experiments with automatic logging, visualize training in real-time, optimize hyperparameters with sweeps, and manage model registry with W&B.

Tracks team OKRs with quarter banner, objective columns, key result progress bars, owner avatars, and status pills.

Track Apple devices and AirTags via FindMy.app on macOS using AppleScript and screen capture.

Track Apple devices/AirTags via FindMy.app on macOS.

Implements user analytics and event tracking in Flutter apps using Firebase Analytics, Mixpanel, and Amplitude, including event definitions, user properties, and e-commerce events.

Geocode, POIs, routes, timezones via OpenStreetMap/OSRM.

Find adjacent vendors and subs (not top market primes) who fill a capability gap against a displacement target using USASpending flows and SAM entity signals. Use when user defines a teaming gap and wants vault-ready partner shortlist with citations.

Track ML experiments with open-source run logging, local or self-hosted dashboards, and media visualization using SwanLab.

LLM observability with Langfuse — tracing, evals, prompt management, cost tracking

Tracks DeFi positions across DEX pools, lending markets, and vaults, alerting only on meaningful changes like APR drops, utilization spikes, or health factor approaching liquidation.

Set up, improve, or audit analytics tracking and measurement for marketing and product decisions.

Design privacy-aware observability for AI agents using traces, spans, structured events, metrics, cost attribution, dashboards, alerts, and investigation workflows. Use when instrumenting an agent, debugging intermittent tool or model failures, defining service-level objectives, analyzing latency or spend, auditing agent decisions, or preparing production monitoring.

Finds all places matching a query within a radius using grid-based Google Places scanning, with options for ratings, reviews, and map export.

Track stocks, ETFs, indices, crypto (where available), and FX pairs with caching + provider fallbacks.

Track code changes with structured JSON records, an enforced state machine, and a session handoff format for AI continuity.

Finds all places matching a query within a radius using grid-based Google Places scanning, with options to filter by rating, reviews, and open status, and export results to JSON, CSV, or an interactive map.

Append structured execution traces across operational, cognitive, and contextual surfaces with minimal overhead. Load when inspecting agent runs, logging tool calls and observations, enabling post-run debugging, or pairing with structured-planning step IDs. Also triggers on "trace this run", "log execution", "agent observability", "run log", or when fault-localize needs evidence. Default-on during multi-step plans. Traces live at .agent-loom/traces/ — git-ignored by default.

Track flight status, delays, and search routes. Uses FlightAware data.