SKILLEMALL.ai
GitHub ↗ RU Sign in

CD openclaw-proof-validation

Plan and collect OpenClaw Windows validation/proof: tests, rubber-duck review, UI evidence, MCP output, and gateway runtime proof.

openclaw/openclaw-windows-node Agent Skills author: openclaw 2 files body ≈ 2 644 tokens Open the sourcegithub.com↗ analyzed 5 d ago

Plan and collect OpenClaw Windows validation/proof: tests, rubber-duck review, UI evidence, MCP output, and gateway runtime proof.

As a process D 40/100 · Unfinished process — References files that are not bundled: ../../../docs/TEST_COVERAGE.md, ../../../docs/GATEWAY_FIXTURE_TESTING.md, ../../../run-app-local.ps1

AnalyzerAI and agentstype and topics are labelled automatically from the skill text
Runs in: Claude / Claude Code ChatGPT / Codex Gemini CLI Cursor GitHub Copilot / VS Code Qwen Code Kimi Code CLI Z.ai (GLM) DeepSeek (Deep Code) Mistral Vibe LangChain (deepagents) OpenClaw Goose OpenCode
JSON
Technical rating
C
83/100
safety, quality, tests
Safety 60%
100
Quality 40%
58
Run on models
none yet
Process rating
D
40/100
Unfinished process
References files that are not bundled: ../../../docs/TEST_COVERAGE.md, ../../../docs/GATEWAY_FIXTURE_TESTING.md, ../../../run-app-local.ps1
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
  2. The text references files that are not there: add them or drop the references.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 0

✓ No critical or high findings

Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • warning missing-ref reference to a missing file: ../../../docs/TEST_COVERAGE.md
  • warning missing-ref reference to a missing file: ../../../docs/GATEWAY_FIXTURE_TESTING.md
  • warning missing-ref reference to a missing file: ../../../run-app-local.ps1
  • warning missing-ref reference to a missing file: ../native-gateway-from-source/SKILL.md
  • warning missing-ref reference to a missing file: ../autoreview/SKILL.md
  • warning missing-ref reference to a missing file: ../windows-pr-prepare/SKILL.md
  • warning missing-ref reference to a missing file: ../../../docs/PROOF_POOLS.md

Process rating: all ten parameters 40/100

Will not run. References files that are not bundled: ../../../docs/TEST_COVERAGE.md, ../../../docs/GATEWAY_FIXTURE_TESTING.md, ../../../run-app-local.ps1
  • 0Tools and files. 7 referenced file(s) missing: ../../../docs/TEST_COVERAGE.md, ../../../docs/GATEWAY_FIXTURE_TESTING.md, ../../../run-app-local.ps1
  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 20When it triggers. No condition that starts the skill
  • 30Running it twice. 3 mutating operations with no state check
  • 50Failures and branches. 0 branches, has a failure section
  • 100Steps. 17 steps
  • 100Consistency. Name and required fields are in place
  • 100Execution cost. Instruction body is 2644 tokens
  • 100Progress reporting. Reports progress
  • low The response is described with custom markup (4 tags): a typed call is more reliable

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Output format is not stated: the model decides each time
  • -2localhost URLs: will not work for another user
  • +1No license
  • +2Single-language instructions
  • +3Description length 130: enough signal without eating the budget
  • +4Structure: 9 headings
  • +3Step-by-step instructions: 17 items
  • +4Has examples (5 code blocks)

Quality base 70; lint remarks subtract, signals add up to 100. Result: 58.