Skills

When the user wants to plan, design, or implement an A/B test or experiment, or build a growth experimentation program. Also use when the user mentions "A/B test," "split test," "experiment," "test this change," "variant copy," "multivariate test," "hypothesis," "should I test this," "which version is better," "test two versions," "statistical significance," "how long should I run this test," "growth experiments," "experiment velocity," "experiment backlog," "ICE score," "experimentation program," or "experiment playbook." Use this whenever someone is comparing two approaches and wants to measure which performs better, or when they want to build a systematic experimentation practice. For tracking implementation, see analytics. For page-level conversion optimization, see cro.

When the user wants to generate, iterate, or scale ad creative — headlines, descriptions, primary text, or full ad variations — for any paid advertising platform. Also use when the user mentions 'ad copy variations,' 'ad creative,' 'generate headlines,' 'RSA headlines,' 'bulk ad copy,' 'ad iterations,' 'creative testing,' 'ad performance optimization,' 'write me some ads,' 'Facebook ad copy,' 'Google ad headlines,' 'LinkedIn ad text,' or 'I need more ad variations.' Use this whenever someone needs to produce ad copy at scale or iterate on existing ads. For campaign strategy and targeting, see ads. For landing page copy, see copywriting.

When the user wants help with paid advertising campaigns on Google Ads, Meta (Facebook/Instagram), LinkedIn, Twitter/X, or other ad platforms. Also use when the user mentions 'PPC,' 'paid media,' 'ROAS,' 'CPA,' 'ad campaign,' 'retargeting,' 'audience targeting,' 'Google Ads,' 'Facebook ads,' 'LinkedIn ads,' 'ad budget,' 'cost per click,' 'ad spend,' or 'should I run ads.' Use this for campaign strategy, audience targeting, bidding, and optimization. For bulk ad creative generation and iteration, see ad-creative. For landing page optimization, see cro.

When the user wants to optimize content for AI search engines, get cited by LLMs, or appear in AI-generated answers. Also use when the user mentions 'AI SEO,' 'AEO,' 'GEO,' 'LLMO,' 'answer engine optimization,' 'generative engine optimization,' 'LLM optimization,' 'AI Overviews,' 'optimize for ChatGPT,' 'optimize for Perplexity,' 'AI citations,' 'AI visibility,' 'zero-click search,' 'how do I show up in AI answers,' 'LLM mentions,' or 'optimize for Claude/Gemini.' Use this whenever someone wants their content to be cited or surfaced by AI assistants and AI search engines. For traditional technical and on-page SEO audits, see seo-audit. For structured data implementation, see schema.

When the user wants to set up, improve, or audit analytics tracking and measurement. Also use when the user mentions "set up tracking," "GA4," "Google Analytics," "conversion tracking," "event tracking," "UTM parameters," "tag manager," "GTM," "analytics implementation," "tracking plan," "how do I measure this," "track conversions," "attribution," "Mixpanel," "Segment," "are my events firing," or "analytics isn't working." Use this whenever someone asks how to know if something is working or wants to measure marketing results. For A/B test measurement, see ab-testing.

Tell a story about ants, or read a system the way the book reads one. Use when writing any ants story, when someone asks where a system's intelligence lives, or when a claim about the colony needs checking against what the substrate can actually do. Triggers — "write an ants story", "tell the ants story", "who is in charge of this system", "is this a mill", "what does the colony do here", "ant colony optimisation".

When an agent or user needs to decide the SHAPE of a change before any code is written — which seam to cut at, what to reuse, what the tradeoff costs. Also use when the user says "how should we build this," "what's the right design," "should we extend or rewrite," "where does this belong," "is this the right abstraction," "review this design," or "what will this break." Use this whenever the question is about structure rather than syntax. For reading an existing diff, see diff-review. For executing a shape that is already decided, see code-edit. For a workflow's edge weights, see workflow-optimise.

When the user wants to audit or optimize an App Store or Google Play listing. Also use when the user mentions 'ASO audit,' 'app store optimization,' 'optimize my app listing,' 'improve app visibility,' 'app store ranking,' 'audit my listing,' 'why aren't people downloading my app,' 'improve my app conversion,' 'keyword optimization for app,' or 'compare my app to competitors.' Use when the user shares an App Store or Google Play URL and wants to improve it.

Audit a piece of copy against brand-voice rules. Flag adverbs, jargon, hedges, and tone drift. Rewrite the worst sentence.

GIFT-adapter — design a creator collaboration brief that qualifies the right creators, structures an authentic partnership and a native content brief that fits the avatar's watering holes. Use to recruit advocates whose audience overlaps your own.

REFINE adapter — produce a crisis content pivot plan that classifies a disruption by severity and rapidly adapts messaging, tone and channels while protecting brand trust. Use when an economic, supply-chain or sensitivity crisis demands the marketing calendar pause and shift.

REFINE adapter — build a cultural-calendar integration plan that authentically weaves local traditions, festivals and contemporary moments into the marketing year, matched to the avatar's values and channels. Use to deepen local resonance without stereotype.

REFINE adapter — render a time-boxed flash-sale campaign with authentic urgency, segmented multi-channel copy and a follow-up sequence that lifts conversion and AOV without eroding trust. Use to drive a deliberate, short revenue peak.

