Article

10 Oct 2026

What your business knows that nobody has written down

Every business has a house way of doing things that lives in people's heads. Claude skills turn it into something AI applies the same way every time.

Cartoon: colleagues cling to a veteran's suitcase as she leaves on holiday while a robot hands out tidy documents from a recipe book

What I've found, looking across the documents that leave the businesses I work with, is that almost every company has a house way of doing things that nobody has ever written down: a particular tone in client emails, a layout for proposals, a set of checks a report goes through before it reaches a director's inbox, all of it living in the heads of two or three long-serving people. Everyone recognises it when they see it. Ask anyone to describe it, though, and you'll get a shrug, a vague reference to "the template on the shared drive" and possibly a story about the time a proposal went out in Comic Sans. Most of us have lost an evening to this at some point, with the thinking done and the draft finished, still nudging margins and hunting for the right shade of the brand colour at half past six.

A Claude skill gives you that half hour back.

What a skill does

A skill is a set of instructions that tells Claude how to do a particular job the same way every time. Most are a single file written in plain language, sometimes with a template or reference documents alongside. Claude keeps a one-line description of every skill you've switched on, and when your request matches that description, it reads the full instructions and follows them. You can also call one directly by typing a forward slash in the message box and picking it from the list.

Last week I had a finished draft letter in a chat, and I asked Claude to put it into our company-branded Word format using our document skill. A minute later I had a file with our full-bleed header, our imagery, the green sash along the bottom and our standard formatting throughout, plus the gaps I still needed to fill highlighted for me. Without the skill, that job meant a new document, a round of copying and pasting, and the formatting reapplied by hand. Five or ten minutes, perhaps. Across fifteen documents a week, that adds up to as much as two and a half hours of skilled people's time spent on margins and fonts.

Claude reads only the one-line description before deciding whether a skill applies, so a vague description produces a skill Claude never reaches for. Think of it as the skill's job title: get it wrong and the call never comes.

The interview that built my email voice

My email skill took a little longer to build. I wanted Claude to draft emails that sounded like me, so I asked it to interview me about how I write: how I open, how I sign off, the tone I take with clients and the phrases I'd never use. Then I pointed it at a year of my sent emails and asked it to build a skill from both. Claude wrote the whole thing itself, a plain-language guide titled "Writing emails as Matt", covering everything from my openers to my sign-off.

Answering questions about my own writing, I found myself describing habits I'd never consciously noticed, like the way I explain my reasoning even in a two-line reply. Between them, a year of email and one long conversation produced something far closer to my voice than any style guide I could have written cold.

Why skills become a leadership question

The same file that tells Claude how your proposals should read can tell a new starter, on their first morning, what good looks like here. Writing it usually means putting into words, for the first time, something the business has only ever done by feel.

Think about the checks your most experienced person runs on a proposal before it goes out: whether the pricing matches the scope, whether the client's name is spelt correctly throughout, whether the executive summary says anything at all. Those checks live in one person's head, and that person runs them when they have the time. Written into a skill, Claude runs them on every proposal before it reaches that person's desk, which leaves their review time for the judgement calls only they can make.

Knowledge that used to walk out of the building whenever a long-serving colleague went on holiday (or, worse, on to another job) now lives somewhere everyone can reach.

On Team and Enterprise plans, owners can provision skills for everyone, share them with particular people or publish them across the business. The whole team then produces documents that look and sound like they came from the same company, without anyone having to police it. That consistency used to need a brand guardian with a red pen and a lot of patience.

Anthropic doesn't review the skills people share, so anyone installing a skill from outside the business should read it before switching it on, the same way you'd treat a spreadsheet macro from an unfamiliar sender.

Start smaller than you think

You don't need to build anything from scratch to begin. Claude's Discover tab offers ready-made skills from Anthropic and its partners, and on a team plan your colleagues may already have built a few you can borrow. The quickest way to build one is the route I took for my own emails: ask Claude to interview you about the job, give it a few good examples, and ask it to write the skill. When you do build your own, your email voice, your Word template or a style guide for your slides all make good first candidates, because they're small, repeated often and easy to judge.

At the other end of the scale, I use a skill that audits Microsoft 365 tenants. It takes in a large volume of configuration information, analyses it several ways and checks it against a detailed checklist. That one took far longer to build, and it only made sense once the simple ones had taught me how skills behave in practice.

Most teams start for the time saving. A few weeks in, someone usually tries to write a skill for a job everyone assumed was standard and discovers that three colleagues have been doing it three different ways for years. So here's something to take into Monday's meeting: if you had to write down how your business does its most important piece of work, could you, and would the team agree with what you wrote?

Where to go next

Our AI Hackathon is one day with your whole team, building prompts, workflows and agents for your own repeat jobs. For the step-by-step version, read How to get more out of Claude.