Skip to main content

​
What this is

A Claude Code skill — listed on skills.sh — that teaches your local Claude agent to build on top of WaterrAI. Once installed, asking Claude things like “build a candidate screening flow on Waterr” or “create a meeting and pull the analysis” will trigger the skill — which then:
  1. Internally runs a generate-understanding sub-skill to interview you and produce a written scope-of-work
  2. Waits for your sign-off
  3. Implements against the canonical API docs (it cites every endpoint URL it uses)
The skill is the same docs you’re reading right now, packaged for the agent.

​
Install

One command (works for Claude Code, Cursor, Windsurf, Copilot — any SKILL.md-compatible agent):
That installs the waterr-api skill. It loads on any “build/integrate/automate on WaterrAI” request and internally invokes the bundled generate-understanding sub-skill at the start of any non-trivial build — you never have to install or invoke the sub-skill yourself.

​
Manual install (advanced)

If you’d rather manage the files yourself, clone the repo into your Claude Code skills directory:
Update later with cd ~/.claude/skills/waterrai && git pull.

​
How it works

​
1. You describe what you want

​
2. Claude runs the generate-understanding sub-skill first

It asks at most three questions per round, across three rounds:
  • What & why — user-facing outcome, trigger, where results land
  • The meeting — persona reuse vs per-session, goals, recording, language
  • Integration shape — sync vs async, webhooks vs polling, auth model
Then it writes WATERR_BUILD_SCOPE.md to your project root and asks you to confirm before any code is written.

​
3. You approve, Claude builds

Control returns to the parent waterr-api skill. It fetches the relevant API reference pages, writes the integration code, and cites the docs URL next to every endpoint it calls.

​
What the skill knows

The skill links to — and tells Claude to fetch before guessing — the full developer docs: It also encodes the common pitfalls — membership_id ≠ user ID, voice IDs must come from /voices, analyses are async, scenarios are workspace-scoped.

​
Skip the scoping

If you already know exactly what you want, just tell Claude:
The skill will jump straight to implementation for single-endpoint asks.

​
Source

Open source, MIT-licensed: github.com/waterrai/skills. PRs welcome.