SKILLEMALL.ai
GitHub ↗ RU Sign in

BC openclaw-migration

Migrate a user's OpenClaw customization footprint into Hermes Agent. Imports Hermes-compatible memories, SOUL.md, command allowlists, user skills, and selected workspace assets from ~/.openclaw, then reports exactly what could not be migrated and why.

ClawHub Hermes author: Agung Prabowo v0.1.0 MIT-0 3 files body ≈ 3 852 tokens Open the sourceclawhub.ai↗ analyzed 3 d ago

As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency

ReferenceData and analyticsInfrastructureAI and agentstype and topics are labelled automatically from the skill text
Runs in: OpenClaw Hermes Agent
JSON
Technical rating
B
86/100
safety, quality, tests
Safety 60%
100
Quality 40%
66
Run on models
none yet
Process rating
C
52/100
Has gaps
Result and completion w 14
0
Inputs and preconditions w 11
0
Consistency w 8
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. For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
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: 3. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning description-long-hermes description is 251 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period)
  • warning description-no-when neither description nor a "## When to Use" section says when to use the skill

Process rating: all ten parameters 52/100

  • 0Result and completion. Does not say what the result is
  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Consistency. Frontmatter name (openclaw-migration) differs from the folder (openclaw-migration-2)
  • 0Progress reporting. Says nothing while it works
  • 50When it triggers. No condition that starts the skill
  • 60Tools and files. Uses tools (bash) that frontmatter does not declare
  • 100Steps. 132 steps
  • 100Failures and branches. 26 branches, has a failure section
  • 100Execution cost. Instruction body is 3852 tokens
  • 100Running it twice. Mutating operations check current state
  • medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
  • low 11 top-level sections: this looks like several domains in one skill

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
  • -4Absolute local paths (C:\Users, /home/…): not portable
  • +2Single-language instructions
  • +3Description length 251: enough signal without eating the budget
  • +4Structure: 12 headings
  • +3Step-by-step instructions: 132 items
  • +4Has examples (7 code blocks)
  • +3All 1 scripts are documented
  • +1License stated

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

External checks

ClawHub: suspicious
The skill is a coherent local migration tool, but its script can migrate more secrets than the user-facing instructions promise, including some tokens in the supposedly non-secret mode.
LLM: suspicious (high) · VirusTotal: · 29 May 2026