💫 This skill is free — copy it, give it to your Claude, and it installs itself in under a minute.
Free AI Skill · Create

Sound Like a Writer, Not a Transcript

Guide Polish takes a draft built from a podcast episode or coaching call — right message, rough rhythm — and elevates it until it reads like you sat down at your desk and wrote a guide for your best client.

← Back to the Skills Library
01 — GET THE SKILL

Installed in under a minute. No tech skills required.

You don't need to know how to code, and you don't need to set anything up. There are two blocks below. If you can copy and paste, you can install this.

1

Paste the instruction

Copy the first block and paste it into a brand-new Claude conversation. Don't hit send yet — it's the note that tells Claude what to do.

2

Paste the skill underneath, then send

Copy the full skill block and paste it right below the instruction. Send it. Claude builds the skill, personalizes it to your business, and confirms when it's ready.

Step 1 · paste this into Claude first
Install the skill below for me. Keep the skill text exactly as written, then personalize its defaults from what you already know about me — my business, my voice, my priorities, and the places I keep my notes and files. Confirm when it's installed and show me exactly how to run it.
Step 2 · the full Guide Polish skill
---
name: guide-polish
description: Elevate a transcript-based blog post draft into a polished, guide-quality piece that reads like you sat down and wrote it. Use this skill whenever you say "polish this," "clean this up," "make this read like a guide," "this reads like a transcript," "tighten this up," "revision pass," "guide polish," "run guide polish," "make this client-ready," or drop an edited draft and say it needs to be elevated. Also trigger when you have a blog post draft that came from a podcast transcript or coaching call and want it to feel like a written guide you would hand to a client. This is the revision layer that sits between your drafting step, which creates the draft, and your publishing step, which packages the post for publishing. If a draft exists and you want it to read better while keeping the message intact, this is the skill.
---

# Guide Polish

Elevate a transcript-based blog post draft into a polished, guide-quality piece that reads like you sat down at your desk and wrote a guide for your clients.

This skill keeps the message, the structure, and the stories exactly as they are. It changes how they read on the page. The draft goes in sounding like you talking into a microphone. It comes out reading like you sat down and wrote a guide for your best client.

## When This Skill Sits In The Workflow

**Your drafting step** creates the draft from transcript material.
**Guide Polish** elevates that draft into client-ready quality.
**Your publishing step** packages the polished post for publishing.

This skill is the revision layer. It sits between a finished draft and publishing. It makes good drafts great.

## When To Use

- A blog post draft exists that was built from a podcast transcript or coaching call
- The draft has the right message, stories, and structure and reads heavy, spoken, or rough
- You say any variation of: "polish this," "clean this up," "this reads like a transcript," "make this a guide," "tighten this," "revision pass," "make this client-ready"
- The output is a long-form guide or flagship blog post
- You want to hand this piece to a client or feature it as a resource

## The Six Revision Principles

These are the operating instructions for every Guide Polish pass. Apply all six to the full draft in a single revision. Hold all six lenses at once rather than running them one at a time across multiple passes.

### 1. Separate Spoken Rhythm From Written Rhythm

Transcripts carry patterns that work when talking and feel heavy when reading. Identify and rewrite these:

**Filler transitions:** "right? So..." / "so now let's get to..." / "and the next part of this is..." Replace with clean section breaks or let the structure do the transition work.

**Restated emphasis:** Speakers often say the same idea twice for emphasis. On a mic, this builds momentum. On a page, it reads as redundant. Keep the strongest version, cut the echo.

**Run-on thought chains:** Speakers connect ideas with "and" or "because" to maintain flow. Writers split these into separate sentences or paragraphs. If a sentence has more than two commas connecting distinct ideas, it probably needs to be broken apart.

**Verbal momentum builders:** "right? Those little things right there." / "that's the thing." / "and that's what I mean by this." These are mic patterns. Cut them. The writing should trust the reader to follow.

**The test:** Read every sentence and ask, "Did someone write this, or did someone say this?" If the answer is "said," rewrite it so it reads as written. The story stays. The energy stays. The rhythm changes.

### 2. Give Every Idea Its Own Space To Breathe

The draft will have paragraphs doing multiple jobs. A personal story bleeds into a teaching point which bleeds into an action step, all in one block. This creates walls of text that readers bounce off of.

**The rule:** Each major idea or emotional shift gets its own paragraph. If a paragraph is doing more than one job, split it.

**Personal story** gets its own space.
**The lesson it teaches** gets its own paragraph.
**The action step** the reader takes gets its own space.

**Line breaks between thoughts.** Short paragraphs. One-sentence paragraphs for emphasis when earned. Each thought gets room to land before the next one starts.

**Bold subheaders** within pillar sections to break up long stretches. These give the reader's eye a place to land when scanning.

