soak-product
Skill5 starsChanged 24 days agoApache-2.0View on GitHub
Full product soak for Remedy — API health, computer-use, plan mode, browser rail, concurrency, docs check, and sign-off artifacts. Use when soak, product soak, e2e live, computer-use checklist, or pre-merge confidence on desktop+API.
In this repository9 other files it gives its agents.
- change-safetySkill
- gauntlet-securitySkill
- memory-backupSkill
- project-etiquetteSkill
- refactor-safeSkill
- self-dev-loopSkill
- self-injectSkill
- stress-suiteSkill
- webui-paritySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 21
After computer-use / browser / stream / multi-tab changes
- Distinctive: line 23
Before merge of a large feature branch
- Very specific: line 86
Update or create docs/full-product-soak-signoff.md (or dated note):
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Product soak
Goal
End-to-end confidence that Desktop + local API still work as a product —
not only unit tests. Produces machine-readable results under docs/.
When to use
- After computer-use / browser / stream / multi-tab changes
- User says soak, full product soak, e2e live, sign-off
- Before merge of a large feature branch
Preconditions
- API up (
http://127.0.0.1:7400or isolated:7410) - Desktop running with computer host when testing CUA
- Release install or
npm run tauri:dev:isolated
- Release install or
- Build mode (not Plan-only) for click/type
- Token:
~/.remedy/auth/local_api_token(or$REMEDY_HOME/auth/…)
$env:REMEDY_API = "http://127.0.0.1:7400"
$env:REMEDY_HOME = "$env:USERPROFILE\.remedy"Automated soak (primary)
From repo root with API + desktop live:
.\.venv\Scripts\python.exe scripts\_full_product_soak.py- Writes
docs/_full_product_soak_results.json - Exit 0 only if no FAIL (SKIP allowed)
- Covers health, computer-use, plan allowlist, providers, concurrency, docs
Also useful:
.\.venv\Scripts\python.exe scripts\_soak_run.py
.\.venv\Scripts\python.exe scripts\live_full_product_e2e.py
.\.venv\Scripts\python.exe scripts\computer_rail_e2e.pyComputer-use checklist (manual / agent)
Open F1 or:
help_read(id="computer-use-soak")Canonical chapter: docs/manual/computer-use-soak.md.
Minimum path:
computer_monitors→ ≥1 displaycomputer_screenshot→ PNG under homecomputer/shots/computer_snapshot→ window refs- Browser: navigate in-rail, snapshot
eN, click, stop cancels jobs - Offline: navigate does not surprise-open OS browser
Unit neighbors (always before claiming soak)
uv run pytest -q tests/test_computer_use.py tests/test_react_stream.py tests/test_react_policy.py
uv run python scripts/check_docs.py
cd desktop && npm testSign-off format
Update or create docs/full-product-soak-signoff.md (or dated note):
| Metric | Value |
| PASS / FAIL / SKIP | counts |
| API version / port | |
| Desktop host connected | yes/no |
| Verdict | PASS or blocked + next fix |
Anti-patterns
- Soak against dead API
- “PASS” with FAIL in
_full_product_soak_results.json - Skipping computer host when the change was CUA/browser
- Running soak scripts against the wrong home/port during dual-instance dogfood
Related skills
- self-inject — test-gated auto-improve (draft → gate → apply/rollback)
- gauntlet-security — security-focused gate
- stress-suite — higher load after soak is green
- self-dev-loop — sequence
- project-etiquette — ship after green soak when releasing
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

