CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentteams-migrate

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

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 strong, highly actionable workflow skill: domain-specific architecture knowledge Claude cannot infer, copy-paste commands, complete script documentation, and a real verification step at the end. Its only weaknesses are mild redundancy across sections and inlined templates that could live in the existing templates/ directory.

DimensionReasoningScore

Conciseness

The body is dense with product-specific facts Claude cannot know (Matrix-based architecture, MinIO state, builtin-merge markers, pre-installed tool list) with almost no generic filler; only minor trimmable padding ("requires your intelligence — it cannot be done mechanically") and light repetition of Matrix-vs-Discord/Slack points across sections. Not a 5 because a few sections restate the same migration facts in both the table and later sections.

4 / 5

Actionability

Fully executable throughout: copy-paste bash invocations for analyze.sh and generate-zip.sh, a complete flag reference for both scripts, concrete AGENTS.md/SOUL.md output templates, verification commands (ls, unzip -l), and ready-to-run Linux/PowerShell import commands. The one judgment-heavy step (adapting AGENTS.md) is supported by an explicit keep/remove/adapt/add breakdown and a structural template.

5 / 5

Workflow Clarity

A clearly sequenced 6-step workflow with explicit validation checkpoints: Step 1 instructs reviewing the heuristic analysis for false positives, Step 6 is a verification checklist (manifest correctness, Dockerfile packages, no Discord/Slack references in AGENTS.md, AI Identity section present), and Step 5 documents the failure mode of running the packaging script before adapting files, with a recovery alternative (replace files in the generated ZIP).

5 / 5

Progressive Disclosure

Well-organized sections with clearly signaled, verified, one-level-deep script references (scripts/analyze.sh, scripts/generate-zip.sh, scripts/templates/Dockerfile.tmpl all exist) and no nested references. Not a 5 because the AGENTS.md and SOUL.md output templates are inlined in SKILL.md even though a templates/ directory exists in the bundle, and the ~230-line body could offload some reference material (e.g. the builtin-section topic list) to separate files.

4 / 5

Total

18

/

20

Passed

Description

65%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 specific, distinctive description with concrete actions and a clear deliverable, but it lacks any explicit 'when to use' trigger guidance, which limits its discoverability and completeness. Adding a "Use when..." clause would resolve the main weakness.

Suggestions

Add an explicit trigger clause, e.g. "Use when migrating an existing OpenClaw instance to AgentTeams, or when the user mentions moving/transferring their OpenClaw bot to AgentTeams."

Broaden keyword coverage with natural synonyms such as "move", "transfer", or "port" so users phrasing the request differently still match.

Optionally mention the key sub-tasks (adapting AGENTS.md/SOUL.md, packaging a Dockerfile) to make the 'what' more comprehensive.

DimensionReasoningScore

Specificity

The description names the domain and two concrete actions — "Analyze current OpenClaw setup" and "generate a migration package (ZIP)" — with a concrete deliverable, but coverage is not comprehensive (adapting AGENTS.md, SOUL.md, and cron jobs is unstated). This matches the 'names domain and 1-2 concrete actions' anchor; it falls short of 4, which requires several listed actions.

3 / 5

Completeness

Has a clear 'what' (analyze setup, generate ZIP) but no "Use when..." clause or equivalent explicit trigger guidance; per the judging guidelines a missing trigger clause caps completeness at 3. The purpose phrase 'for importing into AgentTeams as a managed Worker' only weakly implies 'when'.

3 / 5

Trigger Term Quality

Includes natural terms users would say: "OpenClaw", "AgentTeams", "migration", "importing", "Worker", "ZIP". Not a 5 because common synonyms like "move", "transfer", or "port" are missing.

4 / 5

Distinctiveness Conflict Risk

Names two specific products (OpenClaw, AgentTeams) and a specific operation (migration to managed Worker), giving it a clear niche with distinct triggers and minimal risk of firing for unrelated skills.

5 / 5

Total

15

/

20

Passed

Validation

100%

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

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.