CtrlK
BlogDocsLog inGet started
Tessl Logo

link-workspace-packages

Link workspace packages in monorepos (npm, yarn, 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.

71

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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.

A compact, highly actionable command reference with executable snippets for each package manager and a clear workflow. Verification is present but could be made into an explicit feedback loop, and the file is slightly long to qualify for the simple-skill progressive-disclosure exception.

DimensionReasoningScore

Conciseness

Largely lean command reference with no padding over concepts Claude already knows; the Examples section lightly repeats the npm command form already shown in the npm section, a minor trim opportunity keeping it just below 5.

4 / 5

Actionability

Copy-paste-ready commands for all three managers (yarn workspace add, npm install --workspace, bun add) with the resulting package.json snippet and a concrete debug workflow, fully covering the common cases.

5 / 5

Workflow Clarity

A clear 4-step sequence including a verify step ('Verify symlinks created in consumer's node_modules/'), but the verification is vague and lacks a fix-and-retry feedback loop, so it is not a 5.

4 / 5

Progressive Disclosure

Well-organized into clear sections (Detect Package Manager, Workflow, per-manager, Examples, Notes) with no nested references; at ~95 lines it slightly exceeds the simple-skill line budget, so a fully self-contained single file lands at 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

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

A strong, well-targeted description with explicit what/when structure and excellent natural trigger terms including real error messages. The only issue is second-person voice in the USE WHEN clause, which costs a specificity point per the rubric.

DimensionReasoningScore

Specificity

Names concrete actions ('Link workspace packages', 'wire up their dependencies', 'add it as a dependency', 'fix actual linking') across npm/yarn/bun, which is several specific actions (base 4), but the description uses second person ('USE WHEN: (1) you just created'), which per the rubric reduces specificity by 1.

3 / 5

Completeness

Explicitly answers both 'what' (link workspace packages in monorepos) and 'when' with a numbered USE WHEN clause containing concrete trigger scenarios, matching the 5 anchor.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including exact error strings users would paste ('cannot find module', 'failed to resolve import', 'TS2307', 'cannot resolve') plus the @org/* pattern and 'sibling package' phrasing.

5 / 5

Distinctiveness Conflict Risk

Clear niche (workspace package linking across the three named managers) with distinct triggers (@org/* resolution errors) plus negative boundary guidance ('DO NOT patch around with tsconfig paths'), minimizing conflict risk.

5 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
leboncoin/spark-web
Reviewed

Table of Contents

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.