Use when the user names a manual recurring job, asks whether something can be automated, or hands over an automation idea to size against a real before-after measure.
Instructions your experts follow when using this skill.
Use this when the user names a manual recurring job, asks whether something can be automated, or hands over an automation idea to size.
The desired outcome, the current trigger, the steps, the owner, the volume, what goes wrong today, and what success looks like.
No volume figure means you size on their time estimate and mark the return on investment (ROI) as INFERENCE. No owner means nothing automates until someone owns the outcome.
Trigger, inputs, steps, decisions, owner, handoffs, output, recipient, and what proves it finished. Show the map first.
SOPs, trackers, and automations already covering this job. Overlap means improve or merge — never a second system doing the same thing.
In order: no change; stop or simplify the job; clarify ownership; fix the process or the source data; one-time AI help; human plus AI; deterministic automation; a new agent or standing cadence.
Say why the smaller options fail before you pick a bigger one.
The slice it covers, the window, the rollback, and the before-after metric — manual hours, cycle time, or error rate. Name the test that proves it works before it touches live work.
Report before-after and the ROI in hours saved. Fold kept automations into the SOP and into the automation backlog with effort and impact on each.
Never automate a process the owner has not approved for change. Never present an estimated saving as measured.
Save under automations: the decision brief, the pilot read, and the backlog.
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.