Hevy

**Judgment** Solid, focused integration for users who actively use Hevy and have a Pro subscription with API access. It’s strong for read-heavy workflows (querying workouts, routines, exercises, and history) and reasonably safe if used carefully. Write operations add power but should be invoked only with explicit user intent. **Key strengths** - Covers the main Hevy entities: workouts, routines, exercise templates, exercise history, and routine folders. - JSON output options (`--json`) make it suitable for reliable parsing and structured reasoning. - Examples and flags are clear, supporting typical user questions about past workouts, progress trends, and routine contents. **Risks / limitations** - **Access requirement**: Requires a Hevy Pro subscription and a configured `HEVY_API_KEY`. Without this, calls will fail (auth errors), so tools must handle missing/invalid credentials gracefully. - **External dependency**: All functionality depends on the Hevy API being available and responsive; network/API issues can degrade performance or reliability. - **Data volume & rate limits**: Using `--all` or high `--limit` values can be slow and may hit rate limits; implementations should prefer minimal, targeted queries. - **Write operations**: Creating/updating workouts, routines, and custom exercises can modify the user’s account. There is no API support for deleting exercise templates, so mistaken creations may be hard to clean up. The `--force` flag for `create-exercise` bypasses duplicate protections and should be avoided unless the user explicitly requests it. - **Privacy**: The skill surfaces potentially sensitive personal fitness and health-related data. It should only be used for the authenticated user’s data, and any summaries or exports should respect user privacy expectations. **Recommended scenarios** - Users who already track their training in Hevy and ask things like: - “What did I do at the gym this week?” - “How am I progressing on bench press/squats?” - “What routines do I have?” or “What’s in my push day routine?” - Situations where structured workout data is needed for analysis, progress summaries, or planning adjustments (e.g., generating insights from exercise history or routine composition). - Explicitly requested account modifications, such as “Create a push day routine in my Hevy account with bench press, shoulder press, and triceps work,” where the tool carefully constructs routine JSON and uses create/update commands. **Usage guidance** - Prefer **read-only commands** (`workouts`, `workout`, `routines`, `routine`, `exercises`, `history`, `count`, `folders`) for most queries. - Use **write commands** (`create-routine`, `update-routine`, `create-exercise`, folder creation, workout creation/update) **only** when the user clearly asks to change their Hevy data and understands that changes affect their live account. - Avoid `--force` on `create-exercise` unless the user explicitly wants multiple exercises with the same name. - Handle pagination and limits conservatively to avoid rate-limit issues and latency spikes.