Abie Maxey
Stop Re-Explaining Yourself to Claude ~ Abie Maxey
The Blog
Claude ~ Beginners May 2026 6 min read

Stop Re-Explainingyourself to Claude

Every new chat, Claude forgets everything. Skills fix that ~ permanently.

Every time you open a new Claude chat, you start from zero. Claude doesn't know your name, your business, your tone, or what you built yesterday. You either type it all out again, get generic output, or quietly give up and do it yourself.

That friction is not a bug in how you're using Claude. It is the default behaviour ~ Claude has no memory between sessions unless you give it one.

Skills are how you give it one. This post explains what they are, what they look like, and how to install one in under five minutes ~ no coding required.

The blank-slate problem~ why Claude keeps forgetting

Claude processes your conversation and gives you a response. When you close the tab, it forgets everything. The next chat is a fresh start. Claude does not carry your tone, your preferences, or anything you said last week into a new session.

That is why most people get generic results. They ask Claude to write an email and it sounds like a template. They ask it to do research and it misses the angle they actually care about. They ask it to write a social post and it sounds like a robot trying to be casual.

The problem is not the prompt. The problem is that Claude is starting cold every single time ~ and you are the one paying the tax of re-explaining who you are.

“You do not have a Claude problem. You have a context problem.”

What a skill actually is~ plain English

A skill is a text file. Specifically, a .md (markdown) file that contains structured instructions for Claude ~ your name, your tone, your writing rules, your business context, examples of how you write. Whatever you would normally type into a chat to give Claude context.

When you install a skill, Claude reads it at the start of every session. It does not have to ask who you are. It does not have to guess your tone. It already knows ~ because you told it once and it remembers every time.

You write the file once. Claude uses it forever.

Brand Voice

Your tone, writing rules, phrases to use and avoid, signature

Content Writer

Your platforms, content pillars, hook style, default CTA

Competitor Analyst

Your business context, differentiators, research sources

What it looks like inside~ the anatomy

A skill file has two parts. The top section (wrapped in ---) is the frontmatter ~ a name and a short description of when Claude should use this skill. Below that is the actual content: your instructions, rules, and examples in plain text.

This is what a Brand Voice skill file looks like:

.claude/skills/brand-voice.md

---

name: my-brand-voice

description: "Enforces my tone on all written output."

---


# My Brand Voice


You are writing as [Your Name / Business].


## Tone

Direct, warm, no corporate jargon.

Short paragraphs. Use ~ instead of dashes.


## Do

- Lead with the point

- Use real examples, not vague generalisations


## Don't

- Never use passive voice

- Never say "leverage" or "synergy"


## Voice Sample

[paste 3 real sentences you've written]

That is it. No code. No syntax to learn. Plain English in a text file. The structure helps Claude understand what each part is for ~ the name identifies it, the tone section calibrates voice, the do/don't section enforces rules, the voice sample gives Claude real examples to match.

The more specific you are, the better Claude performs. Vague instructions get vague results. Specific rules ~ “use ~ instead of dashes,” “never say leverage” ~ get precisely followed output.

Two ways to install it~ Claude.ai vs Claude Code

You can use skills in two places. If you use Claude through the browser at claude.ai, you install skills through Projects. If you use Claude Code in your terminal, skills live as files in your project folder. Both work ~ the right one depends on how you currently use Claude.

Claude CodeDeveloper
1

Save to .claude/skills/your-skill.md

2

Add to CLAUDE.md: Skill: .claude/skills/your-skill.md

3

Invoke with /your-skill or set always-on

Claude.aiNo code needed
1

Open Claude.ai → Projects → New Project

2

Click Set instructions → paste the skill file

3

Every chat in that Project uses it automatically

If you have never touched a terminal and you just use Claude.ai in the browser, go with the Project instructions path. You do not need Claude Code for any of this. Create a Project, paste your skill file into the instructions, and you are done.

If you are a developer or you use Claude Code, save the file into .claude/skills/ and reference it in your CLAUDE.md. Now it loads automatically and you can invoke it as a slash command.

You don't need to write one from scratch~ Skill Maker does it

The blank-page problem is real. Even if you know what you want Claude to do, translating that into a well-structured skill file takes time ~ and most people don't do it because of that friction.

I built Skill Maker to remove that friction. You pick a template, fill in your details, and it generates the full skill file ~ formatted, structured, and ready to copy. It takes about two minutes.

Free Tool

Skill Maker

You do not have to write a skill file from scratch. Fill in a few fields and Skill Maker generates the full structured .md file ~ ready to copy and install in under two minutes.

Brand VoiceContent WriterCompetitor AnalystCustomer Research
Build my skill

There are four templates right now: Brand Voice, Content Writer, Competitor Analyst, and Customer Research. Each one asks you the right questions and generates a skill file you can install immediately. No account, no payment, no setup.

What changes after~ the actual difference

Before: you open Claude, type a long context dump, get an output that is halfway there, correct it, re-explain your tone, get something better, close the tab. Next day: repeat from the beginning.

After: you open Claude, type your actual request, and get an output that already sounds like you. No preamble. No re-explaining. Claude already knows your voice because the skill file told it before you typed anything.

The bigger shift is that Claude becomes a real tool instead of a powerful one that requires constant management. When Claude knows your context, you stop editing AI output and start shipping it. That is the actual leverage ~ not the model, not the features, but the persistent context that makes every session feel like a continuation rather than a restart.

Before vs after a brand voice skill

Without a skill

You: Write me a follow-up email...

Claude: “Hope this email finds you well! I wanted to circle back on...”

You: No, that sounds nothing like me. Be more direct. Drop the filler. Shorter.

Claude: [tries again]

You: Still wrong. Let me just write it myself.

With a brand voice skill

You: Write me a follow-up email to [name] re: proposal.

Claude: “Hey [name] ~ just following up on the proposal I sent Tuesday. Happy to jump on a call this week if it helps. Let me know.”

You: Perfect. Sending.

Skills are not an advanced feature. They are the most basic quality-of-life improvement you can make to your Claude setup. If you use Claude more than twice a week for the same types of tasks, you should have at least one skill file installed.

Start with Brand Voice. It is the most transferable ~ once Claude knows how you write, every output it produces is closer to what you would have written yourself. That alone saves hours.

Build it at Skill Maker. Two minutes. No account.

A

Love, Abie

abiemaxey.com

~ Save it for later

Share as acarousel

Weekly Dispatch

Thebuilder'sdiaries.

What I'm building, breaking, and figuring out.

  • AI tools I actually use to build faster
  • Behind-the-scenes of growing a business in Madrid
  • Community plays, client wins, and real revenue breakdowns
  • Grounded dispatches from someone building roots

Drop your email.

Unsubscribe any time. No spam, ever.