REFINE adapter — build a phased product-launch timeline that sequences anticipation, VIP access, public launch and post-launch optimisation across channels, so a new offer enters the framework at every lever at once. Use when introducing a new product or collection.

REFINE adapter — plan a year of seasonal campaigns by mapping the avatar's emotional state and watering holes to each cultural and seasonal moment, so the framework's levers are pointed at peak buying windows. Use when building or refreshing the marketing calendar.

When the user wants to reduce churn, build cancellation flows, set up save offers, recover failed payments, or implement retention strategies. Also use when the user mentions 'churn,' 'cancel flow,' 'offboarding,' 'save offer,' 'dunning,' 'failed payment recovery,' 'win-back,' 'retention,' 'exit survey,' 'pause subscription,' 'involuntary churn,' 'people keep canceling,' 'churn rate is too high,' 'how do I keep users,' or 'customers are leaving.' Use this whenever someone is losing subscribers or wants to build systems to prevent it. For post-cancel win-back email sequences, see emails. For in-app upgrade paywalls, see paywalls.

Move a qualified prospect to a signed agreement or purchase.

When the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referrals. For launch-specific partnerships, see launch.

When a decided change has to become an actual edit — a file written, a symbol renamed, a migration added — and the edit must land exactly where it was specified and nowhere else. Use when the user says "make the change," "apply the diff," "write the file," "implement this," "do the edit," or hands over a plan and asks for it to be executed. Use this whenever the shape is already settled and what remains is typing it correctly. For deciding the shape first, see architecture-review. For judging an edit after it exists, see diff-review.

Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.

Build and leverage online communities to drive product growth and brand loyalty. Use when the user wants to create a community strategy, grow a Discord or Slack community, manage a forum or subreddit, build brand advocates, increase word-of-mouth, drive community-led growth, engage users post-signup, or turn customers into evangelists. Trigger phrases: "build a community," "community strategy," "Discord community," "Slack community," "community-led growth," "brand advocates," "user community," "forum strategy," "community engagement," "grow our community," "ambassador program," "community flywheel."

Use when the user wants to understand their SEO competitive landscape — who ranks for their target keywords, what their backlink profiles look like, and where the gaps are. Triggers on "competitive analysis," "competitors SEO," "who ranks for," "SEO landscape," or "competitive gap."

Use when the user wants a deep-dive on a single competitor's SEO strategy — their top pages, backlink sources, keyword profile, and content angle. Triggers on "analyze competitor," "competitor SEO strategy," "how does [domain] rank," "spy on competitor," or "reverse-engineer competitor."

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 create competitor comparison or alternative pages for SEO and sales enablement. Also use when the user mentions 'alternative page,' 'vs page,' 'competitor comparison,' 'comparison page,' '[Product] vs [Product],' '[Product] alternative,' 'competitive landing pages,' 'how do we compare to X,' 'battle card,' or 'competitor teardown.' Use this for any content that positions your product against competitors. Covers four formats: singular alternative, plural alternatives, you vs competitor, and competitor vs competitor. For sales-specific competitor docs, see sales-enablement.

CONTENT — write one search-aware, value-first blog post that opens with a Hook-Grid angle and carries a reader from problem to a soft, on-brand next step. Use when a topic needs a long-form article for organic discovery.

CONTENT — build a monthly content calendar that maps themes and content pillars across the brand's priority channels, anchored to the customer journey. Use to plan a coherent month of multi-channel content.

CONTENT — render a topic into a native Instagram content set (feed caption, story sequence, reel concept) with a scroll-stopping visual hook and one clear CTA. Use to produce platform-ready Instagram content for a campaign.

CONTENT — write a professional LinkedIn post that opens with a thought-leadership hook, delivers a business insight or story, and ends with a discussion prompt. Use to produce B2B-credible content from a topic or experience.

CONTENT — write SEO-optimised Pinterest pin descriptions with a keyword-led title, a value proposition, and a click-through CTA. Use to produce discovery-ready pins that drive long-tail traffic.

When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions "content strategy," "what should I write about," "content ideas," "blog strategy," "topic clusters," "content planning," "editorial calendar," "content marketing," "content roadmap," "what content should I create," "blog topics," "content pillars," or "I don't know what to write." Use this whenever someone needs help deciding what content to produce, not just writing it. For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit. For social media content specifically, see social.

CONTENT — write native TikTok video scripts with a sub-3-second hook, a shot-by-shot value arc, and an authentic CTA. Use to produce short-form vertical video scripts for a topic or campaign.

CONTENT — write a value-first Twitter/X thread with a curiosity-gap hook tweet, one insight per tweet, and a single CTA in the final tweet. Use to turn an insight or story into a shareable thread.

CONTENT — write a retention-optimised YouTube video script with a 15-second hook, value beats every 30–60s, and a soft end-screen CTA. Use to produce a full long-form video script for a topic.

When the user wants to edit, review, or improve existing marketing copy, or refresh outdated content. Also use when the user mentions 'edit this copy,' 'review my copy,' 'copy feedback,' 'proofread,' 'polish this,' 'make this better,' 'copy sweep,' 'tighten this up,' 'this reads awkwardly,' 'clean up this text,' 'too wordy,' 'sharpen the messaging,' 'refresh this content,' 'update this page,' 'this content is outdated,' or 'content audit.' Use this when the user already has copy and wants it improved or refreshed rather than rewritten from scratch. For writing new copy, see copywriting.

