Quick start
Best if you want the shortest path from install to first publish.
For creators
Turn your knowledge into a real marketplace pack
This is the canonical creator guide for Context as Code packs. Start here if you want to understand the workflow, install the CLI, publish your first version, and manage the pack confidently afterwards.
What you can do here
Get set up fast
Follow the quick start if you want the shortest path from zero to your first published pack.
Learn the workflow properly
Use the build and publish guide to understand the CLI, the pack structure, validation, and the hand-off into Creator Studio.
Understand the methodology
If you are still shaping the underlying process or knowledge, the methodology page shows how to move from messy source material to a clean sellable pack.
Best path for a new creator
- Read the quick start so you know the moving parts before you install anything.
- Install the CLI and sign in.
- Create a pack locally and run validation early.
- Publish a first version.
- Use Creator Studio to manage visibility, release notes, and lifecycle.
Choose your route
Three ways into the creator workflow
Pick the entry point that matches where you are right now.
Build and publish
Best if you want the fuller CLI, structure, and management workflow explained step by step.
Pack authoring methodology
Best if you are still turning raw notes or practical experience into something reusable enough to sell.
Troubleshooting themes
I can sign in but I cannot publish
Check which active account you are operating from in the marketplace. Publishing permissions are account-based, not just user-based.
Validation is failing
Start by checking your manifest fields, version format, required pack docs, and content structure. Validation should be treated as part of the authoring workflow, not a last-minute gate.
The pack published but the listing needs work
That is expected. Use Creator Studio after publish to refine release notes, visibility, and listing presentation without changing the canonical artifact contract.
I am not sure whether this should be a pack yet
If the material is still messy, collect it first. The strongest packs come from a repeatable process or body of knowledge that is ready to be curated into a reusable product.
ctx pack install is targeting the wrong directory
Run pack install from the root of your git repo, or pass --repo-root explicitly. The CLI walks up the directory tree to find a context.yaml; if you are inside a parent repo that already has one installed, it will find that instead.
Frequently asked questions
Should I start in the marketplace or the CLI?
Start in the marketplace if you need to understand the flow and confirm your account context. Start in the CLI when you are ready to initialize an authoring workspace and create a real pack.
Do I need an organisation account to publish?
Not necessarily. You can publish from whichever active account has the right capabilities. Use an organisation account when the pack should belong to a shared team workspace.
What belongs in a good first pack?
A focused, repeatable process or body of knowledge with clear value. Packs are stronger when they solve a specific problem instead of trying to include everything at once.
What happens after I publish?
The new version becomes part of your pack history and can then be managed through Creator Studio. That is where you refine the user-facing side of the listing.