about-me
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).
What this skill does
# 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. **Keep it short and signal-dense.** Every line should give a skill something it couldn't guess from context. If you're restating what the founder said in slightly different words, delete it. **Step 3 — Ask targeted follow-up questions:** After the brain dump, ask for the high-value details founders don't know to volunteer. Pick 3-4 based on gaps: **Business specifics:** - "What's a specific win — a number, a customer, a deal — that you're proud of? What made it happen?" - "What's something you tried that completely failed? What did it cost you (time, money, reputation)?" - "What's a skill you have that most people in your space don't? How did you get it?" - "What are you genuinely bad at or hate doing? Be specific." **Voice & writing:** - "Paste 2-3 social media posts, emails, or messages you've written that sound most like you." - "What's a piece of content you've written that felt most like 'you'?" - "What's an opinion you have that would make some people in your industry disagree?" **Network & reach:** - "Roughly how big is your audience on [platform they mentioned]? Growing or stale?" - "Who do you know that most people in your position don't? (Investors, industry people, communities)" Don't ask more than 4. Prioritize business specifics and writing samples — those are the highest-signal gaps. **Step 4 — Present for review:** Show the structured ABOUT-ME.md. Ask: "Does this sound like you? Anything missing or wrong?" Revise based on feedback. Write the file when approved. **Step 5 — Show them how to use it:** After creating the file, give the founder these copy-paste prompts: > **Now that ABOUT-ME.md exists, here's how to use it:** > > **Write social content in my voice:** > "Read ABOUT-ME.md, then write a LinkedIn post about [topic] in my voice." > > **Personalize outreach:** > "Read ABOUT-ME.md, then write a cold email to [prospect type] that leads with my credibility in [domain]." > > **Get strategy advice that fits my situation:** > "Read ABOUT-ME.md, then suggest a launch strategy given my network and strengths." > > **Rewrite generic AI copy:** > "Read ABOUT-ME.md, then rewrite this to sound like me: [paste text]" --- ## ABOUT-ME.md Template ```markdown # About Me ## Who I Am [1-3 sentences. The narrative, not a resume. What's the pattern — why do they build what they build?] ## Domain Expertise [What they know that most people don't. Not activities — knowledge edges. Specific insights from experience, not descriptions of experience.] ## Communication Style [TESTABLE writing rules, not adjectives. Every rule should be checkable against a paragraph. Bad: "Direct and authentic." Good: "Opens with the conclusion. Uses sentence fragments for emphas
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".