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

81%

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

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.

The body is an exemplar of lean, executable skill content: complete commands with dry-run safety, both migration variants covered, and skill-specific gotchas. The only meaningful gap is the absence of explicit error-recovery guidance after the validate step.

Dimension	Reasoning	Score
Conciseness	The body is lean and command-driven with no explanations of concepts Claude already knows; every section (Goal, Guardrails, Workflow, Gotchas) carries skill-specific, non-obvious information. Only trivial overlap exists between Guardrails/Gotchas and the workflow steps, which is closer to anchor 5 (every token earns its place) than anchor 4.	5 / 5
Actionability	Fully executable npx ai-agent-skills commands are provided for both migration paths (vendor for house copies, catalog for upstream picks), each shown with a --dry-run run followed by the real invocation, plus build-docs and validate commands. This matches anchor 5 (copy-paste ready commands covering the common cases), not anchor 4 which implies gaps.	5 / 5
Workflow Clarity	The six steps are clearly sequenced with dry-run checkpoints before every mutating command and a final validate step, satisfying anchor 4 (clear sequence, most checkpoints present). It falls short of anchor 5 because there is no error-recovery feedback loop explaining what to do if validate fails or a dry-run reports a collision.	4 / 5
Progressive Disclosure	There are no bundle files and none are needed; the compact body is organized into clear Goal, Guardrails, Workflow, and Gotchas sections with no content that belongs in a separate file. Per the rubric's simple-skill guidance, well-organized sections in a self-contained skill warrant anchor 5.	5 / 5
	Total	19 / 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.

The description has an explicit, well-targeted "Use when" clause with natural trigger phrases and a distinct niche, but its what-clause is thin. Expanding the capability list and adding synonyms like "migrate" or "transfer" would strengthen it.

Suggestions

Enumerate more concrete capabilities in the what-clause, e.g. "Preserves metadata and dependencies, checks for name collisions, and rebuilds docs in the target workspace" to raise specificity from 1-2 actions to several.

Add natural synonyms such as "migrate", "transfer", or "copy skills" to the trigger phrasing so users who say "migrate my skills" match the description.

Mention the underlying tooling (e.g. the ai-agent-skills CLI) or file types involved to further reduce overlap with generic skill- or library-management skills.

Dimension	Reasoning	Score
Specificity	The description names the domain plus two concrete actions ("Export from one workspace, import into another"), but does not enumerate the fuller capability set such as preserving metadata, checking name collisions, or rebuilding docs. It matches anchor 3 (domain and 1-2 concrete actions, not comprehensive), not anchor 4 which requires several specific actions.	3 / 5
Completeness	Both parts are present: an explicit "Use when moving skills... or upgrading from a personal library to a team library" trigger and a what-clause "Export from one workspace, import into another". The when-clause is explicit with two concrete triggers, so it clears anchor 3, but the what-clause is terse and not fully specific, keeping it below anchor 5.	4 / 5
Trigger Term Quality	Natural phrases a user would say are present ("moving skills", "personal library", "team library", "upgrading"), giving good keyword coverage. It falls short of anchor 5 because common synonyms like "migrate", "transfer", or "copy skills" are missing, but exceeds anchor 3 whose keywords are thinner and lack natural variations.	4 / 5
Distinctiveness Conflict Risk	The niche (migrating skills between library workspaces, personal-to-team library upgrades) is clearly distinguishable with distinct trigger phrases, matching anchor 4. It is not a 5 because "skills" and "library" are broadly used terms that could mildly overlap with general skill-management or package-management skills.	4 / 5
	Total	15 / 20 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: 6d95c78

Reviewed: 6 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.