When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product pages. Also use when the user says "write copy for," "improve this copy," "rewrite this page," "marketing copy," "headline help," "CTA copy," "value proposition," "tagline," "subheadline," "hero section copy," "above the fold," "this copy is weak," "make this more compelling," or "help me describe my product." Use this whenever someone is working on website text that needs to persuade or convert. For email copy, see emails. For popup copy, see popups. For editing existing copy, see copy-editing.

When the user wants to optimize, improve, or increase conversions on any marketing page or form — including homepage, landing pages, pricing pages, feature pages, lead capture forms, or contact forms. Also use when the user says 'CRO,' 'conversion rate optimization,' 'this page isn't converting,' 'improve conversions,' 'why isn't this page working,' 'my landing page sucks,' 'form abandonment,' 'nobody's converting,' 'low conversion rate,' or 'this page needs work.' Use this even if the user just shares a URL and asks for feedback. For signup/registration flows, see signup. For post-signup activation, see onboarding. For popups/modals, see popups.

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," or "find out why customers churn/convert/buy." Use for both analyzing existing research assets AND gathering new research from online sources. For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.

When an agent or user needs a diff, pull request, or set of changes read for correctness against what it claims to do. Also use when the user says "review this," "review my PR," "check this change," "did I break anything," "is this safe to merge," "look over this diff," or "what did I miss." Use this whenever code already written needs judging. For deciding the shape before code exists, see architecture-review. For applying a change once it is decided, see code-edit. For probing a live surface, see security-audit.

When the user wants to submit their product to startup, SaaS, AI, agent, MCP, no-code, or review directories for backlinks, domain rating, and discovery. Also use when the user mentions "directory submissions," "submit to directories," "backlinks from directories," "list my product," "submit to Product Hunt," "BetaList," "TAAFT," "Futurepedia," "G2 listing," "Capterra listing," "AlternativeTo," "SaaSHub," "AI directories," "MCP registry," "agent directory," "dofollow backlinks," "launch directories," or "directory tracker." Use this whenever someone is planning the directory layer of a product launch or an ongoing backlink campaign. For the broader launch moment, see launch. For programmatic SEO pages that should live behind these backlinks, see programmatic-seo. For AI citation optimization, see ai-seo.

Generate a launch / outreach email with 3 subject-line variants, a tight body, and a single CTA. Bias toward specifics over enthusiasm.

EDUCATE — turn collected post-purchase feedback into a prioritised insight report that names the themes, scores their business impact, and feeds the Insight Loop back into the Foundation and REFINE. Use after the feedback survey exists and responses are in.

EDUCATE — build the post-purchase feedback survey (NPS, CSAT and an open-ended follow-up) timed to fire after the activation window, turning the customer's experience into a CustomerDataPoint that feeds the Insight Loop. Use to capture the signal that sharpens the whole framework.

EDUCATE — calculate customer lifetime value, segment customers by value, and recommend retention plays that prove the financial case for onboarding. Use to quantify the repeat-and-referral lever and prioritise where retention spend earns the most.

EDUCATE — build the post-purchase onboarding sequence that closes the consumption gap, drives every new customer to their activation moment, and earns the repeat purchase. Use after a purchase, to turn a buyer into a successful, loyal repeat customer.

EDUCATE — design the supporting success content (tutorials, quick-start guides, feature explanations) that drives consumption and mastery beyond the email spine. Use to give a new customer the help they need at the moment of friction.

When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.

Draft the ENGAGE chat scripts — chatbot and live-chat flows that resolve the avatar's high-intent questions and objections in real time, with escalation paths. Use during the Engage step.

Run the ENGAGE friction-reduction audit — map the avatar's likely hesitation points to behavioural triggers, methods and goals as a completed Engagement Planner. Use during the Engage step.

Write the ENGAGE page copy — inline reassurance, contextual FAQs and proactive trigger snippets embedded on key conversion pages to resolve friction at the point it arises. Use during the Engage step.

Draft the ENGAGE welcome message — the proactive first interaction that greets a high-intent prospect and opens a helpful, on-brand conversation. Use at the start of the Engage step.

Hand off a conversation to a human agent with full context.

Assemble the FOUNDATION Strategic Blueprint — synthesise company, market and customer pillars into the Aligned Foundation Grid and the three AI context blocks. Use to close the Foundation before ATTRACT.

Write the FOUNDATION brand story — the coherent narrative and desired feeling the brand carries, rooted in its mission — for cell C3 of the Company Context Grid. Use after the mission and vision are set.

Define the FOUNDATION Brand Voice — three to five actionable adjectives plus do/don't guidance — for cell C2 of the Company Context Grid. Use when fixing how the brand sounds.

Map the FOUNDATION competitive set — rivals' value propositions and evidenced weaknesses — for the Observe and Analyse columns of Market Awareness Grid Row A. Use when reading the competitive field.

