agentteams-migrate

Analyze current OpenClaw setup and generate a migration package (ZIP) for importing into AgentTeams as a managed Worker

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./migrate/skill/SKILL.md

Quality

Content

75%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.

A well-structured, actionable migration guide with concrete commands, clear sequencing, and a verification checklist. It is held back from the top band by a few trims available, a heuristic manual-review step, and the absence of an explicit fix-retry feedback loop.

Suggestions

Add an explicit validate-then-retry loop after Step 6's verification (e.g. 'If any check fails, fix the file and re-run generate-zip.sh before delivering').

Tighten the architecture section by moving the lengthy builtin-merge example and base-image package list into a short reference table or a separate file, keeping SKILL.md as an overview.

Give more concrete guidance for the heuristic 'review and adjust' step in Step 1, such as example false-positive patterns to remove or a command to list unknown_binaries.

Dimension	Reasoning	Score
Conciseness	The architecture, builtin-merge, and base-image details are product-specific knowledge Claude would not already have, so the prose mostly earns its place; a few explanatory sentences could still be trimmed, fitting 'efficient with minor over-explanation.'	4 / 5
Actionability	Copy-paste-ready bash commands with full flags, concrete verify commands, and structured AGENTS.md/SOUL.md templates give mostly executable guidance; the heuristic 'review and adjust' step leaves a minor gap.	4 / 5
Workflow Clarity	Six steps are clearly sequenced and Step 6 provides an explicit verification checklist with ls/unzip commands; it stops short of a strong validate-fix-revalidate feedback loop, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Sections are well organized with a dedicated Script Reference pointing one level deep to the real bundle scripts (analyze.sh, generate-zip.sh, Dockerfile.tmpl); the inline architecture section is fairly long but overall placement is good.	4 / 5
	Total	16 / 20 Passed

Description

70%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.

A concise, specific description that clearly states what the skill does and occupies a distinct niche, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness. Adding a trigger clause would push it toward the top band.

Suggestions

Append a 'Use when...' clause, e.g. 'Use when migrating an OpenClaw instance into AgentTeams as a managed Worker, or when the user mentions AgentTeams migration/import.'

Surface a couple of natural trigger synonyms (e.g. 'import', 'move', 'convert OpenClaw to AgentTeams') so the description matches more user phrasings.

Dimension	Reasoning	Score
Specificity	Names several concrete actions ('Analyze current OpenClaw setup', 'generate a migration package (ZIP)', 'importing into AgentTeams as a managed Worker') with only minor coverage gaps, fitting the 'several specific actions' anchor above the 1-2-action midpoint.	4 / 5
Completeness	The 'what' is explicit but there is no 'Use when...' clause or equivalent trigger guidance, so 'when' is only weakly implied; per the judging guideline a missing trigger clause caps completeness at 3.	3 / 5
Trigger Term Quality	Product-specific terms 'OpenClaw', 'AgentTeams', 'managed Worker', and 'migration package (ZIP)' are natural phrases users of those products would say, giving good keyword coverage though a few synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	The description targets a narrow OpenClaw-to-AgentTeams migration niche with distinct product-name triggers, giving a clear niche with minimal conflict risk against other skills.	5 / 5
	Total	16 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: agentscope-ai/AgentTeams
Path: migrate/skill/SKILL.md
Commit: 223ddc2

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.