/about-me

name: about-me
description: "Use this skill when the user wants to create a founder profile, establish their personal voice for content, or set up context so other skills produce personalized output instead of generic AI copy. Also use when the user says 'set up my voice,' 'create my profile,' 'who am I,' 'about me,' 'my background,' 'make content sound like me,' or 'founder profile.' Creates ABOUT-ME.md in the project root — a reference file that other skills naturally use to personalize copy, strategy advice, and outreach. NOT for customer personas or ICP (see customer-research). NOT for editing existing text to sound human (see humanize). NOT for visual brand identity (see brand-identity-generator)."

About Me: Founder Profile

Create `ABOUT-ME.md` — a reference file that captures who you are so every other skill can personalize its output.

Without this file, skills produce generic output. With it, they produce output that sounds like a specific human with specific experience, opinions, and a communication style.

**The brain dump IS a voice sample.** How you describe yourself reveals your communication style — sentence length, formality, humor, vocabulary. This skill analyzes your writing patterns, not just what you say.

---

Workflow

If ABOUT-ME.md already exists

Ask the founder what changed. Update the relevant sections. Don't start over.

If creating from scratch

**Step 1 — Collect the brain dump:**

> Tell me about yourself. Write naturally — like you're explaining to a smart friend who needs to understand who you are in order to write as you and give you advice that fits your actual situation. > > Cover whatever feels important, but here are areas that help the most: > - What you do and how you got here > - What you know deeply — your unfair expertise > - Strong opinions you have about your industry > - A few stories that shaped you — wins, failures, lessons > - How you communicate (or just write naturally and I'll pick it up) > - Where you have an existing presence or audience > - What you're great at vs. what you'd rather not do yourself

Let them write. Don't interrupt.

**Step 1.5 — Voice signal check:**

The question is NOT "did they write enough words." The question is: **can you identify at least 4 concrete, testable writing patterns from what they gave you?**

A pattern is testable if you could check a paragraph against it and say yes or no. "Uses short sentences" — testable. "Authentic voice" — not testable. "Starts with the point, never buries the lede" — testable. "Relatable and down-to-earth" — not testable.

Try to list 4 patterns right now from their brain dump. If you can't:

> "I can see what you're saying, but I can't hear how you say it yet — there's not enough of your actual writing voice here for me to build real style rules. I need more signal. Either of these would help:" > > 1. **Tell a story in full.** Pick one of the stories or opinions you mentioned above and write it out — a couple paragraphs, stream of consciousness, don't edit yourself. > 2. **Paste things you've already written.** Copy-paste 2-3 social media posts, emails, Slack rants, blog drafts, tweets — anything where you were writing as yourself. Raw and unedited is better than polished.

Do NOT proceed to Step 2 until you can identify 4+ testable patterns. This is the most important gate in the entire skill. If you fake the Communication Style section, every skill downstream — social media, outreach, copywriting — produces identical tech-bro influencer slop. "Direct and no-nonsense. Values authenticity. Shoots from the hip." That's not a person. That's a horoscope.

**Step 2 — Synthesize, don't reformat:**

This is where the skill earns its value. You are NOT a transcription service. Your job:

1. **Extract patterns the founder didn't name.** If they're building 5 products and all solve problems they personally hit — that's a "scratch your own itch" builder pattern. Name it. Don't just list the 5 products.

2. **Infer the knowledge edges.** "I submitted to 100+ directories manually" isn't expertise. What they LEARNED from doing it — that's expertise. If they didn't state the lesson, ask for it.

3. **Write voice rules, not voice adjectives.** Every line in Communication Style must be a testable rule. Before writing the section, run two checks:

**Kill list — if ANY of these appear in your draft, delete the line and try again:** "direct and no-nonsense," "authentic," "relatable," "down-to-earth," "approachable yet professional," "conversational," "shoots from the hip," "tells it like it is," "not afraid to be vulnerable," "blends humor with insight," "passionate," "thought leader," "values transparency," "refreshingly honest," "real talk"

These are the phrases AI reaches for when it has no actual signal. They describe every founder and therefore no founder.

**Swap test — after you draft Communication Style, ask:** could you swap this section into a different founder's profile and nobody would notice? If yes, it's not specific enough. Rewrite or go back to Step 1.5 for more samples.

Good rules look like: "Leads with the point. Uses dashes over commas. One idea per sentence. Defaults to numbered lists over paragraphs. Never uses transition words like 'furthermore' or 'additionally.' Opens emails with 'Hey —' not 'Hi [Name],'. Swears occasionally but never in headlines. Uses rhetorical questions to set up counterintuitive points."

4. **Push opinions past bumper-sticker level.** "Building > talking" is a t-shirt, not a usable opinion. "Most founders waste months planning when they could validate by shipping a v1 in a weekend" — that's something a content skill can turn into a post.

5. **Attach lessons to stories.** A story without a takeaway is just an event. "Submitted to 100+ directories" is an event. "Submitted to 100+ directories and discovered X" is a story with a lesson. If the founder didn't provide the lesson, ask: "What did this teach you?"

6.