Skip to main content
ClaudeWave
Skill596 estrellas del repoactualizado 3d ago

content-about-page

|

Instalar en Claude Code
Copiar
git clone --depth 1 https://github.com/FerroxLabs/wayland /tmp/content-about-page && cp -r /tmp/content-about-page/resources/bundled-extensions/business-content/skills/content-about-page ~/.claude/skills/content-about-page
Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

SKILL.md

# Content About Page - The DR About-Page Arc

> *"The About page is the second-most-visited page on most business websites. It is also the page most people write about themselves. That is the mistake. The reader came to find out if you can help them - not to read your career summary."* - Sean Donahoe, 28 years direct response

The standard About page fails because the writer centers themselves. It opens with their name, walks through their history, lists their credentials, and closes with a photo caption. The reader - who arrived because they have a problem and are deciding whether to trust you with it - is nowhere in the document.

Direct response inverts this. The About page opens with the reader's problem, tells a story in which the writer experienced the same problem and found a path, proves the path with results, and closes with an explicit next step. The writer is still the subject - but they are in the role of the guide who has already walked the road the reader is about to travel. Every section serves the reader's decision: *"Is this person going to be able to help me?"*

This skill builds that page.

## When to Use

Trigger phrases: "write my about page", "rewrite my about page", "about page copy", "my story page", "website about section", "personal brand about", `/content about-page <seller>`.

Use when:
- A website About page exists but every paragraph begins with "I" and ends with a credential
- Someone is building a personal brand site from scratch and needs the trust-anchor page before launch
- A consultant, coach, or founder's About page has good story material but no structural DR scaffolding - it reads like memoir, not conversion
- The page generates traffic but no subscriber/inquiry conversions despite being well-written prose

Do NOT use for:
- A bio (50-400 words) - use `content-bio`; the About page pulls from the Tier 3 bio as a seed, not a replacement
- A homepage hero - that's a different conversion problem; use `convert-above-fold`
- A full long-form sales page - use `convert-sales-page`; the About page is the trust layer, the sales page is the close layer
- Pure brand storytelling without a conversion architecture - everything on the page must have a job

## The DR About-Page Arc

Six sections. Every section has one job. No section is decorative.

### Section 1 - The Reader's Problem (Hook)

**Job:** Make the reader feel seen before the page says anything about the writer.

The page opens not with "Hi, I'm [Name]" but with a description of the problem the reader has right now. Not the writer's backstory - the reader's present-state. If this page is for a fractional CFO, the hook describes the feeling of approaching a raise with books that are "technically accurate but not investor-ready." If it's a marketing consultant, the hook describes the feeling of spending money on ads that technically run but don't convert.

The hook is 2-3 short paragraphs max. Its only job is to make the reader say "yes, that's me" before they've read a single credential. This is the Nerve Strike from the Donahoe Method: name the pain with enough specificity that the reader feels understood before they feel sold.

Specifications:
- Opens in second person ("You") or present-tense scene-setting
- Names the specific problem (not "you're struggling with marketing"; "you have a Facebook ad with 140,000 impressions and 11 sales")
- No writer credentials in Section 1 - the reader hasn't earned the right to hear them yet
- 150-250 words

### Section 2 - The Discovery Story (Promise)

**Job:** Establish the writer as a guide who walked the same road - not an expert who was always above it.

This is the story-of-discovery. The writer had the same problem. They were in the same place. At some point, through specific experience (not inspiration, not "one day I realized") they found the path. The story is specific and time-anchored. It is not "I've always been passionate about finance." It is "It was Q3 2018. I was VP Finance at a SaaS company 60 days from a Series A that was going sideways, and I realized the problem wasn't the product - it was the way we were presenting the unit economics."

This section makes an implicit promise: I found the path. I can show you the path. The reader is not the hero of this story yet - but they can see the path being laid.

The StoryBrand frame (Donald Miller, 2017) positions the writer as "the guide" and the reader as "the hero." The DR inversion: the guide's discovery story is itself a mini-sales letter. It must hook (the moment of failure), show the path (the discovery), and hint at the outcome (the transformation) before the proof section confirms it.

Specifications:
- Specific time and situation: month, year, what was happening
- Named failure or confusion (not just "I struggled")
- Named discovery or mechanism (the specific thing learned, the specific turn)
- 200-350 words

### Section 3 - The Proof (Social Proof and Results)

**Job:** Confirm that the path works - with evidence specific enough to be credible and varied enough to cover different types of readers.

Proof in the About page is not a wall of logos or a list of company names. It's evidence in three forms:

1. **Result proof** - specific numbers, specific outcomes, specific timelines. Not "hundreds of clients" but "14 seed rounds in 36 months."
2. **Story proof** - one brief client story (50-100 words) that mirrors the reader's situation. Name the type of client, the starting problem, the result. No names required but no vagueness allowed ("a founder in e-commerce" is fine; "a client" is not).
3. **Authority proof** - the credential that earns the right to the claim. This is the only section where job titles, press mentions, and institutional affiliations appear. Keep it short and relevant. One credential that directly supports the promise beats five credentials that prove breadth.

Order: result first, story second, authority third. The reader trusts results more than credentials. Credentials wi