nx-multi-repo-migrate

Migrate several repos to a target nx version (e.g. 23.0.0-beta.25) in one coordinated pass — delegates `nx migrate` + migrations to a Polygraph child agent per repo, then pushes branches and opens linked draft PRs. Use when asked to upgrade/migrate multiple repos to a specific nx version, or when working a Polygraph session whose goal is an nx version bump across repos.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

77%

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

Highly actionable and clearly sequenced with strong validation checkpoints, reflecting hard-won operational knowledge. The main weakness is conciseness and progressive disclosure: dense gotcha paragraphs and scattered version numbers are inline in one monolithic file rather than tightened or offloaded to a reference.

Suggestions

Tighten the 'Gotchas from real runs' paragraphs into shorter bullets and move illustrative version numbers (e.g. beta.23->beta.25) into a single concrete example rather than scattering them through prose.

Extract the five 'Gotchas from real runs' entries into a references/ file (e.g. GOTCHAS.md) and link to it one level deep, keeping SKILL.md as an overview + procedure.

Consider an 'old patterns' or 'deprecated' section for version-pinned specifics so the main flow stays version-agnostic and concise.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and assumes Claude's competence (no explaining what nx/PRs are), and the gotchas are genuinely non-obvious knowledge. But the 'Gotchas from real runs' paragraphs are dense, long run-on sentences, and specific version numbers (e.g. 23.0.0.beta.25, 23.1.0-beta.5) are scattered inline rather than isolated, so it could be tightened.	2 / 3
Actionability	Fully executable commands throughout — `npm view nx@<version> version`, `git fetch origin <base> && git checkout -B migrate-nx-<VERSION> origin/<base>`, `nx migrate --run-migrations`, `nx run-many -t lint --skip-nx-cache` — plus a copy-paste-ready package-manager cheat sheet.	3 / 3
Workflow Clarity	An explicit 11-step numbered procedure with a dedicated verification step (step 9), a per-repo verification checklist, and feedback loops (fix migration breaks, re-validate) for this batch operation across multiple repos.	3 / 3
Progressive Disclosure	Well-sectioned (Input, Procedure, Verification checklist, Gotchas) with no nested references, but it is a single ~90-line file with no bundle files; the large inline 'Gotchas from real runs' section is content that could be split into a one-level-deep reference.	2 / 3
	Total	10 / 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.

A strong description: third-person voice, concrete actions, explicit 'Use when' triggers, and a clearly bounded niche. It does not pad with concepts Claude already knows.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "delegates `nx migrate` + migrations to a Polygraph child agent per repo, then pushes branches and opens linked draft PRs" — rather than vague language.	3 / 3
Completeness	Explicitly answers both what (migrate repos per child agent, push branches, open linked draft PRs) and when via an explicit "Use when asked to upgrade/migrate..." clause.	3 / 3
Trigger Term Quality	Covers natural phrasings a user would say — "asked to upgrade/migrate multiple repos to a specific nx version" and "nx version bump across repos" — alongside the Polygraph-session trigger.	3 / 3
Distinctiveness Conflict Risk	Niche is narrow and distinct — coordinated multi-repo nx migration via Polygraph child agents with linked draft PRs — unlikely to trigger for unrelated skills.	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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: nrwl/nx
Path: .claude/skills/nx-multi-repo-migrate/SKILL.md
Commit: 0abf7a4

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