clipboard-testinglisted
Install: claude install-skill ClipboardHealth/groundcrew
# Clipboard Testing
This skill lets you verify Clipboard Health changes end-to-end against `development`. It is opinionated about two things:
- **API-first.** curl against the dev gateway with tokens from `cbh auth gentoken`. No packages to install.
- **Concepts over memorized payloads.** Field shapes and validation rules change. The skill teaches you _what owns what_ and _where to read current truth_ — not a fixed cookbook.
The one area where the skill carries enough detail to run alone is the **core happy-path flow** (create workplace → create worker → create shift → book → clock in/out → trigger pay → generate invoice). Everything else is concept + controller pointer + "read the file before you call it".
## Hard guardrails
`development` only. The recipes here mint S2S tokens, create Cognito users, and move test-mode money — running them in any other environment is out of scope and can have real consequences.
1. **Env literal must be `development`.** If the user asks for `staging`, `prod-shadow`, `prod-recreated`, `production`, or any other env, refuse and stop. Pin in scripts:
```bash
ENV=development
[ "$ENV" = "development" ] || { echo "REFUSE: dev-only" >&2; exit 1; }
```
2. **HTTPS host allowlist.** Every curl or browser request must match one of:
- `*.development.clipboardhealth.org` (gateway + admin-webapp + hcp-webapp + home-health-api)
- `mailpit.tools.cbh.rocks`
- `sandbox.invoiced.com` (Invoiced.com sandbox)
```bash
case "$URL"