SKILLEMALL.ai
GitHub ↗ RU Sign in

BF openclaw-release-validation

Test the latest OpenClaw main commit through an isolated OCM copy or an explicitly approved in-place gateway update, then guide structured release feedback.

ClawHub Claude Code author: OpenClaw v0.1.7 MIT-0 7 files body ≈ 10 754 tokens Open the sourceclawhub.ai↗ analyzed 2 d ago

Test the latest OpenClaw main commit through an isolated OCM copy or an explicitly approved in-place gateway update, then guide structured release feedback.

As a process F 46/100 · Will not run — References files that are not bundled: taxonomy-url, release-url

AnalyzerGitHubData and analyticstype and topics are labelled automatically from the skill text
Runs in: OpenClaw 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) Goose OpenCode
JSON
Technical rating
B
80/100
safety, quality, tests
Safety 60%
95
Quality 40%
58
Run on models
none yet
Process rating
F
46/100
Will not run
References files that are not bundled: taxonomy-url, release-url
Tools and files w 18
0
Result and completion w 14
0
Inputs and preconditions w 11
30
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

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 SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
  3. 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 · 1

✓ No critical or high findings

Medium and low: 1
  • medium Dangerous commands cmd-pipe-to-shell-known-host SKILL.md:353
    Pipe-to-shell installer from a well-known host (still executes remote code)
    curl -fsSL https://github.com/openclaw/ocm/releases/latest/download/install.sh | bash

Files scanned: 7. 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 body-long SKILL.md body ≈ 10754 tokens (recommended < 5000); move details to references/
  • warning missing-ref reference to a missing file: taxonomy-url
  • warning missing-ref reference to a missing file: release-url

Process rating: all ten parameters 46/100

Will not run. References files that are not bundled: taxonomy-url, release-url
  • 0Tools and files. 2 referenced file(s) missing: taxonomy-url, release-url
  • 0Result and completion. Does not say what the result is
  • 30Inputs and preconditions. Does not say what the process needs to start
  • 40Consistency. Frontmatter name (openclaw-release-validation) differs from the folder (release-validation)
  • 40Execution cost. Instruction body is 10754 tokens: crowds the task out of the window
  • 50When it triggers. No condition that starts the skill
  • 100Steps. 45 steps
  • 100Failures and branches. 1 branches, has a failure section
  • 100Running it twice. Mutating operations check current state
  • 100Progress reporting. Reports progress
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 10 top-level sections: this looks like several domains in one skill
  • low The response is described with custom markup (20 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 156: enough signal without eating the budget
  • +4Structure: 16 headings
  • +3Step-by-step instructions: 45 items
  • +4Has examples (27 code blocks)
  • +4Reference files are cited in the instructions (2 of 2)
  • +3All 1 scripts are documented

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

External checks

ClawHub: clean
This skill is a disclosed release-validation workflow with clear safeguards around local gateway changes and public GitHub posting.
LLM: benign (high) · VirusTotal: · 31 Aug 2026