The Meta Plugin

Now we arrive at the part that should make you sit up straight in your chair. There is a plugin that creates other plugins. It is called the meta plugin, and it is exactly as powerful as it sounds.

The meta plugin takes your plain-English description of a workflow — dictated, typed, or pasted — and turns it into a deployable plugin with skills, commands, and connector definitions. You do not need to know how to write a skill specification. You do not need to understand MCP connector syntax. You describe what you do, how you do it, and what tools you use, and the meta plugin does the engineering.

This is not a toy. This is how you turn institutional knowledge — the workflows in your head that you have never bothered to document because they are "just how I do things" — into reusable AI infrastructure.

1. 1. Describe Your Workflow In plain English, dictate or type everything about the workflow you want to automate. Don't worry about technical details — just explain what you do, step by step, including the tools you use and the decisions you make. Be verbose. Be specific. Mention the edge cases. Mention the "oh, and also" steps that you do subconsciously but never write down.
2. 2. Let the Meta Plugin Analyze It identifies what capabilities need to be created from scratch, which existing tools can be connected via MCP, and what slash commands would be most useful for day-to-day invocation. The meta plugin is doing requirements analysis on your verbal description — decomposing your workflow into automatable components.
3. 3. Review the Generated Components Check the skills (do they capture your actual workflow?), commands (are the trigger words intuitive?), and connectors (do you need all the MCPs it suggests?). Trim aggressively — less is more. A plugin with 3 focused skills outperforms one with 12 vague skills every time.
4. 4. Deploy and Iterate Install the plugin in Co-Work (upload as zip) or import into Claude Code. Run it for a month before declaring it "done." Skills should evolve as your workflow evolves. The first version is a starting point, not a finished product.

Let me give you a concrete scenario because the abstract description undersells how practical this is.

You run a solopreneur consulting business. You do client onboarding, proposal writing, project scoping, invoicing, and follow-up. Each of those is a workflow with specific steps, specific tools, and specific decision points. You have never documented any of it because it all lives in your head.

You sit down with the meta plugin and describe each workflow. "When I onboard a new client, I first create a shared folder, then send them an intake questionnaire, then schedule a kickoff call, then create a project brief from the questionnaire responses, then set up milestones in my project tracker." The meta plugin hears this and creates: a skill for client onboarding that knows the sequence, a /new-client command that triggers the workflow, and connectors for your file storage and project management tools.

Repeat for proposals, scoping, invoicing, and follow-up. In a couple of hours, you have a custom plugin that encodes every workflow in your business. You have turned "how I do things" into "how my AI team does things." That is leverage.