ReddRadar
Agent skill
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.
Install this agent skill to your Project
npx add-skill https://github.com/PackmindHub/packmind/tree/main/.github/skills/packmind-create-package
SKILL.md
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
packageSlugsparameter when creating standards/commands - Web interface: Navigate to the package URL and add items manually
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
PackmindHub/packmind
working-with-playground-app
This skill provides guidance for building UI/UX prototypes in the Packmind playground app. It should be used when creating a new prototype, iterating on an existing prototype, or working with files in apps/playground/. Triggers on mentions of "playground", "prototype", or direct work within the apps/playground/ directory.
PackmindHub/packmind
qa-review
Review a user story implementation against its Example Mapping (EM) specification.
PackmindHub/packmind
packmind-create-command
Guide for creating reusable commands via the Packmind CLI. This skill should be used when users want to create a new command that captures multi-step workflows, recipes, or task automation for distribution to CoPilot.
PackmindHub/packmind
doc-audit
Audit Packmind end-user documentation (apps/doc/) for broken links, outdated CLI references, non-existent concepts, misleading information, and missing coverage. Produces a structured markdown report at project root. Use when docs may have drifted from the codebase, before a release, or on a regular cadence.
PackmindHub/packmind
git-commit-guidelines
Enforce git commit best practices using gitmoji + Conventional Commits format. TRIGGER when creating commits. Ensures quality-gate passes, prevents issue auto-closing (no Close/Fix keywords), includes Co-Authored-By for AI commits, and requires user approval before committing.
PackmindHub/packmind
internal-comms
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
Didn't find tool you were looking for?