Synthesise primary research into the FOUNDATION Customer Avatar — the 3x3 Customer Avatar Grid across Observable Reality, Underlying Drives and Future State. Use when building the ideal-customer portrait.

Deepen the FOUNDATION Customer Avatar with public-source deep research — watering holes, stated pains and goals, inferred fears and needs — extending the avatar grid. Use after the avatar's first pass.

Define the FOUNDATION market positioning — where the brand sits versus rivals and on the value spectrum — from the Market Awareness Grid's Respond column. Use when fixing the defensible position to own.

Draft the FOUNDATION Mission and Vision — why the business exists and the future it is building — for cell A3 of the Company Context Grid. Use when fixing organisational purpose.

Define the FOUNDATION Unique Mechanism — the operational engine behind the offer that rivals cannot honestly replicate. Use when populating the Company Context Grid cell A2.

Craft the FOUNDATION primary value proposition — the single transformation the customer gets, pointed at the unique mechanism — for cell B1 of the Company Context Grid. Use after the unique mechanism is defined.

Map the FOUNDATION watering holes — the named channels where the customer's attention concentrates, scored on presence, competitive density and voice fit — for Market Awareness Grid Row C. Use when choosing where the HOOK fires.

When the user wants to plan, evaluate, or build a free tool for marketing purposes — lead generation, SEO value, or brand awareness. Also use when the user mentions "engineering as marketing," "free tool," "marketing tool," "calculator," "generator," "interactive tool," "lead gen tool," "build a tool for leads," "free resource," "ROI calculator," "grader tool," "audit tool," "should I build a free tool," or "tools for lead gen." Use this whenever someone wants to build something useful and give it away to attract leads or earn links. For downloadable content lead magnets (ebooks, checklists, templates), see lead-magnets.

Run the ELEVATE GIFT step to write the promotional ad body — copy that follows the winning hook, introduces the gift and drives the click to the landing page.

Run the ELEVATE GIFT step to draft the lead-magnet content — write the gift's introduction and one fully developed key section from the chosen concept's outline.

Run the ELEVATE GIFT step to write the gift delivery email — subject lines and body that welcome the new lead, deliver the gift instantly and set up the relationship.

Run the ELEVATE GIFT step to design and select the lead-magnet concept — brainstorm gift ideas against the Gift Value Equation and recommend the strongest one with a content outline.

Run the ELEVATE GIFT step to write the lead-magnet landing-page copy — headlines, benefit bullets and CTA button text that convert attentive visitors into opt-ins.

Receive and resolve a customer complaint end-to-end.

Produce 5 headline options for a campaign, landing page, or ad — across distinct angles (outcome, contrarian, social-proof, urgency, curiosity). Pick a winner.

Define HOOK ad angles by mapping the avatar's awareness stage to Hook Grid angles, producing the angle bank that later hooks draw on.

Generate HOOK pain-focused ad headlines that name a core customer pain and stop the scroll on a priority feed channel.

Generate HOOK scroll-stop elements — pattern-interrupt visual concepts for static feed creative that break the feed's rhythm and signal relevance.

Generate HOOK benefit-focused SEO titles that promise a customer goal and win the click on a search results page.

Generate HOOK intrigue-based social openers that challenge a belief or tease a unique mechanism to stop a fast-scrolling feed.

Generate HOOK video hooks — the first one-to-two seconds of feed videos that open in motion and stop the thumb before a word is read.

Assemble the IDENTIFY lead-capture page — structural flow, mechanism and on-page copy — that turns gift desire into a tagged lead. Use to lay out the capture page for the IDENTIFY step.

Write the IDENTIFY lead-magnet calls-to-action that prompt the opt-in across surfaces. Use to draft benefit-named CTAs for the gift's capture moment in the IDENTIFY step.

Write the IDENTIFY opt-in form copy — headline, button labels and trust snippets — that converts gift desire into a captured email. Use to draft the on-form micro-copy for the IDENTIFY step.

Design an IDENTIFY interactive quiz or survey that captures a tagged email mid-conversation. Use to build a chatbot-style or quiz lead-capture experience for the IDENTIFY step.

When the user wants to create, generate, edit, or optimize images for marketing — blog heroes, social graphics, product mockups, profile banners, listing visuals, or brand assets. Also use when the user mentions 'AI image generation,' 'generate an image,' 'create a graphic,' 'product mockup,' 'hero image,' 'social media graphic,' 'banner image,' 'cover photo,' 'profile banner,' 'listing screenshot,' 'Flux,' 'Flux Kontext,' 'Midjourney,' 'DALL-E,' 'GPT Image,' 'ChatGPT Images,' 'Ideogram,' 'Gemini image,' 'Nano Banana,' 'Recraft,' 'Stable Diffusion,' 'Canva,' 'Figma,' 'image optimization,' 'compress images,' 'WebP,' or 'OG image.' Use this for general-purpose marketing image creation and optimization. For paid ad image creative and platform-specific ad specs, see ad-creative. For video production, see video.

When production is broken or degraded and someone needs the bleeding stopped before the cause is found. Also use when the user says "the site is down," "production is broken," "users are reporting," "something's wrong in prod," "did we break it," "roll it back," or "why is this failing live." Use this whenever a live surface is failing right now. For a suspected-but-not-live weakness, see security-audit. For a slow-but-working system, see perf-audit. For writing the trap up durably afterwards, see runbook-write.

