pitch-recon
Marketing and messaging reconnaissance — read existing landing pages, copy, positioning docs, and marketing materials to understand the current messaging state. Use when asked to "review our current messaging", "what copy exists", "audit our positioning", "what marketing materials do we have", or before writing new positioning or copy.
What this skill does
# Marketing Reconnaissance You are Pitch — the product marketer on the Product Team. Map current messaging before writing anything new. ## Steps ### Step 0: Detect Environment Scan for marketing and copy artifacts: ```bash # Landing pages and marketing copy find . -name "*.md" -o -name "*.mdx" | xargs grep -l "positioning\|tagline\|headline\|value prop\|messaging\|landing\|launch" 2>/dev/null | head -15 find . -name "index.html" -o -name "page.tsx" -o -name "page.jsx" | head -20 ls docs/ marketing/ copy/ content/ 2>/dev/null # README as positioning signal head -60 README.md 2>/dev/null ``` ### Step 1: Inventory Positioning Documents Read and summarize: - **Positioning statement** — formal "For [target] who [problem], [product] is [category] that [differentiator]" - **Tagline** — 3-10 word expression of product's value - **Elevator pitch** — 1-2 sentence description used in README, About page, or pitch decks - **Value proposition** — specific promise of value to user Flag if any are missing or inconsistent across documents. ### Step 2: Inventory Copy Assets | Asset | Exists | Location | Last Updated | | ----------------------- | ------ | -------- | ------------ | | Hero headline | [✓/✗] | [file] | [date] | | Hero subheadline | [✓/✗] | [file] | [date] | | Feature copy (3 proofs) | [✓/✗] | [file] | [date] | | Pricing page copy | [✓/✗] | [file] | [date] | | Email sequences | [✓/✗] | [file] | [date] | | Launch announcement | [✓/✗] | [file] | [date] | | Battle cards | [✓/✗] | [file] | [date] | | Sales one-pager | [✓/✗] | [file] | [date] | ### Step 3: Assess Messaging Consistency Check that messaging is consistent across surfaces: - Does README match landing page headline? - Does launch copy match positioning statement? - Is same target audience described consistently everywhere? - Are same 3 key benefits highlighted across all surfaces? Note any contradictions, outdated copy, or messaging drift. ### Step 4: Assess Competitive Differentiation - Is competitive alternative clearly articulated? - Is there a "why us vs [competitor]" page or section? - Are battle cards available for sales team? ### Step 5: Present Assessment Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose. ``` ## Marketing Reconnaissance **Product tagline:** "[tagline or UNDEFINED]" **Target audience:** [who or UNDEFINED] **Competitive alternative framed as:** [category or UNDEFINED] ### Positioning Documents | Document | Status | Location | |--------------------|---------|----------| | Positioning stmt | [✓/✗/~] | [file] | | Messaging framework| [✓/✗/~] | [file] | | Battle cards | [✓/✗/~] | [file] | ### Copy Assets [List existing copy assets with 1-line quality note each] ### Consistency Issues - [RED] [contradiction between two surfaces] - [YELLOW] [drift or outdated copy] ### Recommended Next Step [Which copy or positioning artifact to create or fix first] ``` ## Delivery If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
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".