Test for openclaw
Skill LeoYeAI/openclaw-coding-skills/skills/test-for-openclaw
Production-grade coding workflow, execution scaffolding, and tuning skills for OpenClaw agents, part of the MyClaw.ai ecosystem.
npx -y skills add LeoYeAI/openclaw-coding-skills --skill test-for-openclawAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Require evidence before declaring coding work done in OpenClaw. Use when the request sounds like "verify this works", "what tests should we add", "prove this is safe", "is this ready", or any implementation, fix, refactor, review, or deploy task where the right level of proof is ambiguous or easy to under-scope.
SKILL.md
1.1 KB, as published. Nobody here has run it
Test For OpenClaw
Completion requires proof.
Process
- Identify the real behavior at risk.
- Choose the cheapest credible form of evidence.
- Run verification as close as possible to the changed surface.
- Record what passed, what was not run, and why.
- Refuse to overclaim when evidence is partial.
Acceptable Evidence
- targeted automated tests
- lint or typecheck on affected code
- browser-based flow verification for UI changes
- reproduction before and after for bug fixes
- diff inspection for prompt or documentation-only work
Reference Files
Read references/evidence-ladder.md when you need to choose the minimum credible proof for a change.
Bad Evidence
- confidence without execution
- "looks right"
- passing unrelated tests
- assumptions about triviality