create-package
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 lacks depth. It is missing a 'Use when...' clause, which is critical for Claude to know when to select this skill. The single action described and limited trigger terms make it harder to distinguish from other package-related skills.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user wants to scaffold, initialize, or add a new package to the monorepo.'
Include natural trigger term variations such as 'scaffold', 'new library', 'add workspace package', 'init package', or 'bootstrap'.
Expand the 'what' portion to mention specific capabilities like generating boilerplate, configuring build tools, or setting up package.json defaults.
| 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 has no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also thin enough to warrant 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', or 'workspace package'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of 'create-package CLI' and 'monorepo' provides some specificity, but 'create a new package' could overlap with other package-related skills like publishing, configuring, or general scaffolding tools. | 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 CLI command. It provides actionable, executable examples and is well-structured. The main weaknesses are minor verbosity in the overview/notes sections and the lack of any validation step after package creation (e.g., verifying the package directory exists or running a build check).
Suggestions
Add a validation step after package creation, e.g., 'Verify the package was created: ls packages/<package-name>/package.json' or run a build check.
Trim the Overview section to remove explanations that are obvious from the command itself — the bullet points about 'generating scaffolding' and 'setting up structure' are redundant.
| 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 itself is self-explanatory. 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 sequenced, but there's no validation checkpoint — no step to verify the package was created correctly, no mention of checking for errors from the create-package command, and no feedback loop if something goes wrong. | 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. | 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.
- Repository
- MetaMask/ocap-kernel
- Commit
a3eff0e
- 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.