**Numbered lists** where action steps are given. Keep three options out of a run-on paragraph and put them in a clean list.

**The test:** Scroll through the draft at arm's length. If any section looks like a wall of text, it needs to be broken up. A reader should be able to scan the piece and get the architecture before committing to reading.

### 3. Shift The Camera From "Me Sharing" To "You Receiving"

The transcript naturally centers on you telling your story. That's how podcasts work. In a written guide, the reader is the subject.

**Before a personal story:** Set up why it matters to them. "I'll share something personal here because it connects directly to what you might be feeling." The story is serving their journey.

**After a personal story:** Turn the lens back to the reader. "You've been through this exact same process." / "That's the growth mindset. Everybody starts somewhere." The reader should feel like the story was told for them.

**Connective tissue between sections** should be reader-facing. "Let me walk you through each one" is guide energy. "So now I'm gonna talk about" is podcast energy.

**Your stories stay.** They're the proof, the relatability, the EEAT signal. The revision keeps every story. It reframes the tissue around them so the reader is always the main character.

**The test:** After every personal story or anecdote, check: does the next sentence turn the camera back to the reader? If it stays on you, add a bridge sentence that connects the story to the reader's experience.

### 4. Clean The On-Ramps And Off-Ramps Between Sections

Transcripts jump between ideas with verbal transitions that work in real time and feel clunky in writing.

**Verbal bridges to cut:** "so now let's get to the second pillar" / "and the next part of this is all around" / "so once you understand those things about precision, now we're gonna get to the final pillar"

**Replace with:** Clean section breaks (horizontal rules or headers) that let the structure do the transition work. If a transition sentence is needed, make it one clean line: "Let me walk you through each one." / "Here's how each one works."

**The principle:** Let the structure carry the navigation. Headers and section breaks tell the reader where they are. The writing inside each section delivers value and lets the headers narrate the journey between sections.

### 5. Remove Performative Energy While Keeping Real Energy

Transcripts sometimes restate ideas for verbal emphasis or build momentum through repetition that works out loud and reads as padding on a page.

**Repetition for emphasis (cut):** When the same idea appears in three sentences that circle the same point, keep the strongest sentence and cut the other two.

**Verbal confirmation patterns (cut):** "right?" / "you know what I mean?" / "those little things right there" / "that's the thing." These are mic patterns that read as filler on a page.

**Real energy (keep):** Short punchy sentences. Bold declarations. The pace speeding up when excitement builds. Caps used sparingly and deliberately. This is your actual energy and it stays.

**The test:** If removing a sentence leaves the meaning of the paragraph intact, the sentence was padding. Cut it.

### 6. Format For Scanners

Most people scan before they commit to reading. The draft needs to work for both.

**Bold subheaders** within long sections to break up the visual weight and let scanners know what's coming.

**Short paragraphs.** Each thought gets its own space. One-sentence paragraphs for emphasis when the idea earns it.

**Numbered or bold-formatted lists** for action steps, options, or sequences. Keep parallel options out of prose paragraphs and put them in a list.

**Strategic bold text** on key phrases that anchor the reader's eye when scanning.

**The test:** If someone scrolled through the piece in five seconds, could they get the structure and the key ideas from the headers, bold text, and paragraph breaks alone? If the answer is no, add more visual scaffolding.

## Workflow

### Step 1: Read The Full Draft

Read the entire draft before making any changes. Understand the message, the structure, the stories, and the arc. Note where the transcript artifacts are heaviest and where the draft is already clean.

### Step 2: Apply All Six Principles In One Pass

Rewrite the full draft applying all six principles simultaneously. This is one revision that holds all six lenses at once.

Preserve:
- Every story and personal anecdote (reframe the tissue around them, keep them all)
- The overall structure and section order
- Your actual language, phrases, and teaching points
- The energy and warmth of how you communicate
- Any frameworks, named concepts, or specific terminology

Change:
- Spoken rhythm to written rhythm
- Walls of text to breathing, scannable paragraphs
- "Me sharing" connective tissue to "you receiving" guide energy
- Verbal transitions to structural transitions
- Padding and repetition to tight, single-delivery points
- Dense formatting to scannable formatting

### Step 3: Present The Polished Draft

Present the full revised draft in conversation. Create a file only when you ask for one. You'll want to read it, make edits, and iterate before it moves to your publishing step.

When presenting, briefly note what changed at a high level. Skip the line-by-line changelog. Something like: "Cleaned up the transcript rhythm throughout, broke up the dense sections in Pillar 2, reframed the stretching story so it bridges back to the reader, and added bold subheaders in the Intention section for scannability."

### Step 4: Iterate If Needed

You may want to tighten specific sections, adjust tone in certain spots, or flag areas that still feel off. Apply the same six principles to any revision requests.

