I Built a Custom Claude Plugin in 20 Min

Building a plugin used to sound like a developer thing. Skills, connectors, commands, all wired together correctly. The kind of project you put off until "later," which is to say never.

I built one in about twenty minutes. No code. Here's how.

Describe it, don't build it

Cowork has a Plugin Create tool, and the whole idea is that you describe your workflow in plain English. That's the input. You're not configuring anything by hand.

From your description, Claude assembles the pieces itself. The skills it needs to know how. The connectors it needs to reach your tools. The commands that fire the whole thing off. It builds the plugin for you, no coding required.

The hard part of building used to be the wiring. Now you just say what you want and the wiring builds itself.

Why this kills the excuse

The reason most people never made a custom plugin wasn't lack of need. It was the setup friction. Assembling all those parts correctly felt like a job, so the generic experience won by default.

Describe-it-and-go removes the friction entirely. If you can explain your workflow to a coworker, you can build a plugin. (And if you can't explain your own workflow, well, that's a separate and slightly concerning conversation.)

Twenty minutes from "I have this repetitive process" to "Claude now does this repetitive process for me." That's the kind of payback that makes you go hunting for more things to automate.

Pick a workflow you do constantly and describe it to the Plugin Create tool today. Twenty minutes from now you'll have your own.