// 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.
| name | packmind-cli-list-commands |
| description | 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. |
| license | Complete terms in LICENSE.txt |
| metadata | {"packmind-cli-version":"< 0.27.0"} |
List available Packmind artifacts (standards, commands, skills, packages) via the CLI.
When presenting results to the user, you MUST:
Example output format to show the user:
## Standards (3)
- **my-standard-slug**
Name: My Standard Name
Link: https://<host>/org/myorg/space/global/standards/abc123/summary
- **another-standard**
Name: Another Standard
Link: https://<host>/org/myorg/space/global/standards/def456/summary
| Command | Purpose |
|---|---|
packmind-cli standards list | List coding standards |
packmind-cli commands list | List reusable commands |
packmind-cli skills list | List available skills |
packmind-cli packages list | List available packages |
packmind-cli packages show <package-slug> | Show content of a package |
Ensure packmind-cli is authenticated before running commands:
packmind-cli whoami
If not logged in, authenticate first:
packmind-cli login
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.
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 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.
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.