openclaw-proof-validation Skill
Plan and collect OpenClaw Windows validation/proof: tests, rubber-duck review, UI evidence, MCP output, and gateway runtime proof. Published by openclaw in openclaw-windows-node.
What is openclaw-proof-validation Skill?
Plan and collect OpenClaw Windows validation/proof: tests, rubber-duck review, UI evidence, MCP output, and gateway runtime proof. Published by openclaw in openclaw-windows-node. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Testing
- Security review
- Data analysis
- Design and media
- Testing use cases
Technical details
- Install or run with Copy skill directory
When to use openclaw-proof-validation Skill
- Use it for testing.
- Use it for security review.
- Use it for data analysis.
- Use it for design and media.
Built with
Editorial notes
Source
- Creator: openclaw
- Repository: openclaw/openclaw-windows-node
- Skill file: .agents/skills/openclaw-proof-validation/SKILL.md
What it does
Plan and collect OpenClaw Windows validation/proof: tests, rubber-duck review, UI evidence, MCP output, and gateway runtime proof.
Skill instructions
OpenClaw Proof and Validation Use for changes that affect tray UX, Settings, onboarding, chat/canvas, Command Center, Windows node capabilities, local MCP, gateway connection/pairing, permissions, diagnostics, or agent-facing instructions. Rules - Required automated/focused tests are mandatory. Do not ask to skip them. - Prefer isolated tray data so proof does not mutate %APPDATA%\OpenClawTray. - Computer-use is usually a batched closeout proof pass, not a continuous dev-loop tool. Mid-development use is fine when explicitly requested or needed to unblock work; ask first whether to run it or provide manual screenshot/output steps. - Local MCP is part of every Windows node command contract: command discovery and invocation must work through winnode or raw MCP JSON-RPC. - Rubber-duck review is required before PR publication for non-trivial UI/MCP/node-command/setup/pairing/security/permissions/diagnostics work; it is also useful mid-development when extra design/testing validation is req
Explore related resources
Frequently asked questions
What is openclaw-proof-validation?
openclaw-proof-validation is a open-source AI agent skill with Copy skill directory. Plan and collect OpenClaw Windows validation/proof: tests, rubber-duck review, UI evidence, MCP output, and gateway runtime proof.
Who is openclaw-proof-validation best for?
openclaw-proof-validation is best for reusing agent instructions, scripts, and references, testing workflows, security review workflows, data analysis workflows.
How do I install openclaw-proof-validation?
Install or run openclaw-proof-validation using Copy skill directory. Check openclaw-proof-validation for the latest setup command.
Is openclaw-proof-validation actively maintained?
openclaw-proof-validation may need a closer maintenance check before production use.
Auto-fetched from GitHub.
