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 with Tessl CLI
npx tessl i github:cteyton/packmind --skill packmind-create-package81
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillAgent success when using this skill
Validation for skill structure
CLI command construction and workflow scripting
CLI availability check
100%
100%
Auth/login reference
0%
85%
Lists existing packages
100%
100%
User confirmation step
0%
100%
Correct create command
100%
100%
origin-skill flag
0%
100%
Human-readable name
100%
100%
Slug auto-generation
0%
100%
No collision handling code
0%
100%
Description parameter
87%
100%
Valid bash script
100%
100%
Prerequisites, naming conventions, and setup guide
CLI version check
100%
100%
Install command
100%
100%
Login step
0%
100%
List packages step
30%
100%
Naming convention review
12%
100%
Kebab-case slug format
80%
100%
Name vs slug distinction
62%
100%
origin-skill flag
0%
100%
User confirmation step
0%
0%
Collision auto-increment
0%
100%
Next steps
100%
100%
Package URL output
0%
100%
Post-creation content population via MCP tools
packageSlugs parameter
0%
100%
packageSlugs value
0%
100%
Web interface alternative
75%
100%
origin-skill flag
0%
100%
List packages step
0%
100%
User confirmation step
0%
0%
Slug format shown
37%
100%
Package URL reference
0%
100%
MCP tool standard creation
0%
100%
Human-readable name
100%
100%
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.