Plugins: Giving Claude Hands

Plugins: Giving Claude Hands

By Cynthia Schomp · Fractional CTO

A skill tells Claude how to think. A plugin gives it something to do.

That's the distinction that changes what AI-assisted work actually looks like day to day. One-line reminder on skills: a skill is a configuration file you load before a session that tells Claude your rules, your voice, your process. It shapes how Claude thinks and outputs. It doesn't touch your systems.

That's the gap skills can't close on their own.

The Problem Skills Can't Solve

You can load a perfectly tuned brand skill and Claude will write in your voice, follow your structure, avoid every word on your banned list. But it can't send the email. It can't pull last month's numbers from your analytics dashboard. It can't log a note in your CRM, check your calendar, or post a draft to your content queue.

A skill is knowledge and process. It has no reach.

If you want Claude to do something in the real world, something has to hand it the keys.

What a Plugin Actually Is

A plugin is a bundle. It packages one or more skills together with tool connections: your email client, your CRM, your project management platform, your analytics stack. Where a skill tells Claude how to think and output, a plugin hands it the ability to actually touch those systems.

Think about what that means for an agency. You have a client reporting workflow. It currently means pulling numbers from three platforms, writing a summary, formatting it, and sending it. With the right skill loaded, Claude writes the summary in your voice. Add a plugin that connects to your analytics platform and your email client, and Claude pulls the numbers, writes the summary, and drafts the send.

That's not a hypothetical. That's what the right plugin configuration does.

One Install, Department-Level Capability

One plugin can give Claude a full department's worth of capability. A client success plugin might bundle your voice skill, your reporting process, your CRM connection, and your email client all together. Load it once. Every session that needs client communication starts with all of that already in place.

You stop rebuilding context every session. You stop switching between five tools to get one thing done. Claude starts the session already knowing the rules, already connected to the systems, already ready to act.

What Changes Day to Day

The operational shift is less obvious than it sounds. It's not "Claude does everything now." It's that the prep work disappears.

Before a plugin-connected workflow: open Claude, load the skill, copy in the relevant data, paste the output somewhere, go do the actual action manually. After: the retrieval, the formatting, and the action are part of the same request.

The sessions get shorter. The context gaps between your AI tool and your actual stack close. That's the practical version of what plugins do. Not magic. Just removed friction.

Still Claude's Sandbox

Everything I've described lives inside Claude's settings menu. The skill shapes how Claude thinks. The plugin extends that into your connected tools.

There's a way to go further. A way to connect Claude not just to SaaS tools via plugin, but to infrastructure you own entirely. Your servers. Your databases. Your automation stack. Systems with no plugin in a marketplace, because you built them yourself.

That's in email 06. Next email is the week-in-review: what it actually looks like when Claude runs your workflow across a full seven days.

If you missed any emails in this series, the full archive is waiting: hellocyn.com/archive -- every issue, in order, yours to read whenever.

-- Cynthia Fractional CTO · Schomp.ai · The CTO's Desk

Reply to this if you're building something similar. I read every reply.