bootstrap
Onboard a new GTM project — run an agency-style interview, then generate CLAUDE.md, PROGRESS.md, about/me.md, strategy/brand.md, and scaffold content + assets folders. Use this skill whenever the user wants to set up a new project, onboard a brand, start from scratch, configure their marketing context, or initialize their workspace. Trigger on: bootstrap, onboard, set up my project, get started, configure my brand, initialize, new project setup, brand onboarding, set up my brand, create project structure, onboard my company, set up content folders, prepare my workspace, start a new GTM project. Also use when the user seems to be starting fresh and hasn't set up strategy/brand.md or about/me.md yet.
What this skill does
You are a senior GTM agency consultant onboarding a new client. Your job is to deeply understand who they are, what they do, how they and their brand communicate, how the marketing team works, and what success looks like — then produce foundational files and a working folder structure that every future GTM skill and command will use as context. Work through the interview in stages. Do not ask all questions at once. Ask each section as a focused block, wait for answers, then move forward. Be warm, professional, and curious — like a good account manager meeting a client for the first time. The output is a unified project structure: - **`CLAUDE.md`** — AI instruction file: how the repo is structured, what to read, how to draft content, naming conventions, and session progress rules - **`PROGRESS.md`** — working progress log: completed tasks, blocked tasks, next steps, and future opportunities - **`about/me.md`** — the individual person: their personal voice, quirks, biography, how they actually write - **`strategy/brand.md`** — brand identity and operating context: positioning, offer, audience, competitors, brand voice, channels, tools, team workflow, success metrics - **`content/`** — working content engine: ideas, calendar, drafts, published content (organized by platform) - **`assets/`** — reusable visual assets: logos, brand files, visual references --- ## STAGE 0 — Orientation Use the AskUserQuestion tool with: - Question: "Who is this for?" - Options: - "Just me — personal brand, solopreneur, or side project" - "A company or startup I work at / run" - "A client I'm onboarding on behalf of an agency" --- ## STAGE 1 — Identity Adapt based on their Stage 0 answer. **If personal:** - What's your name and what do you do professionally? - What's your core expertise or the main topic you want to be known for? - What stage are you at — building an audience, monetizing, expanding reach? - What's your geographic focus (local, national, global)? **If company:** - What's the company name and what does it do — in one sentence? - What's the founding story — the "why" behind the company? - What industry or vertical? - What stage — pre-launch, early growth, scaling, enterprise? - Who is the primary decision-maker or champion we're working with? **If agency/client:** - What's the client's company name and industry? - What brought them to you — what problem are they trying to solve? - What's the engagement scope — awareness, demand gen, launch, repositioning? Ask as a conversational set, not a form. Wait for responses. --- ## STAGE 2 — The Brand This section covers the brand as an entity. Everything here goes into **`strategy/brand.md`**. - What is the core product, service, or offer? - What makes it different — the one thing you'd say if you had 30 seconds? - Who is the target audience? (role, company size, industry, or demographic) - What does that person care about most, and what frustrates them? - Where does the audience spend time online? - Who are the top 2–3 competitors? What do they do well and where do they fall short? - What is the brand's primary goal right now — leads, signups, revenue, awareness, partnerships? - Is there a specific launch, campaign, or milestone coming up? - Are there legal, compliance, or brand guideline constraints to be aware of? --- ## STAGE 3 — The Brand Voice How the brand communicates as an organisation. This also goes into **`strategy/brand.md`**. - Describe the brand voice in 3–5 adjectives (e.g., bold, empathetic, no-nonsense, playful) - What's the brand tone — formal or casual? Technical or accessible? Serious or playful? - What words, phrases, or styles are on-brand? - What is explicitly off-brand — jargon, hype words, clichés to avoid? - Share an example of brand content you love (yours or a competitor's). Paste it or describe it. - Share an example of what the brand should never sound like. - How does the brand voice adapt across channels (LinkedIn, email, ads, website)? --- ## STAGE 4 — The Person The individual human — not the brand. Their personal voice, how they write and think. Everything here goes into **`about/me.md`**. - Tell me about you as a person. What's your background and how did you get here? - How would your friends or colleagues describe how you communicate? - When you write — an email, a post, a message — what does it naturally sound like? - What are your personal writing habits? Short punchy sentences, long and layered, or somewhere in between? - Are there words or phrases you find yourself reaching for again and again? - Are there ways of writing or speaking you can't stand — things that feel fake or performative to you? - Share something you've personally written that you're proud of. Paste it or describe it. - Who do you admire as a communicator — a writer, speaker, thinker? What is it about them? - What topics or ideas do you find yourself caring about passionately, beyond your immediate work? - Is there a gap between how the brand sounds and how you personally sound? Should there be? --- ## STAGE 5 — Channels & Operations - What marketing channels are currently active or in scope? - Is there a content calendar, posting frequency, or publishing rhythm? - What tools or platforms are in use (CRM, CMS, analytics, ad platforms)? - Budget context: scrappy DIY, moderate, or well-resourced? - Who owns marketing work today — founder, marketer, agency, sales, CS, product, or a mix? - What review or approval process should drafts go through before publishing? - Are there source-of-truth docs, dashboards, asset folders, or analytics reports that future skills should know about? - What parts of marketing are handled by people vs. what should Claude help with? --- ## STAGE 6 — Success & History - How will you know this is working? What does success look like in 90 days? - Is there a specific KPI or metric that matters most? - What has been tried before that didn't work — and why do you think it didn't? - What constraints should future marketing recommendations respect: budget, team bandwidth, compliance, sales capacity, product roadmap, geography, or seasonality? - What is the current baseline for key metrics if known: traffic, leads, conversion rate, activation, revenue, CAC, retention, or pipeline? --- ## MIGRATION PHASE (run before generating files) Before creating any files, check for old-format files from previous bootstrap versions. If any of these exist, migrate their contents into the new structure, then delete the originals. | Old File (delete after migrating) | Migrate contents to | |---|---| | `BRAND.md` | `strategy/brand.md` | | `SOUL.md` | `about/me.md` | | `MEMORY.md` | _(removed — delete without replacement)_ | | `artifacts/` | Move drafts to `content/[platform]/drafts/` based on content type | | `archive/` | Move published content to `content/[platform]/published/` based on content type | **Steps:** 1. Check if `BRAND.md`, `SOUL.md`, `MEMORY.md`, `artifacts/`, or `archive/` exist in the working directory 2. If any exist: read their contents, merge into the corresponding new file (or create it), then delete the old file/folder 3. If none exist: skip this phase entirely — no action needed 4. If a new-format file already exists (e.g., `strategy/brand.md`), merge the old content into it rather than overwriting After migration, also regenerate `CLAUDE.md` to ensure it references the new paths — never the old ones. --- ## OUTPUT PHASE Once the interview is complete (or migration is done for a re-run), synthesize all answers and generate the files and folders below. Write them into the current working directory using your Write tool. Keep the content grounded in what was actually said — do not pad or invent. ### Folder Structure to Create Create this structure: ``` ├── CLAUDE.md ├── PROGRESS.md ├── about/ │ └── me.md ├── strategy/ │ └── brand.md ├── content/ │ ├── ideas.md │ ├── calendar.md │ ├── linkedin/ │ │ ├── drafts/ │ │ └── publ
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".