Skip to content

v0.8.5 — whoop-mcp-install-skills (closes #6) + first auto-publish run

Latest

Choose a tag to compare

@AshwanthramKL AshwanthramKL released this 25 Apr 10:12
· 2 commits to main since this release

What

whoop-mcp-install-skills console script. One command installs the bundled whoop-insights skill into ~/.claude/skills/ so Claude Code (and Cursor / Windsurf / Zed) auto-discover it. Closes #6.

pip install --upgrade whoop-mcp
whoop-mcp-install-skills          # writes to ~/.claude/skills/, fetched from GitHub main

For repo-native developers: whoop-mcp-install-skills --source ./skills installs from a local working tree.

Why

The flagship whoop-insights skill was advertised in the README as ready-to-use, but Claude Code only auto-discovers from ~/.claude/skills/. Shipping the file in the repo (or the wheel) doesn't put it there. Every first-time user hit "There's no whoop-insights skill in the available skills list." — including me, during dogfood.

Process milestone

This is the first release shipped through the fully-automated tag→PyPI→Registry pipeline added in v0.8.4 (commit f24e4d5). Workflow:

  1. Push tag → publish-pypi.yml fires
  2. Job 1 builds sdist+wheel, twine check, uploads to PyPI via trusted publishing OIDC (no token in env)
  3. Job 2 (needs: publish-pypi) polls PyPI until propagated, syncs server.json version from tag, validates, publishes to MCP Registry via GitHub OIDC

End-to-end ~1 min. Zero manual steps, zero credentials touched.

Tests

198 passing (190 from v0.8.4 + 8 new tests for the install-skills module). ruff + mypy clean.

Install

uvx --from whoop-mcp==0.8.5 whoop-mcp-oauth   # one-time OAuth (skip if already done)
whoop-mcp-install-skills                       # install the skill
# Then register the server with your MCP client per README.