Creating Packs & Editions
Build your own Skill Packs or create customized editions of existing ones. Share curated skill bundles with your team or the community.
Two Ways to Create
Create a Base Pack
Start from scratch with your own curated collection of skills and shared context. Best when you have a unique workflow to share.
Create New PackCreate an Edition
Fork an existing pack and customize it for your context. Add company guidelines, swap skills, or adjust the shared context.
Find a Pack to ForkCreating a Base Pack
Define the Pack
Give your pack a name, slug, description, and category. The slug must be unique across all packs.
Add Skills
Add skills by referencing existing catalog skills or embedding custom content. Each skill can have a role (primary, helper) and dependencies.
Add Shared Context
Create context files that apply to all skills. These are merged into each skill when users import the pack.
Publish
Set visibility to public to share with the community, or keep it private for personal use.
Creating an Edition
Editions let you customize an existing pack for your specific context. To create an edition:
- 1.Navigate to any base pack's detail page
- 2.Click "Create Edition"
- 3.Give your edition a unique name and description
- 4.Add edition context—what makes your version different
- 5.Modify skills, add new ones, or remove existing ones
- 6.Publish your edition
Your edition links back to the base pack, allowing users to compare changes.
Shared Context Files
Context files are markdown documents that provide shared knowledge:
Each context file gets a filename and optional description. When the pack is imported, all context is merged into each skill.
Best Practices
Focus on a Use Case
Packs work best when they target a specific workflow, not a general collection.
Use Catalog Skills
Reference catalog skills when possible—they're versioned, validated, and maintained.
Keep Context Focused
Shared context should be genuinely shared. Don't bloat it with skill-specific info.
Write Good Descriptions
Clear descriptions help users find and evaluate your pack quickly.
Version Thoughtfully
Bump versions when you make breaking changes. Users rely on version stability.
Respond to Signals
Pay attention to adoption and satisfaction. Low scores may indicate issues.
Sharing with the Community
Public packs appear in the catalog for anyone to discover and use. When you publish a pack:
- •Other users can import your skills and shared context
- •Community members can create editions based on your pack
- •You receive signals: adoptions, recommendations, satisfaction scores
- •Your pack appears in search results and category listings