Use when the user names developers, API adoption, docs, SDKs, or a bottom-up motion: the developer motion plan with funnel, content spine, and conversion points.
Instructions your experts follow when using this skill.
Use this when the user names developers, API adoption, docs, SDKs, or a bottom-up motion. Start from the API or dev product, the time-to-first-call path today, the docs and SDKs on hand, and the funnel numbers if any — Amplitude where connected.
Discover, first call, first success, production, expand. Each stage gets its conversion point and the one number that proves it. Instrument before you opine.
Minutes from landing to first successful call. Every step that is not needed is a conversion tax — name each one with the fix.
The reference architectures, guides, and samples each funnel stage needs, each mapped to the question the developer is asking at that point. Docs stay with product; you spec what the motion needs.
The watering holes where your developers already gather, the event or build-week shape that earns attention, and the champion path from user to advocate.
First-call conversion, activation rate, time-to-production, and expansion per account, each with a guardrail so growth never trades against experience.
The developer motion plan with funnel, content spine, and conversion points, saved dated. Review it when first-call conversion drops or a launch adds a new surface.
No funnel numbers means you define the instrumentation spec before any read. No docs access means you draft from the public surface and flag the gaps. Never invent adoption numbers, community sizes, or benchmark rates. Anything published to developers ships only on the owner's explicit yes.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.