// 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.
Check whether newer stable versions of Node.js (24.x line), Nx, or Vite are available and, if so, generate a detailed upgrade plan markdown file at the repo root. Use this skill whenever the user asks to "check for runtime upgrades", "upgrade Node/NX/Vite", "is our Node version current", "plan a Node 24 upgrade", "refresh our runtime stack", "monthly stack check", or anything along those lines โ even if they don't name a specific tool. Also use it when the user wants a recurring/cadence check of build-toolchain currency. Output is a plan only โ does NOT mutate package.json, Dockerfiles, lockfiles, or any other repo file. CI/CD wrappers can invoke this skill to keep the runtime stack fresh.
Reference for Packmind CLI listing commands. This skill should be used when an agent needs to discover available standards, commands, or skills in the Packmind organization.
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 GitLab Duo.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends GitLab Duo's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating coding standards via the Packmind CLI. This skill should be used when users want to create a new coding standard (or add rules to an existing standard) that captures team conventions, best practices, or coding guidelines for distribution to GitLab Duo.
Complete automated onboarding: analyzes codebase, creates package, and generates standards & commands via CLI. Automatic package creation when none exist, user selection when packages are available.
| name | packmind-create-package |
| description | 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. |
| license | Complete terms in LICENSE.txt |
| metadata | {"packmind-cli-version":"< 0.27.0"} |
Create Packmind packagesโlogical collections of standards, commands, and skills that can be distributed together.
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
Verify packmind-cli is available:
packmind-cli --version
If not installed:
npm install -g @packmind/cli
packmind-cli login
List existing packages to identify naming conventions:
packmind-cli packages list
Review the output to:
Before creating, confirm the package details:
Package name: <name>
Description: <description or "none">
Proceed?
Wait for explicit user approval.
Run the CLI command:
packmind-cli packages create "<name>" --description="<description>"
Or without description:
packmind-cli packages create "<name>"
On success:
Created: <slug>
You can see it at: https://<host>/packages/<slug>
You can install it with: packmind-cli install <slug>
| Error | Solution |
|---|---|
| "Not authenticated" | Run packmind-cli login |
| "Network error" | Check connection, retry |
| "Name must be at least 3 characters" | Use a longer name |
After creating a package, content can be added via:
packmind-cli packages add --to package-slug --standard standard-slug parameter when creating standards (use --command or --skill parameter depending on the artefact type)