sidchaudhary
User78 GTM skills for Claude Code — 7 GTM roles, 8 store loops, one shared setup skill. Lifecycle segmentation, deal scoring, creative direction, and more. Built by Intempt.
Categories
Indexed Skills (113)
competitive-analysis
Two modes. Mode A researches a competitor from public sources into a structured, comparable profile: positioning, pricing, strengths and weaknesses, and the competitive implications. Mode B converts a prospect's known tool stack into a call-ready displacement angle: the specific inefficiency that stack creates, two call questions, and an email hook. Use when you need deep competitor research, a displacement angle for a named prospect, or both. Boundary: `win-loss-analysis` finds which competitors actually beat you using your own closed deals, whereas this skill works from public sources and a stated stack.
the-90-second-brief
Researches a company and produces a structured 90-second rep brief covering what the company does, what changed recently, and the strongest outreach angle. Use when the user provides a company name or domain and wants a pre-call or pre-email research brief.
the-citation-auditor
Audit and improve how citable and extractable a site's content is for AI answer engines (ChatGPT, Perplexity, Google AI Overviews, Claude, Gemini, Copilot): structure, authority signals, and machine-readable files. Use when the user wants their content or brand cited in AI-generated answers, not just ranked in traditional search.
the-theme-miner
Extract signal from customer research assets (transcripts, reviews, tickets, surveys) and synthesize it into themes, quote banks, and evidence-based personas. Use when the user has customer research material to analyze, or wants to build personas grounded in real evidence rather than assumption.
the-competitor-dossier
Two modes. Mode A researches a competitor from public sources into a structured, comparable profile: positioning, pricing, strengths and weaknesses, and the competitive implications. Mode B converts a prospect's known tool stack into a call-ready displacement angle: the specific inefficiency that stack creates, two call questions, and an email hook. Use when you need deep competitor research, a displacement angle for a named prospect, or both. Boundary: `the-win-loss-analyzer` finds which competitors actually beat you using your own closed deals, whereas this skill works from public sources and a stated stack.
product-context
Builds the shared context file every other gtm skill reads, researching the company first and asking only for what research cannot establish: positioning, ICP, brand voice and its banned words, competitors, objections, lifecycle stages, scoring definitions, metrics and the brand-kit pointers. Anything unverifiable is tagged as needing input rather than guessed. Run this first, before any other gtm skill. Use when setting up the pack, when another skill reports the context file is missing, or when positioning, ICP or pricing has changed since it was last built. Boundary: this is the only skill that writes the shared context file, and it produces no campaign, copy or analysis output itself.
account-plan
Builds the engagement plan for one named strategic account: a buying committee map that names the roles still missing, a multi-threading assessment against the account's realistic committee size, and a 90-day action plan with an owner per play. Researches the account from public sources before asking for anything the web can answer. Use when a deal matters enough to plan deliberately, when it is single-threaded on one contact, or when a committee has gone quiet. Boundary: `opportunity-scoring` scores an existing deal's health and intent, while this skill builds the relationship plan for working the account. For one specific upcoming conversation use `call-preparation`.
opportunity-scoring
Scores one deal in depth on two independent axes, health and buyer intent, tracks the direction of travel since the last review, checks MEDDIC or BANT completeness, and returns a prioritised list of three to five specific next steps from where the deal lands. Use when a single deal needs an honest read before a forecast call, a renewal conversation, or a decision to keep investing in it. Boundary: `pipeline-review` triages the whole pipeline to decide which deals deserve this level of attention. For renewal risk on an existing customer use `opportunity-scoring`.
pipeline-review
Reads a whole pipeline export and returns only what genuinely needs attention: deal velocity against your own stage norms, deals stuck past their stage median, risk signals, and where the forecast is most likely to slip. Lists only the deals that warrant action rather than padding to a fixed count. Use for a weekly pipeline review, before a forecast call, or when the pipeline number looks fine but the deals feel soft. Boundary: `opportunity-scoring` scores one deal in depth, while this skill triages across all of them to decide which ones deserve that.
win-loss-analysis
Analyzes a batch of closed-won and closed-lost deals to find the real, evidence-backed reasons deals are actually won or lost, ranked by frequency, not a gut-feel retro. Use when the user wants to know why deals are actually closing or dying, not just track that they did. Pairs with objection-handling and competitive-analysis.
creative-brief
Turns a product and audience into a creative brief: distinct messaging angles selected from a fixed vault of fourteen, each mapped to a funnel stage and a channel, with placement specs and the reason that angle suits that stage. Use when starting a new ad campaign, when existing creative has fatigued and every variant is saying the same thing, or when a brief is needed before any asset gets designed. Boundary: this decides what the creative says and where it runs. `product-photography` then directs the photography and `onboarding-video` produces video. For the wording of a specific LinkedIn opening use `hook-writer`.
hook-writer
Takes a LinkedIn post draft and generates four scored hook variants for the opening one or two lines before the see-more cutoff, each built on a distinct psychological framework, with a recommendation and the reason it wins. Use when a post's opening feels flat, or when testing hooks before publishing. Boundary: LinkedIn post openings only. `cold-email` does the equivalent job for cold email subject lines, and `cold-email` writes the opening line of a cold email body.
onboarding-video
Produces a short conversion-focused onboarding video in Remotion for an iOS app, Android app or website, embedded into an onboarding flow to move New Customers toward their activation moment, with each beat mapped to a conversion milestone that can be tracked. Use when asked to create, build or generate an onboarding video, app preview, activation demo, or any short video that demonstrates a product feature to drive activation. Boundary: `product-photography` directs still photography and `creative-brief` produces the messaging brief. This skill renders an actual video.
product-photography
Turns a product into photography direction as a shootable set: subject, styling, environment, lighting, composition and camera treatment composed from a block system, scoped to five to eight images per product and matched to the store's existing catalogue treatment. Use when briefing a photographer or an image generator, before a product shoot, or when catalogue imagery is visually inconsistent from product to product. Boundary: `creative-brief` decides the messaging angle and placement before the shoot, and `product-page-optimization` reviews a live product page including its images. This skill only directs new imagery.
tone-of-voice
Analyses real content samples and extracts a brand voice profile as a checkable artifact: tone dimensions each carrying at least one followable rule, required and banned vocabulary, sentence and paragraph patterns, channel adaptations, and a weighted scorecard with a publish-ready threshold to grade drafts against. Use when onboarding a writer or agency, when AI-generated copy is drifting off-brand, or when nobody on the team can say concretely what on-brand means. Boundary: `.agents/product-context.md` carries a short voice summary, while this skill produces the full profile and the scorecard.
anomaly-detection
Takes a time series of one metric and flags which recent points are genuinely outside its normal range, using a stated trailing-average-and-deviation method, not a gut read of a chart. Use when the user has a week's or month's worth of numbers for a metric and wants to know if something in it is actually unusual. Boundary: this skill flags anomalies in data the user provides. For designing the dashboard that surfaces this metric in the first place, use `kpi-dashboard`.
benchmark-analysis
Takes one of the user's own metrics and checks it against a stated benchmark source, returning a clear over/under read and what that gap actually means. Use when the user wants to know if a number (churn rate, CAC, conversion rate, NPS) is good or bad relative to a real reference point, not just the number in isolation. Boundary: this skill does not have a live connection to any benchmark database. It compares against whatever source the user supplies, or discloses plainly when it is using general public knowledge instead.
cohort-analysis
Groups customers by acquisition period and tracks a retention or revenue metric across the periods that follow, returned as a cohort table. Use when the user wants to know whether newer customers are performing better or worse than older ones, not just a single blended average. Boundary: this skill builds the cohort table itself. For the dashboard that displays it alongside other KPIs, use `kpi-dashboard`. For comparing the result against outside industry numbers, use `benchmark-analysis`.
contribution-margin
Builds a per-SKU or per-order contribution margin stack (CM1, CM2, CM3) from raw revenue, cost, fee, and ad spend inputs, so the user can see which products actually make money after every variable cost, not just after product cost. Use when ROAS looks fine but profit doesn't, before scaling spend on a product, or when deciding which SKUs are worth promoting. Boundary: this skill computes margin from numbers the user hands over right now. For designing the recurring dashboard that surfaces margin over time, use `kpi-dashboard`.
ecommerce-returns
Takes a structured returns or RMA export with reason codes tied to SKUs and finds which SKUs have a genuine return concentration problem, and which coded reason is the likely root cause. Use when a return rate is rising, a specific SKU returns far above the catalog average, or returns are logged as a cost line instead of mined for the fix behind them. Boundary: this skill works from structured, coded return reasons tied to SKUs. If the input is free-text reviews or support tickets with no reason-code field, say so: the coded-reason analysis here does not apply and the raw text needs reading rather than tallying.
growth-strategy
Produces a prioritised growth plan: a maturity read, the candidate levers scored on effort, risk and reward, channel priorities, a 70-20-10 allocation where there is ongoing capacity, and an explicit statement of what is being declined for now. Use for quarterly or annual growth planning, or when there are more good ideas than the team can actually run. Boundary: `conversion-funnel` diagnoses where one specific funnel loses people, and `ab-test` designs the test for a lever once it has been chosen.
kpi-dashboard
Designs a KPI dashboard: the metric list with an explicit formula per metric, the visualisation form chosen from the question each answers, alert thresholds, and a layout wireframe. Use when building or rebuilding a marketing, sales, exec, product or CS dashboard, or when an existing one is not being read. Boundary: this designs the dashboard and its thresholds. `anomaly-detection` then judges whether a specific movement is genuinely abnormal, and `weekly-report` writes the recurring narrative readout that sits on top.
shipping-cost-analysis
Compares what a store charges for shipping against what shipping actually costs, banded by order value and zone, and tests the free-shipping threshold against the store's real order distribution. Use when fulfillment cost is rising, the free-shipping threshold has never been recalculated, or margin looks worse on small orders than large ones. Boundary: differs from `contribution-margin`, which builds full order-level contribution margin across every cost line. This skill isolates shipping recovery and threshold placement only, and doesn't touch COGS, fees, or ad spend.
weekly-report
Produces one weekly operating readout for a store or product from exported performance, traffic, lifecycle, inventory, and support summaries, instead of scattered dashboards. Use when the user wants a single weekly view of what changed, what likely caused it, and what to do next. Boundary: this skill summarizes across whatever data the user brings this week. For a deep read on one specific area (margin, cohorts, checkout, search), use the matching skill directly and feed its output in here as one of the week's inputs.
ab-test
Designs a runnable experiment: the hypothesis stated so that it can actually fail, the variants, Bayesian allocation with Thompson sampling, guardrail metrics, a holdout, required sample size and duration, explicit exit criteria, and the validity threats that would invalidate the read. Use when planning an A/B or multi-armed test, or when a previous test produced a result nobody trusts. Boundary: `website-personalization` designs personalisation rules that deliberately serve different audiences different content with no winner ever declared, whereas this skill runs a test to find one.
conversion-funnel
Diagnoses where a funnel loses people: stage-by-stage conversion against benchmarks, the drop-offs ranked by the spread they represent rather than by the worst absolute number, likely root causes, and an ordered fix roadmap. Use when conversion is weak on a marketing, sales or product funnel and it is not yet clear which step is responsible. Boundary: locates and ranks the leak, while `ab-test` designs the test for the fix. For checkout specifically use `checkout-optimization`, and for post-signup activation use `onboarding-flow`.
landing-page
Designs a conversion-focused landing page: the copy framework matched to traffic source and awareness stage, section order, form length, proof placement, and prototype-ready HTML with Tailwind. Use for a lead capture page, a signup page or a launch page that does not exist yet. Boundary: builds a new page from scratch. `product-page-optimization` reviews an existing product detail page, and `checkout-optimization` reviews cart and checkout.
onboarding-flow
Designs the post-signup activation path: what happens between signup and first real value, in what order, which step is the actual aha moment rather than a convenient proxy for it, and how drop-off at each step gets diagnosed and fixed. Use when users sign up but do not activate, or when onboarding has never been designed deliberately. Boundary: covers signup to first value for a product. `email-campaign` writes the welcome messaging that carries it, and `conversion-funnel` diagnoses drop-off across any funnel rather than the activation path specifically.
paid-media-audit
Triages paid ad spend, using ROAS, CAC, and spend concentration across channels, campaigns, and audiences, to find where budget is being wasted rather than assuming the ad account is the whole problem. Use when CPA is rising, ROAS is falling, or the team wants to know which campaigns or audiences to cut before adding more budget. Boundary: pairs with `conversion-funnel`, which diagnoses drop-off at a specific page or funnel step; this works one level up, at the level of which channels, campaigns, and audiences are burning spend.
pricing-strategy
Designs pricing and packaging: the value metric to charge on, tier structure, the price points themselves, and the timing and framing of an increase. Flags the case where an absence of price objections is evidence of being underpriced. Use when setting prices for the first time, restructuring plans, or deciding whether and how to raise them. Boundary: sets the structure. `price-negotiation` handles discounting on one live deal, and `contribution-margin` computes what a given price actually earns after every variable cost.
website-personalization
Designs personalisation rules that map an audience to a content variant, with the eligibility condition, the fallback for everyone who matches nothing, and a per-experience measurement plan. Use for dynamic content on pages, in emails or in-app, once the segments exist. Boundary: this serves different audiences different content permanently, with no winner declared. `ab-test` runs a test to pick one winner instead. Segment definitions come from `customer-segmentation`.
call-notes
Reads a raw sales call transcript and extracts what the follow-up needs: deal signals, objections raised, pain points the prospect actually confirmed rather than ones the rep suggested, a stakeholder map, and one specific recommended next action. Use after a discovery call, before writing the follow-up email or updating the CRM record. Boundary: extracts deal facts for the follow-up and the CRM, while `call-preparation` grades the rep's own performance on that same call.
lead-routing
Designs the actual assignment logic for an already-qualified lead, round-robin, territory, account-owner, or score-threshold, with explicit tie-break and fallback rules. Use when leads are qualified but nobody has decided, in writing, exactly who they go to next. Boundary: `lead-management` designs the scoring model and lifecycle stages that decide whether a lead is qualified in the first place. This skill is the layer after that: once a lead is qualified, who actually gets it.
marketing-automation
Designs a marketing or sales automation as a specification: trigger, entry conditions, actions, branching, wait logic, error handling, the scheduled data assertions that catch a silent integration failure where nothing errors but values are wrong, plus a named owner, an audit date and a retirement condition. Use when automating an internal handoff or a repetitive process, or when an existing automation is misfiring and nobody can say why. Boundary: `customer-journey` designs customer-facing lifecycle journeys with messaging in them, while this skill designs the operational plumbing. `lead-management` covers lead scoring and routing specifically.
product-launch-checklist
Runs a one-time go/no-go readiness check before a product or campaign launch, covering stock, page, tracking, lifecycle flows, support, and margin as a checklist the launch owner signs off against. Use when a launch, restock, or spend increase is about to go live and the cost of finding a gap after the fact is high. Boundary: `marketing-automation` designs ongoing marketing and sales automation that runs indefinitely; this skill is a single pre-launch checklist for one specific launch date, not an automation build.
sales-enablement
Produces sales collateral: one-pagers, ROI calculators, proposal templates, and playbooks, mapped to buyer persona and deal stage. Use when a rep needs a specific asset to hand a prospect. Boundary: for objection-handling responses specifically, use objection-handling: that skill already owns the objection library in this pack. This skill covers every other enablement asset type.
churn-reduction
Designs the systemic churn machinery: the cancel flow and its offramps, dynamic save offers ranked by cost against the margin they protect, churn risk scoring, and dunning sequences for failed payments. Splits the churn number into voluntary and involuntary before designing anything, because the two need opposite fixes. Use when reducing churn systemically rather than winning back one gone-dark account. Boundary: `opportunity-scoring` reads risk on one named account, and `repeat-purchase-rate` addresses a missing second order rather than a cancellation.
customer-journey
Designs a multi-channel customer journey: the node sequence, conditional branching, wait logic, holdouts, exit conditions, and a global per-contact message cap across every channel rather than a cap per channel. Settles step count and channel mix before any messaging, because those drive recovery rates far more than copy does. Use for automation flows, onboarding, retention and win-back journeys. Boundary: designs the structure, while `email-campaign` writes the actual messages in each step. For internal operational automation use `marketing-automation`.
customer-segmentation
Builds lifecycle segments with RFM scoring calibrated against your own customer distribution rather than absolute cutoffs, plus behavioural signals, explicit filter logic per segment, and the staleness rule that says when a segment must be recomputed. Use for audience segmentation and targeting, or when existing segments have stopped matching reality. Boundary: defines who is in each segment. `email-campaign` and `customer-journey` then decide what those segments receive. For churn risk on one named account use `opportunity-scoring`.
email-campaign
Designs a lifecycle campaign end to end and decides whether it runs once or runs forever: email sequences with subject variants and deliverability gates, SMS and push with carrier registration and consent gates, and the recurring version of either with a cadence matched to how fast its signal actually moves. Use for welcome, nurture, convert, retain, win-back and announce campaigns on any channel, and when deciding whether a campaign should become an always-on motion. Boundary: writes the messaging. `customer-journey` designs the multi-step journey structure it sits inside, and `customer-segmentation` defines the audience it targets.
referral-program
Designs a customer referral or advocacy program - incentive structure, the moment it's offered, tiers, and anti-abuse rules - so growth comes from existing customers, not just new acquisition spend. Use when the user wants existing customers to actively bring in new ones, not just stay retained. Pairs with churn-reduction and customer-segmentation.
repeat-purchase-rate
Reviews a customer's post-first-purchase flow, reorder prompts, replenishment timing, second-purchase incentives, and pinpoints exactly what's blocking the next order. Use when repeat purchase rate is flat or falling, or the user wants to know why customers aren't coming back for a second order. Boundary: `customer-journey` designs a new multi-channel journey from scratch; this skill audits the flows that already exist against a fixed set of reorder stages and names the specific gap, it doesn't build the journey. `customer-segmentation` segments the whole customer base by RFM across all stages, not just the post-first-purchase window.
ad-copy
Picks the right classic copywriting formula for the placement and writes to it, pain-first structures for cold feeds and story structures only where length is earned, then diagnoses copy that reads fine but never earns the click, usually a formula with one step missing. Use to draft primary text, or when an ad gets impressions and no clicks. Boundary: `responsive-search-ads` writes Google assets against hard character limits; this writes long-form social copy, and `hook-writer` scores opening lines only.
ad-design
Turns an approved angle into finished, on-brand ad images and stages them in the ad account's image library, because an angle that never becomes a file never runs, and aims for native and specific rather than polished. Use after angles are approved and before the campaign is built. Boundary: `product-photography` directs photography from a composable block system and `creative-brief` writes the brief; this produces and uploads the finished ad file. `onboarding-video` covers onboarding video, not paid static.
ad-angles
Writes five or six genuinely different advertising angles for a single fixed offer, each naming a different buyer, a different pain and a different promised outcome, so the delivery system has something specific to aim with instead of one message wearing six costumes. Use when launching an offer, or when testing has killed the angles you had. Boundary: `creative-brief` briefs from a fixed library of fourteen angles mapped to funnel stages and placements; this invents new ones for one offer. Feed it `value-proposition` output and sharpen each line with `value-proposition`.
brand-kit
Reads a public website into a working brand kit, the offer and the proof and the voice and the colour and type, so ads can be written and designed without anyone writing a creative brief first. Use before building any creative, or when ads keep coming out looking like they belong to nobody. Boundary: `tone-of-voice` scores an existing body of writing across six dimensions from samples you supply; this extracts a whole kit from a live site in one pass, and writes nothing back to `.agents/product-context.md`.
promotional-campaigns
Builds a promotional campaign per social channel from what is actually working in the market for similar products, and measures whether a promotion that already ran added real profit or just pulled demand forward (baseline-versus-promo-versus-recovery). Use to design a promo grounded in live competitor and market activity, or to grade one after a sale ends, a promo calendar is about to repeat, discount codes are leaking, or revenue rose while profit stayed flat. Boundary: `pricing-strategy` (Experimentation Lead) designs standing pricing tiers and price points; this designs and measures time-boxed promotions.
budget-reallocation
Ranks every line on both platforms by what a conversion actually costs there, names which are donors and which are recipients, and models three transfer sizes with the projected conversions and blended return for each, including moving money between platforms rather than only within one. Proposes scenarios for approval and moves nothing. Use when the split between platforms was set by history rather than by evidence. Boundary: `scaling-facebook-ads` adds budget to one proven winner in small steps without resetting its learning, `paid-media-audit` finds waste without proposing where it should go instead, and `stockout-alerts` pauses for stock reasons; this shifts money between existing lines.
the-account-blueprint
Builds the engagement plan for one named strategic account: a buying committee map that names the roles still missing, a multi-threading assessment against the account's realistic committee size, and a 90-day action plan with an owner per play. Researches the account from public sources before asking for anything the web can answer. Use when a deal matters enough to plan deliberately, when it is single-threaded on one contact, or when a committee has gone quiet. Boundary: `the-deal-gauge` scores an existing deal's health and intent, while this skill builds the relationship plan for working the account. For one specific upcoming conversation use `the-call-coach`.
the-call-coach
Two modes for one specific meeting: pre-call prep, covering the agenda, discovery questions and the single thing that must be established, and post-call coaching, covering talk ratio, BANT or MEDDIC completeness, every objection raised and how it was handled, and a drill for the weakest habit. Use before a scheduled sales call, or immediately after one while the detail is fresh. Boundary: `the-transcript-miner` extracts deal facts from the same call for the follow-up and the CRM, while this skill grades the rep's own performance. `the-negotiation-coach` covers a pricing or terms conversation specifically.
the-deal-gauge
Scores one deal in depth on two independent axes, health and buyer intent, tracks the direction of travel since the last review, checks MEDDIC or BANT completeness, and returns a prioritised list of three to five specific next steps from where the deal lands. Use when a single deal needs an honest read before a forecast call, a renewal conversation, or a decision to keep investing in it. Boundary: `the-pipeline-scanner` triages the whole pipeline to decide which deals deserve this level of attention. For renewal risk on an existing customer use `the-renewal-tracker`.
the-negotiation-coach
Preps the negotiation strategy for one specific deal - anchor, concession ladder, walk-away point, and the questions that surface what the other side actually needs. Use before a pricing or terms conversation, not after it's already gone sideways. Pairs with the-deal-gauge and the-objection-playbook.
the-objection-playbook
Takes a product description, ICP and target persona and outputs the five most likely objections, each with a specific acknowledgment, a response, and the follow-up question that moves past it. Use when preparing for cold calls, onboarding a new rep, or building objection handling into a sequence before it launches. Boundary: this prepares responses in advance for a persona. `the-reply-classifier` handles an objection that has already arrived in a real reply, and `the-negotiation-coach` handles a live pricing or terms push on one deal.
the-pipeline-scanner
Reads a whole pipeline export and returns only what genuinely needs attention: deal velocity against your own stage norms, deals stuck past their stage median, risk signals, and where the forecast is most likely to slip. Lists only the deals that warrant action rather than padding to a fixed count. Use for a weekly pipeline review, before a forecast call, or when the pipeline number looks fine but the deals feel soft. Boundary: `the-deal-gauge` scores one deal in depth, while this skill triages across all of them to decide which ones deserve that.
the-renewal-tracker
Scores an existing account's renewal risk from usage and relationship signals, and names the one action most likely to change the outcome. Use when a renewal date is approaching and the user wants an honest risk read instead of assuming it's fine because nobody's complained. Pairs with the-deal-gauge and the-save-desk.
the-switch-angle
Takes a prospect's current tool stack and outputs the strongest competitive displacement angle specific to their configuration, grounded only in stack data the user actually provided: the specific inefficiency their stack creates, two questions to surface it on a call, and a one-line email hook. Use when the user wants to displace a competitor or when a prospect's tech stack is known.
the-win-loss-analyzer
Analyzes a batch of closed-won and closed-lost deals to find the real, evidence-backed reasons deals are actually won or lost, ranked by frequency, not a gut-feel retro. Use when the user wants to know why deals are actually closing or dying, not just track that they did. Pairs with the-objection-playbook and the-competitor-dossier.
the-activation-reel
Produces a short conversion-focused onboarding video in Remotion for an iOS app, Android app or website, embedded into an onboarding flow to move New Customers toward their activation moment, with each beat mapped to a conversion milestone that can be tracked. Use when asked to create, build or generate an onboarding video, app preview, activation demo, or any short video that demonstrates a product feature to drive activation. Boundary: `the-scene-composer` directs still photography and `the-angle-vault` produces the messaging brief. This skill renders an actual video.
the-angle-vault
Turns a product and audience into a creative brief: distinct messaging angles selected from a fixed vault of fourteen, each mapped to a funnel stage and a channel, with placement specs and the reason that angle suits that stage. Use when starting a new ad campaign, when existing creative has fatigued and every variant is saying the same thing, or when a brief is needed before any asset gets designed. Boundary: this decides what the creative says and where it runs. `the-scene-composer` then directs the photography and `the-activation-reel` produces video. For the wording of a specific LinkedIn opening use `the-hook-lab`.
the-dual-cut-writer
Draft two distinct LinkedIn post variants on a topic: an educational angle and an operator/contrarian angle, written in the brand's voice. Use when the user wants organic LinkedIn content to build authority or warm up a list before outbound.
the-hook-lab
Takes a LinkedIn post draft and generates four scored hook variants for the opening one or two lines before the see-more cutoff, each built on a distinct psychological framework, with a recommendation and the reason it wins. Use when a post's opening feels flat, or when testing hooks before publishing. Boundary: LinkedIn post openings only. `the-subject-line-lab` does the equivalent job for cold email subject lines, and `the-cold-opener` writes the opening line of a cold email body.
the-scene-composer
Turns a product into photography direction as a shootable set: subject, styling, environment, lighting, composition and camera treatment composed from a block system, scoped to five to eight images per product and matched to the store's existing catalogue treatment. Use when briefing a photographer or an image generator, before a product shoot, or when catalogue imagery is visually inconsistent from product to product. Boundary: `the-angle-vault` decides the messaging angle and placement before the shoot, and `the-pdp-reviewer` reviews a live product page including its images. This skill only directs new imagery.
the-voice-fingerprint
Analyses real content samples and extracts a brand voice profile as a checkable artifact: tone dimensions each carrying at least one followable rule, required and banned vocabulary, sentence and paragraph patterns, channel adaptations, and a weighted scorecard with a publish-ready threshold to grade drafts against. Use when onboarding a writer or agency, when AI-generated copy is drifting off-brand, or when nobody on the team can say concretely what on-brand means. Boundary: `product-context` captures a short voice summary inside the shared context file, while this skill produces the full profile and the scorecard.
the-anomaly-alert
Takes a time series of one metric and flags which recent points are genuinely outside its normal range, using a stated trailing-average-and-deviation method, not a gut read of a chart. Use when the user has a week's or month's worth of numbers for a metric and wants to know if something in it is actually unusual. Boundary: this skill flags anomalies in data the user provides. For designing the dashboard that surfaces this metric in the first place, use `the-kpi-blueprint`.
the-benchmark-check
Takes one of the user's own metrics and checks it against a stated benchmark source, returning a clear over/under read and what that gap actually means. Use when the user wants to know if a number (churn rate, CAC, conversion rate, NPS) is good or bad relative to a real reference point, not just the number in isolation. Boundary: this skill does not have a live connection to any benchmark database. It compares against whatever source the user supplies, or discloses plainly when it is using general public knowledge instead.
the-catalog-auditor
Audits a whole product catalog export for missing attributes, thin or empty descriptions, duplicate copy, and image gaps, ranked by revenue rather than row count. Use when the catalog has too many SKUs to review page by page, before a marketplace or feed push, or when only the best sellers seem to have real content. Boundary: `the-citation-auditor` audits blog and content pages for citability to AI search engines. This skill audits product catalog completeness at SKU scale, not content citability.
the-chargeback-pattern-finder
Takes a dispute or chargeback export and finds whether the disputes cluster by product, channel, geography, order value band, or payment method into a fraud pattern, or whether they're mostly service failures and friendly fraud, then weighs that against what over-blocking would cost in rejected good orders. Use when a dispute rate is rising, a payment provider has sent a warning, or the store wants to know how much of its chargeback problem is real fraud. Boundary: `the-anomaly-alert` flags a generic single-metric time series moving outside its normal range. This skill dates every dispute to the sale it belongs to, not the filing date, and clusters across the dimensions an export actually has instead.
the-cohort-tracker
Groups customers by acquisition period and tracks a retention or revenue metric across the periods that follow, returned as a cohort table. Use when the user wants to know whether newer customers are performing better or worse than older ones, not just a single blended average. Boundary: this skill builds the cohort table itself. For the dashboard that displays it alongside other KPIs, use `the-kpi-blueprint`. For comparing the result against outside industry numbers, use `the-benchmark-check`.
the-inventory-risk-scanner
Turns a SKU-level inventory export and sales history into a stockout/overstock risk brief, using a stated days-of-cover method against sales velocity and lead time, not a gut read of a stock report. Use when deciding which SKUs are safe to promote, which to protect from a planned campaign, or which are quietly overstocked. Boundary: differs from `the-anomaly-alert`, which flags one metric's time series against its own trailing average. This skill scores SKU-level stockout/overstock risk from on-hand units, sales velocity, and lead time, not a single metric's history.
the-kpi-blueprint
Designs a KPI dashboard: the metric list with an explicit formula per metric, the visualisation form chosen from the question each answers, alert thresholds, and a layout wireframe. Use when building or rebuilding a marketing, sales, exec, product or CS dashboard, or when an existing one is not being read. Boundary: this designs the dashboard and its thresholds. `the-anomaly-alert` then judges whether a specific movement is genuinely abnormal, and `the-weekly-reporter` writes the recurring narrative readout that sits on top.
the-lever-finder
Produces a prioritised growth plan: a maturity read, the candidate levers scored on effort, risk and reward, channel priorities, a 70-20-10 allocation where there is ongoing capacity, and an explicit statement of what is being declined for now. Use for quarterly or annual growth planning, or when there are more good ideas than the team can actually run. Boundary: `the-leak-finder` diagnoses where one specific funnel loses people, and `the-hypothesis-engine` designs the test for a lever once it has been chosen.
the-margin-builder
Builds a per-SKU or per-order contribution margin stack (CM1, CM2, CM3) from raw revenue, cost, fee, and ad spend inputs, so the user can see which products actually make money after every variable cost, not just after product cost. Use when ROAS looks fine but profit doesn't, before scaling spend on a product, or when deciding which SKUs are worth promoting. Boundary: this skill computes margin from numbers the user hands over right now. For designing the recurring dashboard that surfaces margin over time, use `the-kpi-blueprint`.
the-returns-miner
Takes a structured returns or RMA export with reason codes tied to SKUs and finds which SKUs have a genuine return concentration problem, and which coded reason is the likely root cause. Use when a return rate is rising, a specific SKU returns far above the catalog average, or returns are logged as a cost line instead of mined for the fix behind them. Boundary: this skill works from structured, coded return reasons tied to SKUs. If the input is free-text reviews or support tickets with no reason-code field, say so: the coded-reason analysis here does not apply and the raw text needs reading rather than tallying.
the-shipping-recovery-check
Compares what a store charges for shipping against what shipping actually costs, banded by order value and zone, and tests the free-shipping threshold against the store's real order distribution. Use when fulfillment cost is rising, the free-shipping threshold has never been recalculated, or margin looks worse on small orders than large ones. Boundary: differs from `the-margin-builder`, which builds full order-level contribution margin across every cost line. This skill isolates shipping recovery and threshold placement only, and doesn't touch COGS, fees, or ad spend.
the-weekly-reporter
Produces one weekly operating readout for a store or product from exported performance, traffic, lifecycle, inventory, and support summaries, instead of scattered dashboards. Use when the user wants a single weekly view of what changed, what likely caused it, and what to do next. Boundary: this skill summarizes across whatever data the user brings this week. For a deep read on one specific area (margin, cohorts, checkout, search), use the matching skill directly and feed its output in here as one of the week's inputs.
the-checkout-auditor
Audits a cart and checkout flow directly, using screenshots or a walkthrough plus policy details, to find specific friction points in forms, payment coverage, trust signals, and step count. Use when cart abandonment is high, checkout conversion is weak, or the team wants a pre-launch or pre-scale checkout review. Boundary: differs from `the-leak-finder`, which diagnoses funnel drop-off against conversion benchmarks; this is a direct UX audit of the checkout flow itself, not a benchmark comparison.
the-first-mile-mapper
Designs the post-signup activation path: what happens between signup and first real value, in what order, which step is the actual aha moment rather than a convenient proxy for it, and how drop-off at each step gets diagnosed and fixed. Use when users sign up but do not activate, or when onboarding has never been designed deliberately. Boundary: covers signup to first value for a product. `the-campaign-engine` writes the welcome messaging that carries it, and `the-leak-finder` diagnoses drop-off across any funnel rather than the activation path specifically.
the-hypothesis-engine
Designs a runnable experiment: the hypothesis stated so that it can actually fail, the variants, Bayesian allocation with Thompson sampling, guardrail metrics, a holdout, required sample size and duration, explicit exit criteria, and the validity threats that would invalidate the read. Use when planning an A/B or multi-armed test, or when a previous test produced a result nobody trusts. Boundary: `the-variant-router` designs personalisation rules that deliberately serve different audiences different content with no winner ever declared, whereas this skill runs a test to find one.
the-leak-finder
Diagnoses where a funnel loses people: stage-by-stage conversion against benchmarks, the drop-offs ranked by the spread they represent rather than by the worst absolute number, likely root causes, and an ordered fix roadmap. Use when conversion is weak on a marketing, sales or product funnel and it is not yet clear which step is responsible. Boundary: locates and ranks the leak, while `the-hypothesis-engine` designs the test for the fix. For checkout specifically use `the-checkout-auditor`, and for post-signup activation use `the-first-mile-mapper`.
the-page-shipper
Designs a conversion-focused landing page: the copy framework matched to traffic source and awareness stage, section order, form length, proof placement, and prototype-ready HTML with Tailwind. Use for a lead capture page, a signup page or a launch page that does not exist yet. Boundary: builds a new page from scratch. `the-pdp-reviewer` reviews an existing product detail page, and `the-checkout-auditor` reviews cart and checkout.
the-pdp-reviewer
Reviews an existing product detail page, using the page itself, reviews, and buyer questions, to find clarity, trust, proof, and objection gaps, then returns a prioritized edit brief. Use when a product page isn't converting or before sending more traffic to it. Boundary: differs from `the-page-shipper`, which generates new landing pages as HTML/Tailwind; this reviews a page that already exists and returns an edit brief, it doesn't generate new page code.
the-price-point-finder
Designs pricing and packaging: the value metric to charge on, tier structure, the price points themselves, and the timing and framing of an increase. Flags the case where an absence of price objections is evidence of being underpriced. Use when setting prices for the first time, restructuring plans, or deciding whether and how to raise them. Boundary: sets the structure. `the-negotiation-coach` handles discounting on one live deal, and `the-margin-builder` computes what a given price actually earns after every variable cost.
the-search-merchandiser
Turns onsite search query logs, including zero-result queries, into specific merchandising fixes: synonym rules, naming corrections, and collection-page gaps. Use when visitors search on the site but don't buy, when collection pages convert poorly, or when the team wants demand signal from real search behavior instead of a keyword tool. Boundary: differs from `the-leak-finder`, which diagnoses funnel drop-off against conversion benchmarks; this works specifically from search query exports, not funnel stage data.
the-spend-waste-finder
Triages paid ad spend, using ROAS, CAC, and spend concentration across channels, campaigns, and audiences, to find where budget is being wasted rather than assuming the ad account is the whole problem. Use when CPA is rising, ROAS is falling, or the team wants to know which campaigns or audiences to cut before adding more budget. Boundary: pairs with `the-leak-finder`, which diagnoses drop-off at a specific page or funnel step; this works one level up, at the level of which channels, campaigns, and audiences are burning spend.
the-variant-router
Designs personalisation rules that map an audience to a content variant, with the eligibility condition, the fallback for everyone who matches nothing, and a per-experience measurement plan. Use for dynamic content on pages, in emails or in-app, once the segments exist. Boundary: this serves different audiences different content permanently, with no winner declared. `the-hypothesis-engine` runs a test to pick one winner instead. Segment definitions come from `the-lifecycle-mapper`.
the-enablement-kit
Produces sales collateral: one-pagers, ROI calculators, proposal templates, and playbooks, mapped to buyer persona and deal stage. Use when a rep needs a specific asset to hand a prospect. Boundary: for objection-handling responses specifically, use the-objection-playbook: that skill already owns the objection library in this pack. This skill covers every other enablement asset type.
the-feed-auditor
Audits the actual data feed sent to Google Shopping, Meta, or another channel for required-attribute completeness, disapproval risk, and price or availability mismatches against the live site. Use when products are disapproved, Shopping or catalog ad performance drops without an obvious campaign cause, or a feed is about to be pushed to a new channel. Boundary: `the-catalog-auditor` (Data Analyst) audits the on-page storefront catalog content itself; this skill audits the feed data sent to an external channel, not the storefront page.
the-launch-readiness-check
Runs a one-time go/no-go readiness check before a product or campaign launch, covering stock, page, tracking, lifecycle flows, support, and margin as a checklist the launch owner signs off against. Use when a launch, restock, or spend increase is about to go live and the cost of finding a gap after the fact is high. Boundary: `the-workflow-builder` designs ongoing marketing and sales automation that runs indefinitely; this skill is a single pre-launch checklist for one specific launch date, not an automation build.
the-lead-router
Designs the actual assignment logic for an already-qualified lead, round-robin, territory, account-owner, or score-threshold, with explicit tie-break and fallback rules. Use when leads are qualified but nobody has decided, in writing, exactly who they go to next. Boundary: `the-routing-engine` designs the scoring model and lifecycle stages that decide whether a lead is qualified in the first place. This skill is the layer after that: once a lead is qualified, who actually gets it.
the-routing-engine
Designs the lead-to-opportunity layer between marketing and sales: MQL scoring model, routing rules, speed-to-lead SLAs, and lifecycle stage definitions. Use when leads aren't reaching sales fast enough, marketing and sales disagree on what counts as qualified, or handoff is undefined. Boundary: the-deal-gauge scores one opportunity; the-pipeline-scanner reports on the whole pipeline; this skill is the layer before either exists.
the-transcript-miner
Reads a raw sales call transcript and extracts what the follow-up needs: deal signals, objections raised, pain points the prospect actually confirmed rather than ones the rep suggested, a stakeholder map, and one specific recommended next action. Use after a discovery call, before writing the follow-up email or updating the CRM record. Boundary: extracts deal facts for the follow-up and the CRM, while `the-call-coach` grades the rep's own performance on that same call.
the-workflow-builder
Designs a marketing or sales automation as a specification: trigger, entry conditions, actions, branching, wait logic, error handling, the scheduled data assertions that catch a silent integration failure where nothing errors but values are wrong, plus a named owner, an audit date and a retirement condition. Use when automating an internal handoff or a repetitive process, or when an existing automation is misfiring and nobody can say why. Boundary: `the-flow-architect` designs customer-facing lifecycle journeys with messaging in them, while this skill designs the operational plumbing. `the-routing-engine` covers lead scoring and routing specifically.
the-cadence-clock
Design a recurring, scheduled marketing workflow (a loop with a defined check cadence, action trigger, self-check, and stop condition) matched to how fast the underlying signal actually changes. Use when the user wants an always-on marketing motion (weekly SEO scan, ad-fatigue check, churn watch) rather than a one-off task.
the-campaign-composer
Design email campaigns and sequences with subject lines, Liquid personalization, and deliverability best practices. Use for nurture, welcome, and retention emails.
the-campaign-engine
Designs a lifecycle campaign end to end and decides whether it runs once or runs forever: email sequences with subject variants and deliverability gates, SMS and push with carrier registration and consent gates, and the recurring version of either with a cadence matched to how fast its signal actually moves. Use for welcome, nurture, convert, retain, win-back and announce campaigns on any channel, and when deciding whether a campaign should become an always-on motion. Boundary: writes the messaging. `the-flow-architect` designs the multi-step journey structure it sits inside, and `the-lifecycle-mapper` defines the audience it targets.
the-flow-architect
Designs a multi-channel customer journey: the node sequence, conditional branching, wait logic, holdouts, exit conditions, and a global per-contact message cap across every channel rather than a cap per channel. Settles step count and channel mix before any messaging, because those drive recovery rates far more than copy does. Use for automation flows, onboarding, retention and win-back journeys. Boundary: designs the structure, while `the-campaign-engine` writes the actual messages in each step. For internal operational automation use `the-workflow-builder`.
the-lifecycle-mapper
Builds lifecycle segments with RFM scoring calibrated against your own customer distribution rather than absolute cutoffs, plus behavioural signals, explicit filter logic per segment, and the staleness rule that says when a segment must be recomputed. Use for audience segmentation and targeting, or when existing segments have stopped matching reality. Boundary: defines who is in each segment. `the-campaign-engine` and `the-flow-architect` then decide what those segments receive. For churn risk on one named account use `the-renewal-tracker`.
the-promo-impact-check
Measures whether a promotion or discount that already ran added real profit or just pulled demand forward, using a stated baseline-versus-promo-versus-recovery window comparison. Use when a sale just ended, a promo calendar is about to repeat, discount codes are leaking, or revenue rose while profit stayed flat. Boundary: `the-price-point-finder` (Experimentation Lead) designs future pricing tiers and price points; this skill measures the after-the-fact impact of a promotion that already happened, not future pricing design.
the-referral-architect
Designs a customer referral or advocacy program - incentive structure, the moment it's offered, tiers, and anti-abuse rules - so growth comes from existing customers, not just new acquisition spend. Use when the user wants existing customers to actively bring in new ones, not just stay retained. Pairs with the-save-desk and the-lifecycle-mapper.
the-repeat-purchase-check
Reviews a customer's post-first-purchase flow, reorder prompts, replenishment timing, second-purchase incentives, and pinpoints exactly what's blocking the next order. Use when repeat purchase rate is flat or falling, or the user wants to know why customers aren't coming back for a second order. Boundary: `the-flow-architect` designs a new multi-channel journey from scratch; this skill audits the flows that already exist against a fixed set of reorder stages and names the specific gap, it doesn't build the journey. `the-lifecycle-mapper` segments the whole customer base by RFM across all stages, not just the post-first-purchase window.
Showing top 100 of 113 skills by quality score. Browse the full catalog at /browse.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.