CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

openclaw-migration

Import an OpenClaw setup (memories, skills) into Hermes.

56

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./optional-skills/migration/openclaw-migration/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with a well-validated workflow: exact commands, exact decision-to-flag mappings, dry-run gating, and report-driven post-run rules. Its main weakness is redundancy — the clarify protocol, payload shapes, and path guidance are each stated multiple times, inflating token cost without adding information.

Suggestions

Merge the clarify rules from "User interaction protocol", the execution gate, and "Important rules" #11-17 into a single authoritative section; the current three restatements say the same thing in slightly different words.

Drop the duplicate JSON payload list (lines 159-165) or replace the earlier prose choice lists with it — one of the two enumerations is enough.

Fix the duplicated "5." numbering in the decision flow and fold the absolute-invocation guidance from "Commands" into the existing path-resolution section to remove the remaining repetition.

DimensionReasoningScore

Conciseness

The clarify interaction rules are stated three times ("User interaction protocol" at lines 85-165, the execution gate, and "Important rules" #11-17), the exact JSON payload list repeats the choice sets already enumerated in the decision flow, and path-resolution guidance reappears in "Commands" — several padded, duplicated sections matching the 'noticeably verbose' anchor. It does not reach 1 because nothing explains general concepts Claude already knows, and exceeds 3 because the duplication goes beyond what incidental tightening would fix.

2 / 5

Actionability

Fully executable, copy-paste-ready commands cover every common case (dry run, --preset user-data, --preset full --migrate-secrets, --workspace-target), plus exact clarify payload JSON, an exact decision-to-flag mapping, and post-run rules keyed to concrete report fields — matches the top anchor with no pseudocode or vague steps.

5 / 5

Workflow Clarity

The default workflow is a clear 8-step sequence with dry-run-first validation, an explicit execution gate blocking unresolved decisions, a validate->fix->retry feedback loop for clarify errors, and post-run verification against report.summary with a reconciliation rule. This destructive/batch operation does have validation, so the cap at 3 does not apply; it matches the top anchor including error-recovery loops and checklists.

5 / 5

Progressive Disclosure

Good structure across 13 clearly headed sections; the single bundle reference (scripts/openclaw_to_hermes.py) is real, clearly signaled, and backed by a dedicated path-resolution section, with the ~150KB of implementation detail correctly kept in the script rather than inlined. Not 5: the ~80-line clarify protocol could live in a reference file, and the cross-section duplication degrades navigation.

4 / 5

Total

16

/

20

Passed

Description

57%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise, distinct, and names the core domain, but it is incomplete and under-triggered. It lacks any "Use when..." trigger guidance and omits the most natural user verb ("migrate"), so it would only reliably trigger on users who happen to say "import".

Suggestions

Add an explicit trigger clause, e.g. "Use when the user wants to migrate, move, or import an OpenClaw setup (~/.openclaw) into Hermes Agent."

Include the verb "migrate" and terms like "persona (SOUL.md)" or "command allowlist" to broaden natural trigger coverage without padding.

Mention the dry-run/conflict-report capability briefly so the 'what' covers what the migration actually produces.

DimensionReasoningScore

Specificity

"Import an OpenClaw setup (memories, skills) into Hermes" names the domain and two concrete action objects (memories, skills), matching the '1-2 concrete actions, but not comprehensive' anchor. It omits the other migrated items (SOUL.md, command allowlist, workspace assets, migration report), so it does not reach the 'several specific actions' anchor.

3 / 5

Completeness

The 'what' is clear (import OpenClaw setup into Hermes), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Relevant keywords are present ("Import", "OpenClaw", "setup", "memories", "skills", "Hermes"), but the most natural user verbs for this task — "migrate", "move", "transfer" — are absent, fitting 'some relevant keywords but missing common variations or synonyms'. Not 4, since a primary natural trigger phrase is missing rather than just a few.

3 / 5

Distinctiveness Conflict Risk

The two unique product names ("OpenClaw", "Hermes") define a clear niche with distinct triggers and minimal overlap with any other skill, matching the top anchor exactly.

5 / 5

Total

14

/

20

Passed

Validation

81%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository

NousResearch/hermes-agent

Path

optional-skills/migration/openclaw-migration/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.