A Lot Out of the Gates: Plugins, Connectors and Why You're Still the Builder

Claude gives you a lot out of the gates, and most of it sits in the Customize screen of the desktop app where you might never go looking. Skills for productivity (planning your tasks and projects, following up with people), product management, running a small business, HR, legal, sales, marketing, customer support. There is so much in there. I know a number of people who've used artifacts, projects and scheduled tasks to make Claude the backbone of their entire business. I've gone down that route a little bit myself, and I'll come back to it later.

Scheduled tasks are worth a look on their own. Remember what we did with GitHub and /loop? You could do that as a scheduled task instead, and just ask for it:

create a scheduled task for me that checks GitHub, works on the issue, and does all the stuff we just said

Then plugins. A plugin wraps up the commands, skills, agents and settings we've been talking about so you can share them. If I made a Rob plugin for my Elixir projects and gave it to you, you'd get all my skills, namespaced, so my test skill would be rob:elixir-test. You can grab plugins with npx skills, which drops them in for you. And connectors hook Claude up to Gmail, Google Drive and anything else you've got, including MCP servers you write yourself, in the desktop app and the CLI.

So how do you go from "yeah, I've heard of that" to pro level? You know these tools are there, so when a task comes up you remember you can automate it, or add a plugin, or put the whole thing together. We're still the builders here. Yes, you can turn on ultrathink, ask for a CRM, go to bed and wake up to one. Is it something people want to use, or a buggy mess that's going to crash? I don't know. Finding that out is your job, and that's the end of our dive into the back-end stuff of Claude.