How do I install the Packmind Create Package skill?

Run npx skillmds@latest add tomevault-io/packmind-create-package in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Packmind Create Package safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Packmind Create Package?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Packmind Create Package free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Packmind Create Package?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Packmind Create Package by tomevault-io

Name: Packmind Create Package
Author: tomevault-io

Packmind Create Package

Guide for creating Packmind packages via the CLI. This skill should be used when users want to create a new package to organize standards, commands, and skills for distribution. Use when this capability is needed.

tomevault-io 6f2ff2f 2 files · 3.2 KB Updated Sep 17, 2026

File contents

Package Creator

Create Packmind packages—logical collections of standards, commands, and skills that can be distributed together.

About Packages

A Package groups related artifacts by technology, domain, team, or architectural layer. Instead of managing individual items, packages let you distribute related content as a single unit.

Examples: frontend, backend-api, nestjs, e2e

Prerequisites

Verify packmind-cli is available:

packmind-cli --version

If not installed:

npm install -g @packmind/cli
packmind-cli login

Workflow

Step 1: Check Existing Packages

List existing packages to identify naming conventions:

packmind-cli install --list

Review the output to:

Avoid duplicate or conflicting names
Follow existing naming conventions (lowercase, kebab-case slugs)
Understand how packages are organized in this workspace

Step 2: Confirm with User

Before creating, confirm the package details:

Package name: <name>
Description: <description or "none">

Proceed?

Wait for explicit user approval.

Step 3: Create the Package

Run the CLI command:

packmind-cli packages create "<name>" --description="<description>"

Or without description:

packmind-cli packages create "<name>"

Expected Output

On success:

Created: <slug>
You can see it at: https://<host>/packages/<slug>
You can install it with: packmind-cli packages install <slug>

Naming Guidelines

Name: Human-readable, can include spaces (e.g., "Backend API")
Slug: Auto-generated from name, lowercase with hyphens (e.g., "backend-api")
Collision handling: If slug exists, server auto-increments (e.g., "frontend-2")

Troubleshooting

Error	Solution
"Not authenticated"	Run `packmind-cli login`
"Network error"	Check connection, retry
"Name must be at least 3 characters"	Use a longer name

Next Steps

After creating a package, content can be added via:

MCP tools: Use packageSlugs parameter when creating standards/commands
Web interface: Navigate to the package URL and add items manually

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: packmind-create-packagedescription: Guide for creating Packmind packages via the CLI. This skill should be used when users want to create a new package to organize standards, commands, and skills for distribution. Use when this capability is needed.---# Package CreatorCreate Packmind packages—logical collections of standards, commands, and skills that can be distributed together.## About PackagesA **Package** groups related artifacts by technology, domain, team, or architectural layer. Instead of managing individual items, packages let you distribute related content as a single unit.Examples: `frontend`, `backend-api`, `nestjs`, `e2e`## PrerequisitesVerify packmind-cli is available:```bashpackmind-cli --version```If not installed:```bashnpm install -g @packmind/clipackmind-cli login```## Workflow### Step 1: Check Existing PackagesList existing packages to identify naming conventions:```bashpackmind-cli install --list```Review the output to:- Avoid duplicate or conflicting names- Follow existing naming conventions (lowercase, kebab-case slugs)- Understand how packages are organized in this workspace### Step 2: Confirm with UserBefore creating, confirm the package details:```Package name: <name>Description: <description or "none">Proceed?```Wait for explicit user approval.### Step 3: Create the PackageRun the CLI command:```bashpackmind-cli packages create "<name>" --description="<description>"```Or without description:```bashpackmind-cli packages create "<name>"```### Expected OutputOn success:```Created: <slug>You can see it at: https://<host>/packages/<slug>You can install it with: packmind-cli packages install <slug>```## Naming Guidelines- **Name**: Human-readable, can include spaces (e.g., "Backend API")- **Slug**: Auto-generated from name, lowercase with hyphens (e.g., "backend-api")- **Collision handling**: If slug exists, server auto-increments (e.g., "frontend-2")## Troubleshooting| Error | Solution ||-------|----------|| "Not authenticated" | Run `packmind-cli login` || "Network error" | Check connection, retry || "Name must be at least 3 characters" | Use a longer name |## Next StepsAfter creating a package, content can be added via:1. **MCP tools**: Use `packageSlugs` parameter when creating standards/commands2. **Web interface**: Navigate to the package URL and add items manually---> Converted and distributed by [TomeVault](https://tomevault.io/claim/packmindhub) — claim your Tome and manage your conversions.

Frequently asked questions