Best use case
create-package is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Create a new monorepo package using the create-package CLI
Teams using create-package should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/create-package/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How create-package Compares
| Feature / Agent | create-package | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Create a new monorepo package using the create-package CLI
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Create Package Skill
Use this skill when the user asks to create a new package in the monorepo.
## Overview
The `yarn create-package` command automates the creation of new monorepo packages by:
- Generating package scaffolding from the template package
- Setting up the package structure, configuration files, and dependencies
- Creating package.json with the provided name and description
## Required Arguments
- `--name` (or `-n`): The package name. Will be prefixed with "@ocap/" if not provided.
- `--description` (or `-d`): A short description of the package for package.json
## Usage Pattern
1. Ask the user for the package name and description if not provided
2. Run `yarn create-package --name <package-name> --description "<description>"`
3. Add any additional dependencies using `yarn workspace @ocap/<package-name> add <dep>`
## Example
```bash
# Create the package
yarn create-package --name my-package --description "A package for handling my feature"
# Add dependencies if needed
yarn workspace @ocap/my-package add some-dependency @ocap/kernel-agents
```
When adding monorepo dependencies like `@ocap/kernel-agents`, update the TypeScript references:
```jsonc
// packages/my-package/tsconfig.json and tsconfig.build.json
{
"references": [{ "path": "../kernel-agents" }],
}
```
This creates a new package at `packages/my-package` with the name `@ocap/my-package`.
## Notes
- The package name will automatically be prefixed with "@ocap/" if not provided
- The created package is private by default
- The template is located at `packages/template-package/`
- All placeholder values in the template will be replaced with actual valuesRelated Skills
wallet
Use the wallet tools for all balance, send, and sign operations. Supports both ETH and ERC-20 tokens. The away wallet operates autonomously after setup — the home device does not need to be online.
metamask
Use the MetaMask tools to request and interact with wallet capabilities from the MetaMask capability vendor.
discovery
Use the discovery tools to find and use services through a service matcher. Do not rely on prior knowledge of services, providers, or APIs.
update-changelogs
Updates changelogs for all packages with consumer-facing changes.
push
Pushes the current branch to the remote repository.
pr
Creates a pull request for the current branch.
lint-build-test
How to check code by linting, building, and testing.
glossary
How to add entries to the glossary
evm-wallet-docker-e2e
Run the evm-wallet Docker e2e tests (build, start stack, wait for healthy, test, diagnose failures).
commit
Optionally checks, then commits code to the current or a new feature branch.
code-review
How to review code; a pull request, feature branch, local changes etc.
create-pr
Alias for sentry-skills:pr-writer. Use when users explicitly ask for "create-pr" or reference the legacy skill name. Redirects to the canonical PR writing workflow.