A single skill helps you. A plugin helps your whole team. Here's how to package a set of skills into one install and distribute your standards.
A plugin is nothing fancy — it's a tidy collection of skills, each in its own named folder with a SKILL.md inside. Cluster the skills that support the same workflow: a content kit, a research kit, an ops kit.
Keeping each skill in its own folder is the whole structure. Get that right and packaging is trivial.
When you have multiple skills to share, zip the folders together and upload the bundle as a personal plugin. Everyone who installs it gets all the skills at once.
Customize -> Personal plugins -> "+" -> Create plugin
-> Upload plugin -> upload your .zipIf you only have one skill, you don't need a plugin at all. Upload it directly as a skill — either a zipped folder or a single SKILL.md file. Use plugins only when you're bundling several skills together.
Customize -> Skills -> "+" -> Create skill
-> Upload a skill -> upload .zip or SKILL.mdSend the plugin file directly, or commit the skill folders into your project's repository so they travel with the code. Either way, everyone ends up running the same standards — your format, your process, your defaults — without re-explaining anything.
This is the moment a personal habit becomes a team system.
Folder structure, zip steps, and the exact upload paths for both single skills and full plugins.