ClawTrust
7.7
/ 10
1 evaluations
2.3k Downloads
Overview
Connects to the Strava API to load a user’s activities, athlete profile, and aggregated stats so the AI can analyze workouts, training history, and fitness trends directly from live Strava data.
Key Advantages
1.Direct integration with Strava’s official API using OAuth tokens, enabling access to real user activity data (runs, rides, swims, etc.).
2.Supports key Strava endpoints: recent activities, activity details, athlete profile, and athlete statistics, plus pagination and date-based filtering.
3.Clear setup instructions for obtaining OAuth tokens and configuring them via environment variables or Clawdbot config, aligned with the OpenClaw/Clawhub ecosystem.
4.Exposes rich activity fields (distance, time, elevation, speed, heart rate, kudos, etc.) that the model can leverage for deeper analysis and coaching-style insights.
5.Includes guidance on handling token expiry and rate limits, with a helper script and manual curl examples to refresh tokens and manage API usage.
Use Cases
- Summarizing and analyzing a user’s recent Strava activities (e.g., past 10–30 workouts) to extract trends, highlights, or anomalies.
- Building custom training summaries, such as weekly or monthly distance, elevation gain, and time spent in different sports.
- Filtering activities over specific date ranges (e.g., last week, last month, pre-race block) to assess training load and consistency.
- Deep-diving into individual workouts (interval sessions, long runs/rides) using the activity details endpoint for performance review and feedback.
- Retrieving overall athlete profile and high-level stats to contextualize coaching advice or compare current vs. historical performance periods.
Evaluation Scores
7.7
/ 10
Reliability
7.4
Functionality
8.3
Usability
6.7
Safety
7.5
Performance
8.5
Compatibility
9.0
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
7.7/103/19/2026▼
OS: darwin-x64LLM: google/gemini-2.5-flash
**Quick judgment:**
A solid, technically oriented Strava integration that exposes key read-only endpoints (activities, stats, profile) for analysis within OpenClaw. Very useful for users comfortable with API tokens and basic configuration; less plug-and-play for non-technical users.
**Strengths**
- Good coverage of core Strava read endpoints (activities list, activity details, athlete profile, athlete stats, pagination, date filters).
- Well-aligned with Claw/Clawdbot configuration patterns (env vars or `~/.clawdbot/clawdbot.json`).
- Rich activity fields enable the AI to perform meaningful training and fitness analyses once data is loaded.
- Documentation includes token refresh guidance and rate-limit awareness.
**Key risks / limitations**
- **Privacy & sensitivity:** Accesses detailed personal fitness and potentially location data. Users must understand they are exposing their Strava data to the AI runtime; this may be sensitive in some contexts.
- **Token handling:** Requires manual OAuth setup and storage of access/refresh tokens. Misconfiguration (e.g., pasting tokens into prompts, committing them to repos) could leak credentials.
- **Rate limits & external dependency:** Bound by Strava’s API limits (200/15 min, 2000/day) and uptime; heavy or automated use could hit limits and cause intermittent failures.
- **Usability/technical barrier:** Setup and examples are curl- and shell-oriented, assuming comfort with environment variables, JSON config, and Unix tooling. Not as friendly for non-technical end users.
**Recommended scenarios**
- Fitness or coaching assistants that need **direct access to a user’s Strava history** to generate summaries, progress reports, or training insights.
- Data-driven athletes or developers wanting to **analyze training blocks, weekly load, or trends** via natural language queries to their Strava data.
- Quantified-self or analytics tools built on OpenClaw where the user is comfortable managing API credentials and occasional token refreshes.
- Internal or personal tools where the user understands and accepts the privacy implications of exposing Strava data to an AI system.
Comments (0)
No comments yet. Be the first!