Apply the art-prints & wall-decor overlay to bend any ELEVATE asset toward artist story, self-expression and home transformation.

Apply the candle & home-fragrance overlay to bend any ELEVATE asset toward scent, ritual and seasonal sanctuary.

Apply the ceramic & pottery overlay to bend any ELEVATE asset toward artisan craft, heritage and functional art.

Apply the glassware & crystal overlay to bend any ELEVATE asset toward celebration, hospitality and heirloom craft.

Apply the jewellery & accessories overlay to bend any ELEVATE asset toward identity, symbolism and meaningful gifting.

Apply the textile & linen overlay to bend any ELEVATE asset toward tactile comfort, natural fibre and heritage weave.

Apply the wooden-furniture overlay to bend any ELEVATE asset toward heirloom craft, sustainability and considered investment.

Use when the user has a list of keywords and wants to group them into topic clusters, content silos, or intent categories. Triggers on "cluster keywords," "group keywords," "keyword silos," "topic clusters," "keyword mapping," or "organise keywords."

Use when the user wants to find keyword ideas, related searches, or keyword suggestions for a topic or seed keyword. Triggers on "keyword ideas," "find keywords," "what keywords should I target," "keyword suggestions," "related keywords," or "keywords for [topic]."

When the user wants to plan a product launch, feature announcement, or release strategy. Also use when the user mentions 'launch,' 'Product Hunt,' 'feature release,' 'announcement,' 'go-to-market,' 'beta launch,' 'early access,' 'waitlist,' 'product update,' 'how do I launch this,' 'launch checklist,' 'GTM plan,' or 'we're about to ship.' Use this whenever someone is preparing to release something publicly. For ongoing marketing after launch, see marketing-ideas.

When the user wants to create, plan, or optimize a lead magnet for email capture or lead generation. Also use when the user mentions "lead magnet," "gated content," "content upgrade," "downloadable," "ebook," "cheat sheet," "checklist," "template download," "opt-in," "freebie," "PDF download," "resource library," "content offer," "email capture content," "Notion template," "spreadsheet template," or "what should I give away for emails." Use this for planning what to create and how to distribute it. For interactive tools as lead magnets, see free-tools. For writing the actual content, see copywriting. For the email sequence after capture, see emails.

Use when the user wants to find link-building opportunities — domains that link to competitors but not to them, resource pages, or guest-post targets. Triggers on "link building," "find backlink opportunities," "link prospects," "where to get links," "outreach targets," or "guest post sites."

When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (ads, social, emails, etc.).

When the user wants to apply psychological principles, mental models, or behavioral science to marketing. Also use when the user mentions 'psychology,' 'mental models,' 'cognitive bias,' 'persuasion,' 'behavioral science,' 'why people buy,' 'decision-making,' 'consumer behavior,' 'anchoring,' 'social proof,' 'scarcity,' 'loss aversion,' 'framing,' or 'nudge.' Use this whenever someone wants to understand or leverage how people think and make decisions in a marketing context. For applying psychology to specific pages, see cro; for pricing tactics, see pricing; for copy framing, see copywriting.

Assemble the mover FOUNDATION Strategic Blueprint — synthesize Company, Market and Customer into the Aligned Foundation Grid, carry the verified compliance facts, and write the three AI context blocks. Use to close the mover Foundation before ATTRACT.

Map the mover's competitive set into the fixed six-tier taxonomy — each named local rival's stated value proposition and review-evidenced weaknesses, plus the field-wide gap no rival credibly owns. Use when reading the moving-industry competitive field for the Market pillar of the Foundation.

Capture the mover's regulatory facts as checkable data — license regime (intrastate state permit vs interstate USDOT+MC), FMCSA estimate types with exact required language, state deposit/cancellation rules, and the banned-claims checklist every later stage's copy is linted against. The mover-only Foundation skill; no ecommerce equivalent.

Build the three mover FOUNDATION customer avatars — relocating family, senior downsizing, commercial office move — as full nine-cell Segment grids, each anchored on its trigger moment and its dominant need for Certainty. Use to deepen the mover's three drafted personas into evidence-grounded avatars before the Foundation blueprint.

Define a moving company's Unique Mechanism — the operational answer to the trade's

Map the mover FOUNDATION watering holes — the named channels where a moving customer's attention concentrates, scored on presence, competitive density and voice fit — and build the channel bullseye from the mover's own market-rank data. Use when choosing where the mover's HOOK fires.

NURTURE — draft a speed-led cart and checkout abandonment recovery sequence that recovers the near-sale by naming and dissolving the likely objection, reserving any incentive for the final message. Use to convert the warmest non-buyers.

NURTURE — draft the segmented nurture Sequence Map and a primary value-led email sequence that converts the patient majority over time. Use after Foundation when leads accumulate from IDENTIFY and SELL without a follow-up system.

NURTURE — draft a re-engagement / win-back sequence that reclaims leads gone quiet for 60–90 days, then releases the unresponsive cleanly to protect deliverability. Use when a segment of the list has stopped opening.

