3 Claude Skills That Quietly Run My Business

Most of the AI demos people show me are impressive for about thirty seconds and then never get used again. The things that have actually stuck around in my own business are the opposite: small, unglamorous, and repeated so often I'd forgotten they were AI at all. Here are three of them, exactly as they run today.

What a "skill" actually is

A skill is instructions plus a script, bundled together. Instead of asking Claude to figure out the same task from scratch every time, a skill pairs a written playbook (when to use it, what order to do things in) with the actual code that does the reliable, repeatable parts. Claude reads the playbook and runs the script. That combination is what makes these three worth trusting with real, recurring work instead of a one-off chat message.

1. The one that sorts my inbox before I open it

My Gmail gets triaged before I've had coffee. A skill reads unlabelled email and sorts it into three buckets: Action Required, Waiting On, and Reference. It works across more than one account, so I'm not manually checking each inbox to see what actually needs me versus what's just noise.

The point isn't that it replaces reading my email. It's that I open Gmail already knowing what's urgent instead of scanning forty subject lines to find the three that matter.

2. The one that writes my morning brief

Every morning, before I've opened my laptop properly, something has already read the state of my business. A Chief of Staff skill pulls from my calendar, my Gmail, a business dashboard sheet, and recent files, then writes a short brief: priorities for the day, drafts waiting on my review, anything that needs my attention. It doesn't decide anything for me. It just makes sure I'm not starting the day by reconstructing what happened yesterday from memory.

If a source is missing or a file isn't where it's expected, it says so instead of guessing. That's the part that actually makes it trustworthy enough to read first thing, rather than something I have to double-check before I believe it.

3. The one drafting this very post

This is the most honest example I can give you, because it's true right now. A skill picks the next topic from a backlog, reads a couple of my existing posts to match my voice and structure, writes a full draft with the house rules applied (no fabricated stats, no invented quotes, no filler), and opens it for my review. It never publishes on its own. Nothing goes live until I've read it, checked the facts, and approved it.

That review step isn't a limitation I'm apologising for. It's the design. A skill that writes content without a human checking it before it's public is a skill I wouldn't run.

What makes these actually work, not just cool demos

The common thread across all three is narrow scope. None of them is "an AI that runs my business." Each one does one specific, well-defined job, reads only the tools it's been given access to through connectors, and hands off to me before anything customer-facing or public happens. Broad, do-everything automation is where these things get unreliable. Narrow and repeatable is where they get boring, in the best way.

If you're setting any of this up for the first time, the order matters more than people expect. I laid out the sequence that made the biggest difference for me in the nine settings that turn Claude into your team: get memory and connectors right first, and skills like these become far more useful, not less.

Where to start if you want your own

Don't start by trying to build all three. Pick the one task you already do the same way, on a predictable cadence, every single week. That repetition is the signal it's worth turning into a skill. Once you've got a task like that identified, pairing it with a schedule (I covered how in recurring tasks in Claude Cowork) is what turns it from "a thing I asked Claude to do once" into "a thing that just happens now."

FAQ

What is a Claude skill?

A skill is a bundle of written instructions and a script that Claude runs together for a specific, repeatable task, like triaging email or drafting a status report. Instead of re-explaining the task every time, you set it up once and Claude follows the same playbook and runs the same reliable code each time it's triggered.

Do I need to be technical to set one up?

Not to use an existing skill, no, that's mostly plain-English instructions plus a click to run it. Building a brand new skill from scratch benefits from some comfort getting hands-on, closer to the Claude Code end of things, but plenty of non-technical business owners get skills built for them and just run them afterwards.

Is it safe to let AI handle my inbox or publish content automatically?

Sorting and labelling email is low-risk because nothing external happens, it's just organisation. Anything customer-facing or public, like a blog post or a sent email, should keep a human approval step before it goes live. That's exactly how the blog skill above works: it drafts and stops, it never publishes without me reviewing it first.

What's the best first skill to build for a small business?

Start with whatever repetitive task already eats the same chunk of time every week and follows a predictable pattern, inbox triage and a recurring status brief are both good starting points because the input and the output rarely change shape. If you're not sure which task that is for you, running a free AI time audit of your week is the fastest way to find it.

If one of these sounds like something eating your week right now, that's usually the best place to start. Book a strategy call and we'll figure out which recurring task is worth turning into a skill first.