CtrlK
BlogDocsLog inGet started
Tessl Logo

migrate-skills-between-libraries

Use when moving skills between library workspaces or upgrading from a personal library to a team library. Export from one workspace, import into another.

71

Quality

88%

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

93%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, executable migration workflow with explicit guardrails and validation. The only gap is a missing explicit validate-then-fix-retry feedback loop for destructive operations, which prevents a perfect workflow_clarity score.

Suggestions

Add an explicit feedback loop after the final `validate` step: 'If validation reports errors, fix them in the target workspace and re-run `validate` before considering the migration complete.'

Clarify the dependency-migration sub-workflow with a concrete command sequence rather than only noting it in Gotchas, since dependencies must also be migrated.

DimensionReasoningScore

Conciseness

Lean and efficient with no over-explanation of concepts Claude already knows; every line and code block earns its place.

5 / 5

Actionability

Fully executable, copy-paste-ready commands with real flags (--dry-run, --skill <name>, --format json, --branch) covering both house-copy and upstream cases.

5 / 5

Workflow Clarity

Clear numbered sequence with a --dry-run checkpoint before mutating commands and a final validate step, but lacks an explicit error-recovery feedback loop ('if validate fails, fix and re-run') for these destructive/batch operations.

4 / 5

Progressive Disclosure

Self-contained single file (~60 lines) with well-organized sections (Goal, Guardrails, Workflow, Gotchas) and no need for external references.

5 / 5

Total

19

/

20

Passed

Description

82%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 strong, third-person description with an explicit 'Use when' trigger and concrete what/when coverage. Minor room to expand specificity (dependency/collection migration) and trigger synonyms, but otherwise clear and distinct.

DimensionReasoningScore

Specificity

Names the domain ('moving skills between library workspaces') and two concrete actions ('Export from one workspace, import into another'), but coverage is not comprehensive — no mention of dependency/collection handling or validation that the body covers.

3 / 5

Completeness

Explicitly answers both 'what' (export from one workspace, import into another) and 'when' ('Use when moving skills between library workspaces or upgrading from a personal library to a team library') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a user would say ('moving skills between library workspaces', 'upgrading from a personal library to a team library'), with good coverage though a few synonyms (e.g. 'migrate', 'transfer') are absent.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (skill migration between library workspaces) with distinct triggers and minimal overlap risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
MoizIbnYousaf/ai-agent-skills
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.