Create a new monorepo package using the create-package CLI
69
52%
Does it follow best practices?
Impact
100%
1.31xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.claude/skills/create-package/SKILL.mdQuality
Discovery
32%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 concise and identifies a specific tool and action but is too minimal to be effective for skill selection. It lacks a 'Use when...' clause, which is critical for Claude to know when to select this skill. It also misses common trigger term variations that users might naturally use.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to add a new package to the monorepo, scaffold a library, or mentions the create-package CLI.'
Include natural trigger term variations such as 'scaffold', 'new library', 'add workspace package', 'init package' to improve matching.
Expand the 'what' portion to mention any additional capabilities like configuring package settings, choosing templates, or setting up dependencies.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names a specific action ('Create a new monorepo package') and a specific tool ('create-package CLI'), but only describes one action rather than listing multiple concrete capabilities. | 2 / 3 |
Completeness | Describes what it does (create a monorepo package using a CLI) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and since the 'what' is also thin, this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'monorepo', 'package', and 'create-package CLI' that users might say, but misses common variations like 'new library', 'add package', 'scaffold', 'init package', or 'workspace package'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'monorepo package' and 'create-package CLI' provides some specificity, but without more context it could overlap with general package creation or scaffolding skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid, focused skill for a single-purpose CLI task. It provides actionable, executable examples and clear structure. The main weaknesses are minor verbosity in the overview/notes sections and the lack of a verification step after package creation.
Suggestions
Trim the Overview section to 1 line — the command's purpose is self-evident from its name and arguments
Add a verification step after creation, e.g., 'Verify: check that `packages/<name>/package.json` exists and `yarn workspaces list` includes the new package'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The overview section explains what the CLI does (generating scaffolding, setting up structure, etc.) which is somewhat unnecessary since the command name and arguments already convey this. The Notes section repeats the prefix behavior already mentioned in Required Arguments. Could be tightened. | 2 / 3 |
Actionability | Provides fully executable bash commands with concrete examples, including the create-package command, adding dependencies, and updating tsconfig references. The example is copy-paste ready with realistic package names. | 3 / 3 |
Workflow Clarity | The 3-step usage pattern is clear and well-sequenced, but there's no validation checkpoint — no step to verify the package was created correctly (e.g., checking the generated files, running a build, or confirming the workspace is recognized). For a scaffolding operation this is acceptable but not ideal. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines with no need for external references, the content is well-organized with clear sections (Overview, Required Arguments, Usage Pattern, Example, Notes). No bundle files are needed for this straightforward skill. | 3 / 3 |
Total | 10 / 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.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
052f4d4
Table of Contents
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.