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.

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

87%

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

The body is lean and highly actionable, with concrete executable commands and a clearly sequenced workflow. Its main weakness is workflow clarity: validation checkpoints exist but the validate→fix→retry feedback loop is implicit rather than explicit.

Suggestions

Make the error-recovery feedback loop explicit, e.g. after each '--dry-run' add 'If the dry-run reports name collisions or missing dependencies, resolve them before running the command without --dry-run'.

After the final 'validate' step, add a conditional such as 'If validation fails, review the errors, fix the offending skill metadata, and re-run validate before proceeding.'

De-duplicate the name-collision guidance, which appears in both Guardrails ('Never import skills without checking for name collisions') and Gotchas ('Skill names must be unique per workspace. Check for collisions before importing').

Dimension	Reasoning	Score
Conciseness	The body is lean — a one-sentence goal, guardrails, concrete workflow commands, and gotchas — with no explanation of concepts Claude already knows. It is not score 2 because there is no padded or unnecessary exposition to tighten.	3 / 3
Actionability	It provides fully executable commands such as 'npx ai-agent-skills list --format json --fields name,tier,workArea,collections' and 'npx ai-agent-skills vendor ... --dry-run', copy-paste ready with clearly marked placeholders.	3 / 3
Workflow Clarity	Steps are clearly numbered 1–6 with an explicit '--dry-run' checkpoint and a final 'validate' step, but the error-recovery feedback loop ('if dry-run/validate fails → fix → retry') is not spelled out, which the top anchor requires. It is above score 1 because validation checkpoints are present, not missing.	2 / 3
Progressive Disclosure	This single-purpose skill is organized into clear sections (Goal, Guardrails, Workflow, Gotchas) with no nested or external references, so well-organized sections alone meet the bar. It is not score 2 because nothing that belongs in a separate file is inlined.	3 / 3
	Total	11 / 12 Passed

Description

100%

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, third-person, and clearly states both what the skill does (export/import skills) and when to use it (moving or upgrading skill libraries). Concrete trigger terms and a distinct niche make it strong across all dimensions.

Dimension	Reasoning	Score
Specificity	It lists concrete actions — 'Export from one workspace, import into another' — rather than vague language, matching the anchor for multiple specific concrete actions. It is concise, not padded.	3 / 3
Completeness	An explicit 'Use when...' clause supplies the trigger, and 'Export from one workspace, import into another' answers what it does, satisfying both what and when.	3 / 3
Trigger Term Quality	Phrases like 'moving skills between library workspaces' and 'upgrading from a personal library to a team library' are natural terms a user managing skill libraries would actually say, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	The niche — migrating skills between library workspaces — is specific with distinct triggers, making it unlikely to fire for an unrelated skill.	3 / 3
	Total	12 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: MoizIbnYousaf/Ai-Agent-Skills
Path: skills/migrate-skills-between-libraries/SKILL.md
Commit: 039ad59

Reviewed: about 5 hours 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.