create-package

Create a new monorepo package using the create-package CLI

1.31x

Quality

64%

Does it follow best practices?

Impact

100%

1.31x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/create-package/SKILL.md

Quality

Content

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

The body is highly actionable with executable commands and examples, and is well structured for a simple single-purpose skill. Its main weakness is the absence of any validation or verification step in the workflow.

Suggestions

Add a verification step to the Usage Pattern, e.g. 'Confirm the package exists at packages/<name> and that yarn workspaces info lists it.'

Pull the TypeScript-references update guidance out of the Example section into its own short section so it is easier to discover.

De-duplicate the '@ocap/' prefix note between Required Arguments and Notes to tighten the content.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence, with only minor redundancy such as the '@ocap/' prefix note restated in both Required Arguments and Notes, fitting 'efficient; minor instances that could be trimmed' rather than the fully lean score 5.	4 / 5
Actionability	It provides copy-paste-ready commands ('yarn create-package --name ... --description ...', 'yarn workspace ... add ...') plus a concrete tsconfig references example, covering the common cases of creating a package, adding deps, and wiring references.	5 / 5
Workflow Clarity	The three-step Usage Pattern is clearly sequenced, but there are no validation or verification checkpoints (e.g. confirming the package was created), matching 'steps listed but validation gaps; checkpoints missing'.	3 / 5
Progressive Disclosure	Sections are well organized with clear headers and no unnecessary external references, but the TypeScript-references guidance is tucked inside the Example section rather than surfaced, a minor organization gap keeping it below 5.	4 / 5
	Total	16 / 20 Passed

Description

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

The description clearly conveys what the skill does and targets a distinct niche, but it lacks an explicit 'when to use' trigger clause and offers only one concrete action with limited keyword coverage. Adding a 'Use when...' clause and a few synonym triggers would lift the weaker dimensions.

Suggestions

Append an explicit trigger clause, e.g. 'Use when the user asks to create, add, or scaffold a new package in the monorepo.'

Broaden trigger keywords with natural synonyms such as 'add a package', 'scaffold a package', or 'new monorepo package'.

Consider naming one or two more concrete actions (e.g. scaffolding from a template, wiring TypeScript references) to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain and one concrete action ('Create a new monorepo package') but lists no further actions, matching the '1-2 concrete actions, not comprehensive' anchor rather than the multi-action score 4.	3 / 5
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 3.	3 / 5
Trigger Term Quality	'Create a new monorepo package' is a natural phrase a user would say, but coverage is limited to a single trigger concept with no synonyms or variations like 'add' or 'scaffold a package'.	3 / 5
Distinctiveness Conflict Risk	'Create a new monorepo package using the create-package CLI' carves a distinct niche with only minor overlap risk against other scaffolding skills, fitting 'mostly distinct' rather than the fully distinct score 5.	4 / 5
	Total	13 / 20 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: MetaMask/ocap-kernel
Path: .claude/skills/create-package/SKILL.md
Commit: 37db357

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