link-workspace-packages

Link workspace packages in monorepos (npm, yarn, pnpm, bun). USE WHEN: (1) you just created or generated new packages and need to wire up their dependencies, (2) user imports from a sibling package and needs to add it as a dependency, (3) you get resolution errors for workspace packages (@org/*) like "cannot find module", "failed to resolve import", "TS2307", or "cannot resolve". DO NOT patch around with tsconfig paths or manual package.json edits - use the package manager's workspace commands to fix actual linking.

Quality

91%

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

82%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 tightly written, actionable across all four package managers, and well-structured with a detection step, per-manager command recipes, and useful hoisting notes. Main gaps are mild command duplication in Examples and a verification step that lacks an explicit re-run-on-failure feedback loop.

Suggestions

Remove or differentiate the 'Examples' section entries that merely repeat the pnpm/npm commands already shown above, keeping only the genuinely new multi-package and debug cases.

Tighten workflow step 4 into an explicit feedback loop, e.g. 'Verify symlink exists at <consumer>/node_modules/@org/<pkg>; if missing, run the manager's install command and re-check'.

Consider moving the per-manager hoisting/PnP notes into a short reference table so the main flow stays scannable.

Dimension	Reasoning	Score
Conciseness	Lean and assumes Claude's competence (no explaining what monorepos or package managers are), but the 'Examples' section repeats the pnpm and npm commands already shown in the per-manager sections, a minor trim opportunity.	4 / 5
Actionability	Fully executable, copy-paste-ready commands for all four managers, each paired with the resulting package.json snippet, plus lockfile detection and a debug flow covering the common cases.	5 / 5
Workflow Clarity	A clear 4-step workflow is present including a verify step ('Verify symlinks created in consumer node_modules/'), but the verification is stated without an explicit error-recovery feedback loop or the exact check command.	4 / 5
Progressive Disclosure	Well-organized with clear per-manager section headers and self-contained content requiring no external references, but at ~120 lines with no bundle files it does not meet the simple-skill exception for a 5, and the inlined Examples/Notes could be slightly tighter.	4 / 5
	Total	17 / 20 Passed

Description

100%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 exemplary: it states the capability concisely, gives three concrete trigger scenarios with real error-string keywords, and draws a clear boundary against tsconfig/manual-edit workarounds. It fully satisfies what/when/distinctiveness without padding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (link workspace packages, wire up dependencies, add a sibling as a dependency, fix resolution errors via the package manager's workspace commands) with comprehensive coverage across the domain.	5 / 5
Completeness	Explicitly answers both what ('Link workspace packages in monorepos (npm, yarn, pnpm, bun)') and when via a numbered 'USE WHEN:' clause with three concrete trigger scenarios.	5 / 5
Trigger Term Quality	Comprehensive natural-term coverage including exact error strings users encounter ('cannot find module', 'failed to resolve import', 'TS2307', 'cannot resolve') plus synonyms like 'sibling package' and '@org/*'.	5 / 5
Distinctiveness Conflict Risk	Clear niche (workspace package linking in monorepos) with distinct triggers and explicit boundary guidance ('DO NOT patch around with tsconfig paths or manual package.json edits'), minimizing overlap with adjacent skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: nrwl/nx
Path: .agents/skills/link-workspace-packages/SKILL.md
Commit: 9064aa9

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