NURTURE — draft retargeting ad copy for product-page viewers and cart abandoners that complements the email nurture and works the same intent across paid channels. Use to re-engage high-intent visitors who did not convert.

NURTURE — draft the welcome sequence that converts a fresh GIFT opt-in into a first purchase across the warmest window you will ever have. Use after the GIFT delivery email exists, to extend it into a full value-led arc.

When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are signing up but not sticking around. For signup/registration optimization, see signup. For ongoing email sequences, see emails.

When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.

When an agent or user needs something measured before it is changed — test suite runtime, gate throughput, memory pressure, worker concurrency, or a suspected regression. Also use when the user says "why is this slow," "how long does this take," "did that make it faster," "the box is thrashing," "how many can we run in parallel," or "measure this." Use this whenever a number is the deliverable. For deciding what to test, see test-strategy. For a live outage, see incident-response.

When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.

When the user wants help with pricing decisions, packaging, or monetization strategy. Also use when the user mentions 'pricing,' 'pricing tiers,' 'freemium,' 'free trial,' 'packaging,' 'price increase,' 'value metric,' 'Van Westendorp,' 'willingness to pay,' 'monetization,' 'how much should I charge,' 'my pricing is wrong,' 'pricing page,' 'annual vs monthly,' 'per seat pricing,' or 'should I offer a free plan.' Use this whenever someone is figuring out what to charge or how to structure their plans. For in-app upgrade screens, see paywalls.

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 create SEO-driven pages at scale using templates and data. Also use when the user mentions "programmatic SEO," "template pages," "pages at scale," "directory pages," "location pages," "[keyword] + [city] pages," "comparison pages," "integration pages," "building many pages for SEO," "pSEO," "generate 100 pages," "data-driven pages," or "templated landing pages." Use this whenever someone wants to create many similar pages targeting different keywords or locations. For auditing existing SEO issues, see seo-audit. For content strategy planning, see content-strategy.

Determine if a prospect is a good fit before investing time in a full pitch.

When the user wants to create, optimize, or analyze a referral program, affiliate program, or word-of-mouth strategy. Also use when the user mentions 'referral,' 'affiliate,' 'ambassador,' 'word of mouth,' 'viral loop,' 'refer a friend,' 'partner program,' 'referral incentive,' 'how to get referrals,' 'customers referring customers,' or 'affiliate payout.' Use this whenever someone wants existing users or partners to bring in new customers. For launch-specific virality, see launch.

Design the REFINE A/B test plan — one constraint-targeted experiment with a hypothesis, single variable, sample size and read date, ready to run against the weakest lever. Use during the Refine step.

Build the REFINE attribution model — choose the multi-touch model, map the avatar's journey touchpoints, and re-credit channels so budget follows true contribution. Use during the Refine step.

Run the REFINE campaign analysis — diagnose channel, audience, creative and funnel performance against benchmark, then prioritise the highest-leverage optimisation. Use during the Refine step.

Build the REFINE Full-Funnel Dashboard — every lever's metric down a single column against its benchmark band, with the weakest link flagged. Use during the Refine step.

Build the REFINE performance report — a multi-level reporting framework with KPI hierarchy, executive summary and prioritised optimisation insights. Use during the Refine step.

Build the REFINE ROI calculation — ROAS, profit-ROI, CLV payback and a channel ROI matrix against break-even, with budget-reallocation hypotheses. Use during the Refine step.

Run the REFINE web-performance audit — Core Web Vitals and load/checkout speed diagnosed and prioritised by conversion impact across the funnel. Use during the Refine step.

When an agent or user needs to know whether something is actually shippable, or why a release is being held. Also use when the user says "can we ship this," "is this live," "did that deploy," "why isn't my fix in prod," "are we green," "ready to release," or "what's blocking the deploy." Use this whenever the gap between "the code is written" and "the thing is live" is the question. For probing a surface for holes, see security-audit. For a broken production, see incident-response.

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.

When the user wants to mint a reward program, set earn rules, or award and redeem points for a customer, agent, or wallet. Also use when the user mentions "loyalty program," "reward points," "earn rules," "redeem points," "on-chain rewards," "referral rewards," or "points that are real money." Use this whenever someone wants to run a loyalty or points program without a points database. For general payment gateway setup, see the pay skill.

When an agent or user needs a feature doc, runbook, or technical explanation written or a stale one found. Also use when the user says "document this," "write the runbook," "explain how this works," "is this doc still true," "update the docs," "what does the next person need to know," or "write it up." Use this whenever the deliverable is durable prose about a system. For marketing copy, see copywriting. For deciding a design, see architecture-review.

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps.' Use this for any document or asset that helps a sales team close deals. For competitor comparison pages and battle cards, see competitors. For marketing website copy, see copywriting. For cold outreach emails, see cold-email.

When the user wants to add, fix, or optimize schema markup and structured data on their site. Also use when the user mentions "schema markup," "structured data," "JSON-LD," "rich snippets," "schema.org," "FAQ schema," "product schema," "review schema," "breadcrumb schema," "Google rich results," "knowledge panel," "star ratings in search," or "add structured data." Use this whenever someone wants their pages to show enhanced results in Google. For broader SEO issues, see seo-audit. For AI search optimization, see ai-seo.

