From Chat Artifact to Command Center: What Claude Cowork Changes
What You'll Learn
How plugins, connectors, and skills in Claude Cowork actually differ -- and which one your legal dashboard should be
How to take a Claude Chat artifact and turn it into a persistent, reusable plugin (not just a one-off prototype)
What the legal command center looks like in practice, including the part where I tried to build it live and had to figure it out in real time
From Chat Artifact to Command Center: What Claude Cowork Change
I had built something useful. I just didn't know where to put it.
My legal triage dashboard existed as a Claude Chat artifact. It worked. I could pull it up, run scenarios through it, use it as a thinking tool. But every session started from scratch. No persistence. No workflow integration. Just a prototype I kept rebuilding.
Then I spent a Friday with my friend Alexander Irschenberger. who knows Claude Cowork. He showed me where the dashboard actually belonged.
My first challenge was figuring out the vocabulary.
Cowork gives you three things:
plugins
connectors
skills.
They sound like they might be interchangeable. They are not.
Here is how I now think about the distinction.
A connector is a live data bridge. It links Cowork to an external system -- your email, your contract database, your Slack -- so Claude can read from or write to that system in real time. Connectors are about data flow. They answer the question: what does Claude need access to?
A skill is a reusable instruction set. It tells Claude how to behave in a specific context -- how to analyze a contract, how to triage an incoming request, how to draft a particular clause. Skills are about behavior. They answer the question: what should Claude know how to do?
A plugin is the interface layer. It is the thing you actually use. It combines a skill (the logic) with a connector (the data) into something you can open and run. Plugins are about workflow and can use many connectors and many skills. They answer the question: what am I actually building?
My dashboard was always a plugin waiting to be deployed.
What the transformation looked like
The video below shows you the Chat dashboard and then how it was transformed into a plugin.
The shift wasn't just technical. It changed how I think about what I'm building. A Chat artifact is a prototype. A Cowork plugin is infrastructure.
If you are experimenting in Claude Chat and wondering when to move something into a more permanent setup, here is the question I now ask: is this something I want to run once, or something I want to run repeatedly as part of how legal operates?
One-off analysis stays in Chat.
Repeatable workflows go into Cowork.
The artifact stage is not wasted. It is how you figure out what you actually want to build before you build it properly. I am glad I prototyped in Chat first. I knew what the dashboard needed to do before I tried to make it permanent.
I did not figure out the plugin build instantly. The Field Guide session this week is me working through it so that you don’t have to be confused by the terminology.
If you want to watch the Cowork plugin build in real time -- including the parts where I had to stop and reconsider -- that session is for Field Guide members. Members get the overview video, a PDF walkthrough, and a live build of me converting the Chat dashboard into a working Cowork plugin. The founding rate is still available if you want in.
Join The Field Guide here.
Claude Chat to Cowork - upgrading the legal dashboard explanation.
Speak soon!
