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

88%

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.

A concise, highly actionable reference card covering all four package managers with executable commands and expected results. The main gap is workflow validation: the verify step is vague and lacks an explicit feedback loop for when linking or install fails.

Suggestions

Make the verification step concrete with an executable check, e.g. step 4: `ls consumer/node_modules/@org/<package>` (or `pnpm ls --filter`) and confirm the symlink resolves to the provider directory.

Add an error-recovery feedback loop after install: if the import still fails, re-run the manager's install, confirm the workspace dependency entry is present, and only then retry resolution.

De-duplicate Example 1 (it reuses the exact pnpm --filter command already shown in the pnpm section); replace it with a distinct case or fold its value into the pnpm section to save tokens.

Dimension	Reasoning	Score
Conciseness	Lean reference card that assumes Claude's competence: short per-manager sections with just the command and expected package.json result, no explanations of what monorepos or workspaces are. Every section earns its place.	3 / 3
Actionability	Provides fully executable, copy-paste-ready commands for each manager (pnpm add --workspace, yarn workspace add, npm install --workspace, bun add) alongside the exact resulting dependency entries.	3 / 3
Workflow Clarity	The four-step workflow is sequenced and includes a verify step, but validation is implicit ('Verify symlinks created in consumer node_modules/') with no concrete command, and there is no error-recovery feedback loop for install/package.json-mutating operations, capping the score at 2.	2 / 3
Progressive Disclosure	Single, well-organized SKILL.md with clearly delimited sections (Detect Package Manager, Workflow, one section per manager, Examples, Notes) separated by headers and rules; no external references are needed for this focused scope, so well-organized inline content suffices.	3 / 3
	Total	11 / 12 Passed

Description

90%

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, well-targeted description with explicit trigger guidance and natural error-term keywords. The only weakness is second-person phrasing in the USE WHEN clause, which lowers the specificity score.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions ('Link workspace packages', 'wire up their dependencies', 'add it as a dependency', 'fix actual linking'), but the USE WHEN clause is written in second person ('you just created', 'you get resolution errors'), which incurs the -1 specificity penalty per the rubric guidelines.	2 / 3
Completeness	Clearly states what the skill does ('Link workspace packages in monorepos (npm, yarn, pnpm, bun)') and provides an explicit USE WHEN clause with three concrete trigger scenarios, satisfying both what and when.	3 / 3
Trigger Term Quality	Strong coverage of natural terms a developer would encounter or paste: 'cannot find module', 'failed to resolve import', 'TS2307', 'cannot resolve', plus '@org/*' and 'sibling package'.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (workspace package linking) with manager-specific commands and distinctive error-code triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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: 0abf7a4

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