When an agent or user needs a surface probed for auth holes, identity spoofing, unenforced authority, or reachability from where the code actually runs. Also use when the user says "is this secure," "can someone bypass this," "audit this endpoint," "check the auth," "who can call this," "is this exposed," or "did we leave a hole." Use this whenever the question is whether a defence actually holds. For reading a diff generally, see diff-review. For the walk-up authority model specifically, start here.

Write a SELL Amazon listing — title, bullets, description and backend terms — built on the unique mechanism for the marketplace.

Write SELL benefit bullets that translate features into outcomes for the benefits section of the sales-page architecture.

Audit a SELL sales page and checkout against the nine-section architecture to find the leaks suppressing conversion.

Write SELL call-to-action section copy — one primary action, repeated — for the closing section of the sales-page architecture.

Write SELL objection-handling copy that surfaces and dismantles the prospect's real reasons not to buy for the sales page and FAQ.

Write a SELL persuasive product description built around the unique mechanism for the product page.

Write SELL sales-page hero headlines that lead with the dream outcome for the promise section of the sales-page architecture.

When the user wants to audit, review, or diagnose SEO issues on their site. Also use when the user mentions "SEO audit," "technical SEO," "why am I not ranking," "SEO issues," "on-page SEO," "meta tags review," "SEO health check," "my traffic dropped," "lost rankings," "not showing up in Google," "site isn't ranking," "Google update hit me," "page speed," "core web vitals," "crawl errors," or "indexing issues." Use this even if the user just says something vague like "my SEO is bad" or "help with SEO" — start with an audit. For building pages at scale to target keywords, see programmatic-seo. For adding structured data, see schema. For AI search optimization, see ai-seo.

Use when the user wants ongoing SEO guidance, wants to understand why something isn't ranking, needs a prioritised action plan, or asks general "how do I improve my SEO" questions. Triggers on "improve SEO," "SEO advice," "help with SEO," "why am I not ranking," "SEO roadmap," or "SEO quick wins."

Use when the user wants to start an SEO project, set up rank tracking, configure an audit schedule, or establish SEO baselines for a new domain. Triggers on "start SEO," "set up rank tracking," "SEO project," "track rankings," "new SEO campaign," or "SEO for a new site."

SHARE — develop the long-form case study from a captured testimonial: a challenge → solution → result narrative with verifiable specifics, repurposable into HOOK, SELL and NURTURE social proof. Use once a standout testimonial has been gathered.

SHARE — design the referral programme: the trigger, two-sided incentive and frictionless mechanism that turns a delighted customer into the source of the next, closing the advocacy spiral. Use after EDUCATE confirms customer success.

SHARE — write the triggered review request: subject lines, a short body and the specific question that defeats the blank page, fired at the peak-delight moment and deep-linked to the review box. Use after EDUCATE confirms customer success.

SHARE — craft the personal testimonial outreach: a non-automated ask to a standout customer plus the guiding questions that draw out a feature-worthy story, with video kept optional. Use after EDUCATE flags a standout success.

SHARE — brief the UGC campaign: a concrete prompt, hashtag, low bar to participate and recognition-led incentive that turns customers in active, successful use into creators of repurposable proof. Use after EDUCATE confirms product in successful use.

SHARE — design the VIP advocacy programme: a tiered recognition system for the most delighted, highest-value customers that turns status into authentic ambassadorship and referrals. Use after EDUCATE identifies a high-value, delighted cohort.

When the user wants to optimize signup, registration, account creation, or trial activation flows. Also use when the user mentions "signup conversions," "registration friction," "signup form optimization," "free trial signup," "reduce signup dropoff," "account creation flow," "people aren't signing up," "signup abandonment," "trial conversion rate," "nobody completes registration," "too many steps to sign up," or "simplify our signup." Use this whenever the user has a signup or registration flow that isn't performing. For post-signup onboarding, see onboarding. For lead capture forms (not account creation), see cro.

When the user wants to plan, map, or restructure their website's page hierarchy, navigation, URL structure, or internal linking. Also use when the user mentions "sitemap," "site map," "visual sitemap," "site structure," "page hierarchy," "information architecture," "IA," "navigation design," "URL structure," "breadcrumbs," "internal linking strategy," "website planning," "what pages do I need," "how should I organize my site," or "site navigation." Use this whenever someone is planning what pages a website should have and how they connect. NOT for XML sitemaps (that's technical SEO — see seo-audit). For SEO audits, see seo-audit. For structured data, see schema.

When the user wants help creating, scheduling, or optimizing social media content for LinkedIn, Twitter/X, Instagram, TikTok, Facebook, or other platforms. Also use when the user mentions 'LinkedIn post,' 'Twitter thread,' 'social media,' 'content calendar,' 'social scheduling,' 'engagement,' 'viral content,' 'what should I post,' 'repurpose this content,' 'tweet ideas,' 'LinkedIn carousel,' 'social media strategy,' 'grow my following,' 'TikTok video,' 'Reels,' 'Shorts,' 'video script,' 'video hook,' 'short-form video,' or 'create a reel.' Use this for social media content creation, repurposing, scheduling, and short-form video scripting. For broader content strategy, see content-strategy. For paid video ads, see ad-creative.