## What This Skill Does NOT Do

- Does not change the message, thesis, or core teaching
- Does not add new stories, frameworks, or content that wasn't in the draft
- Does not remove stories (it reframes the tissue around them)
- Does not restructure the piece (reorder sections, merge pillars, and so on)
- Does not do the AEO optimization pass (that happens after this skill, before publishing)
- Does not create the publishing prompt (that's your publishing step)
- Does not write from scratch (that's your drafting step)

## Quality Standard

The polished draft should read like you sat down at your desk with a cup of coffee and wrote a guide for your best client. Like you, the writer, created this piece with intention.

Every sentence should pass the test: "Did someone write this, or did someone say this?"

The answer should always be "wrote."
That's it. You're installed.

From then on, just drop in a draft and say "Polish this."

Want to go further than skills?

Skills like this are how Christine runs her own business every day. In the Heart-Led AI Signature Group Coaching, she teaches you the whole system — live, in plain English, at your pace.

Explore Signature Coaching
02 — WHAT COMES BACK

One polished draft. Six lenses, applied at once.

Guide Polish is one full revision pass that holds six lenses at the same time — and hands back the whole draft, elevated. Here's what each lens does to your piece:

1 · Spoken Rhythm Becomes Written Rhythm

Every sentence gets the test: did someone write this, or say this? Filler transitions, restated emphasis, and run-on thought chains get rewritten so the page reads like writing.

2 · Every Idea Gets Room to Breathe

Walls of text get split. The story, the lesson it teaches, and the action step each get their own paragraph, with line breaks that let every thought land.

3 · The Camera Shifts to the Reader

Your stories all stay — they're the proof. The tissue around them gets reframed so the reader is always the main character, before each story and after it.

4 · Clean On-Ramps and Off-Ramps

Verbal bridges like "so now let's get to the second pillar" come out. Headers and section breaks carry the navigation instead.

5 · Real Energy Stays, Padding Goes

Repetition and mic patterns get cut; your short punchy sentences, bold declarations, and building pace stay. If removing a line changes nothing, it was padding.

6 · Formatted for Scanners

Bold subheaders, short paragraphs, numbered lists, and strategic bold text — so someone scrolling for five seconds still gets the architecture.

7 · The Polished Draft, Presented

You get the full revised draft right in the conversation, plus a short plain-English note on what changed — no line-by-line changelog, and a file only if you ask for one. From there you iterate together until it's ready for your publishing step.

What it will never touch

Your message, your thesis, your stories, your section order, and your named frameworks stay exactly as they are. Guide Polish never adds content that wasn't in the draft, never removes a story, and never restructures the piece. It changes how your draft reads, not what it says — and it holds one standard the whole way: every sentence should answer "wrote," not "said."

Keep stacking: pairs beautifully with The Humanizer

Guide Polish turns spoken rhythm into written rhythm — The Humanizer hunts down the telltale signs of AI-generated writing and rewrites them so the text sounds natural and human.

Get The Humanizer →
03 — WHY IT WORKS

Because a transcript was never meant to be read.

What works on a mic — repetition, verbal bridges, momentum builders — reads heavy on a page. Guide Polish exists because the gap between a good draft and a great guide is rhythm, not message.

1

It knows the difference between said and written

Transcripts carry patterns that build momentum out loud and read as filler in print. The skill names those patterns specifically — filler transitions, restated emphasis, verbal confirmations — and rewrites each one instead of guessing at "smoother."

2

One pass, all six lenses

The revision applies all six principles simultaneously rather than running six separate passes. That's why the polished draft reads coherent instead of patched.

3

Your voice is the thing being protected

Your actual language, phrases, teaching points, and warmth sit on the preserve list. The skill elevates how they sit on the page — it never swaps them out for generic polish.

4

It knows exactly where it sits

Guide Polish is the revision layer: it doesn't draft from scratch, doesn't restructure, and doesn't do your SEO pass. Doing one job well is what turns good drafts into great guides.

04 — FAQ

Questions people actually ask

What is the Guide Polish skill?
Guide Polish is a free Claude AI skill that takes a blog post draft built from a podcast transcript or coaching call and elevates it into a polished, guide-quality piece. It keeps your message, structure, and stories exactly as they are — and changes how they read on the page, from spoken rhythm to written rhythm.
When would I actually use it?
Whenever a draft exists that has the right message but reads heavy, spoken, or rough — usually because it started life as a transcript. It's built for long-form guides and flagship posts you'd hand to a client or feature as a resource, and it sits between your drafting step and your publishing step.
Will it change what I said?
No. The message, thesis, stories, section order, and your named frameworks are all preserved — the skill never adds content that wasn't in the draft and never removes a story. You get the full revised draft in the conversation with a brief note on what changed, and you can iterate from there.