dist-build-migration

Migrate an Nx package to build to a local dist/ directory with nodenext module resolution, exports map, and @nx/nx-source condition.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/dist-build-migration/SKILL.md

Quality

Content

77%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.

This is a highly actionable, well-sequenced migration guide with strong validation and error-recovery loops. Its main weaknesses are verbosity in the rationale prose and a lack of file-level progressive disclosure for such a long skill.

Suggestions

Move the large step 14b codemod procedure into a dedicated reference file (e.g. references/internal-lockdown.md) and link to it from SKILL.md to improve progressive disclosure.

Tighten the "Why" narratives into one-line rationales, keeping the failure symptom and fix but trimming the explanatory prose.

Consider extracting the per-step gotchas (steps 15, 15b, 16) into a compact checklist reference so the main flow stays scannable.

Dimension	Reasoning	Score
Conciseness	The many gotchas are repo-specific and load-bearing, but the prose around them is often expansive with lengthy "Why" narratives and repeated rationale that could be tightened without losing the signal.	3 / 5
Actionability	The body provides copy-paste-ready bash commands, before/after JSON snippets, exact file paths, and parameterized templates that cover the common migration cases concretely.	5 / 5
Workflow Clarity	Steps 0–17 are clearly sequenced with explicit validation checkpoints (e.g. verifying inferred tsbuildinfo outputs) and error-recovery feedback loops mapping failure messages back to specific steps.	5 / 5
Progressive Disclosure	Internal section headers give it reasonable structure, but it is a 590-line monolith with no bundle files; large portions such as the step 14b codemod guide could be split into one-level-deep reference files.	3 / 5
	Total	16 / 20 Passed

Description

62%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 is specific and clearly distinct within the Nx ecosystem, but it omits explicit "when to use" trigger guidance and leans on technical jargon over natural user phrasing. Adding a Use-when clause with plainer trigger terms would lift completeness and trigger-term quality.

Suggestions

Append an explicit trigger clause, e.g. "Use when migrating an Nx package's build output from the shared workspace dist to a per-package dist/."

Soften jargon with natural synonyms users actually say (e.g. "per-package build output", "local build folder") alongside the technical terms.

Spell out the migration's intent in plain language so the trigger reads naturally rather than as a configuration checklist.

Dimension	Reasoning	Score
Specificity	Names the Nx migration domain plus several concrete specifics — "local dist/ directory", "nodenext module resolution", "exports map", and "@nx/nx-source condition" — but stops short of a fully comprehensive enumeration of actions.	4 / 5
Completeness	It gives a clear "what" (migrate an Nx package to a local dist build) but includes no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	"Migrate an Nx package" is a natural phrase a user might say, but the remaining trigger vocabulary (nodenext, exports map, nx-source condition) is technical jargon with missing synonyms and common variations.	3 / 5
Distinctiveness Conflict Risk	The description targets a highly specific Nx monorepo build-layout niche with unique technical triggers, making overlap with other skills minimal.	5 / 5
	Total	15 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (591 lines); consider splitting into references/ and linking	Warning
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	13 / 16 Passed

Repository: nrwl/nx
Path: .claude/skills/dist-build-migration/SKILL.md
Commit: b616fa1

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.