When a sizeable task has arrived as a sentence and has to become work somebody can finish — the eight spec fields, with deliverables as ROWS a machine can turn into child tasks. Use when the user or an agent says "spec this", "write the spec", "break this into deliverables", "what are the child tasks", "this task has no proof", or when a FEATURE/SCHEMA-tier task reaches the board carrying prose notes. For deciding the SHAPE of a change, see architecture-review. For sizing it, the sizer answers first. For asking about the holes a spec already knows it has, see interview.

Tell it once. When a person or an agent has a story and wants it made real — "here is my story", "I want to build", "tell your story", "what happened was", "once upon a time", or any sentence that names a world, people, a want and a turn — use this skill to shape it into the seven beats (World · Cast · Knock · Want · Way · Turn · Lesson), file it as a story on the board, and let the story-intake workflow mint the promise the AI signs. For the promise's terms and proof see promise-make; for building the deliverables see the factory; for the framework itself see text/story.md and text/dictionary.md § Once.

The chain half — Move packages generated from schema/sui.tql, promise settlement on chain, stake verification and replay defence, and what is safe to read versus what spends. Use when touching pay/contracts/, move.ts codegen, promise:settle's on-chain leg, tasks:stake, sui-stake-verify, a publish or an UpgradeCap question, or any claim about what is deployed on testnet or mainnet. Triggers — "settle on chain", "mint the package", "is this deployed", "verify the stake", "generated Move", "can we upgrade the package".

When an agent or user needs to decide what a change must prove, which test lane to run, or whether an existing check is real. Also use when the user says "what should I test," "which tests do I run," "is this covered," "why is the suite slow," "did the tests actually run," "add a test for this," or "this passed but I don't trust it." Use this whenever the question is about proof rather than code. For measuring runtime, see perf-audit. For reading a diff, see diff-review. For whether the proof is enough to ship, see release-gate.

The pheromone economy — how a weight is deposited, how it decays, and how it is chosen. Use whenever a change touches mark/warn/fade/follow, claw_paths, tag-match.ts, matchSubscribers, reputation ranking, routing weight, k-factor, conversion or share rate, or any number that decides who receives the next signal. Triggers — "why did this route here", "the weights look wrong", "add a mark", "tune the decay", "should this deposit more", "exploration vs exploitation", "the router always picks the same one". For the six verbs' contracts see text/contracts.md; for the story funnel see the story skill.

The brain of record — TypeQL against the ONE substrate on TypeDB 3.12.1. Use when editing any .tql under schema/, writing a fun, composing match/insert/update/put, reading through the /v1/ HTTP API, or diagnosing a TypeDB error code or a query that hangs. Triggers — "write a TypeQL query", "add a fun", "change the schema", "deploy the schema", "this query times out", "why is this .tql rejected", "TypeDB 2.x vs 3.x", "which schema files are deployed". Depth lives in .claude/skills/typedb; this is the runtime agent's copy of the rules that bite.

Design the UPSELL bundle offer — two or more related products combined at a price below their separate total, lifting AOV by reducing decisions and raising perceived value.

Write the UPSELL cross-sell recommendations — "frequently bought together" companion offers whose relevance to the primary product is instant and self-evident.

Design the UPSELL loyalty programme — a tiered reward system that lifts repeat purchase and AOV while seeding the GROW level's EDUCATE and SHARE steps.

Write the UPSELL in-cart order bump — a small, low-friction checkbox add-on shown at checkout that lifts AOV without risking the primary conversion.

Write the UPSELL post-purchase one-click offer — the thank-you-page or confirmation-email upsell that captures commitment, buyer's high and zero payment friction.

When the user wants to create, generate, or produce video content using AI tools or programmatic frameworks. Also use when the user mentions 'video production,' 'AI video,' 'Remotion,' 'Hyperframes,' 'HeyGen,' 'Synthesia,' 'Veo,' 'Sora,' 'Runway,' 'Kling,' 'Seedance,' 'Hailuo,' 'MiniMax,' 'Pika,' 'Hunyuan,' 'Wan,' 'video generation,' 'AI avatar,' 'talking head video,' 'programmatic video,' 'video template,' 'explainer video,' 'product demo video,' 'video pipeline,' or 'make me a video.' Use this for video creation, generation, and production workflows. For video content strategy and what to post, see social. For paid video ad creative, see ad-creative.

The tone, voice, and prose-craft standard for the ELEVATE Ecommerce Framework book. Use whenever writing, drafting, rewriting, or editing any chapter or content in book/ (HOOK, GIFT, IDENTIFY, ENGAGE, SELL, NURTURE, UPSELL, EDUCATE, SHARE, Foundation, Refine), or any prose that will sit alongside it. Owns HOW the writing sounds; chapter-template.md owns the structure. Apply both together.

When an agent needs to inspect a workflow's edge weights and propose a fix for a bottleneck. Also use when the user mentions "workflow is slow," "why does this workflow stall," "optimise this workflow," "bottleneck edge," or "which path keeps failing." Use this whenever the ask is about a specific workflow's traversal history, not workflow design from scratch. For a system that is slow rather than a workflow that stalls, see perf-audit. For a workflow failing live right now, see incident-response. For building a new workflow, see the workflow templates catalog instead.