Chapter 15 · CLI
Creating plugins: manifest, components and publishing
Creating your own plugin lets you package capabilities the team needs repeatedly: commands, agents, skills and hooks. The manifest defines the package, and evals verify it works before publishing.
Video
Steps
- Start with the manifest: name, version, description and components. A clear name and precise description help users know when to use it.
- Add components gradually: one command or one agent first, verifying they load before expanding.
- Check dependencies between components and version compatibility, and document special requirements in the readme.
- Before publishing, run evals demonstrating the components do what is promised, and publish to the marketplace your team uses.
Common pitfall: A plugin published without evals can fail for others exactly when they rely on it; testing before publishing is part of the product.
Hands-on exercise: Create a plugin skeleton with a manifest and one command. Load it locally and verify the command appears.
Filmed demo · Video is added in the media phase
Recap
Comprehension check
What is the manifest role in a plugin?
Recap
- The manifest defines the package
- Add components gradually and verify
- Evals before publishing