create-package

Create a new monorepo package using the create-package CLI

1.31x

Quality

—

Does it follow best practices?

Impact

100%

1.31x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

87%

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

The body is concise and highly actionable with executable examples and clean sectioning for a simple skill; its main gap is the absence of an explicit validation/verification step after package creation and tsconfig edits.

Suggestions

Add a verification checkpoint after package creation (e.g. run a build or check that `packages/<name>` exists and imports resolve).

Make the tsconfig reference update a numbered step in the Usage Pattern rather than only an inline example note.

Trim the duplicated '@ocap/ prefix' note from the Notes section since it is already stated under Required Arguments.

Dimension	Reasoning	Score
Conciseness	The body is lean and task-focused with minimal conceptual padding; the only mild redundancy is the @ocap/ prefix note restated in Notes, but overall every token earns its place.	3 / 3
Actionability	It provides fully executable, copy-paste-ready commands (`yarn create-package --name ...`, `yarn workspace ... add`) plus a concrete tsconfig references snippet.	3 / 3
Workflow Clarity	The Usage Pattern gives a clear 3-step sequence, but for an operation that creates packages and edits tsconfig references there is no explicit validation/verification checkpoint, which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	A simple single-task skill under 50 lines with no bundle files; it is well-organized into clear sections (Overview, Required Arguments, Usage Pattern, Example, Notes), satisfying the simple-skill exception.	3 / 3
	Total	11 / 12 Passed

Description

57%

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 specific and clearly scoped to a single CLI-driven task with a distinct niche, but it lacks an explicit 'Use when...' trigger clause and lists only one action, limiting completeness and trigger coverage.

Suggestions

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

Broaden trigger terms to cover natural variations like 'scaffold a package', 'add a new package', or 'generate a package'.

List the concrete capabilities briefly (scaffolding, configuration, dependencies) to raise specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (monorepo package) and a concrete action ('Create a new monorepo package using the create-package CLI'), but lists only a single action rather than multiple specific capabilities.	2 / 3
Completeness	It states what the skill does, but there is no explicit 'Use when...' trigger clause in the description, which caps completeness at 2 per the guidelines.	2 / 3
Trigger Term Quality	'create a new package' and 'monorepo package' are natural terms a user might say, but coverage of common variations (e.g. 'scaffold', 'add a package') is missing.	2 / 3
Distinctiveness Conflict Risk	The named CLI ('create-package') and the monorepo-package niche form a distinct trigger unlikely to fire for unrelated skills.	3 / 3
	Total	9 / 12 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
Commit: 03b6a62

Reviewed: 13 days 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.