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.

80

Quality

100%

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

100%

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

A concise, actionable single-file skill that gives per-manager commands with expected results and a clear workflow including verification, with no token waste.

DimensionReasoningScore

Conciseness

Lean body with no conceptual padding about what workspaces or monorepos are; every section delivers commands or concrete facts, assuming Claude's competence.

3 / 3

Actionability

Provides concrete, executable commands per package manager (yarn/npm/bun) alongside the resulting package.json diffs, making guidance copy-paste ready.

3 / 3

Workflow Clarity

Sequences a 4-step workflow including a 'Verify symlinks created' checkpoint, plus a debug example with a reinstall retry loop; the operation is low-risk so the light validation suffices.

3 / 3

Progressive Disclosure

Single-file skill well under 50 lines with clearly organized sections and no external bundle files, qualifying for a 3 under the simple-skills scoring note.

3 / 3

Total

12

/

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, specific description that clearly answers both what the skill does and when to use it, with natural trigger terms and explicit anti-guardrails that reduce conflict risk.

DimensionReasoningScore

Specificity

Names multiple concrete actions ('Link workspace packages', 'wire up their dependencies', 'add it as a dependency', 'fix actual linking') plus specific error strings, matching the score-3 anchor.

3 / 3

Completeness

Explicitly states what ('Link workspace packages in monorepos') and when via a numbered 'USE WHEN' clause with three concrete trigger scenarios.

3 / 3

Trigger Term Quality

Includes natural user phrases like 'cannot find module', 'failed to resolve import', 'TS2307', 'cannot resolve', and 'imports from a sibling package' that users would actually say.

3 / 3

Distinctiveness Conflict Risk

Narrow niche (workspace package linking in monorepos) with explicit error strings and a 'DO NOT patch around with tsconfig paths or manual package.json edits' guardrail that reduces conflict with adjacent skills.

3 / 3

Total

12

/

12

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.