christopherswarup
UserRevenue Systems, GTM Operations, Applied AI — plus a public GTM Skills library for Claude (demand classification, targeting, ICP, metrics, and an orchestrator).
Categories
Indexed Skills (6)
buyer-commitment-mapper
Map content, CTAs, and sales discovery questions to the specific stage of buyer commitment they serve, using a six-stage arc across three phases (Recognize, Explore, Decide). Use whenever a user is planning a content calendar, auditing a website or nurture flow, building sales discovery questions, or asks why "good content" isn't converting. Trigger this whenever content or a CTA is proposed without a stated buying stage — an asset with no assigned stage is decorative, not functional, and this skill exists to catch that before budget is spent producing it.
demand-origin-classifier
Classify the origin of market demand for a product, offer, or segment — Dormant (market doesn't know it has the problem), Substitution (market solves it today with an inferior approach), or Active-Category (established, budgeted, actively shopping) — before setting messaging, campaign strategy, or lead-qualification thresholds. Use whenever a user is writing GTM messaging, designing a campaign, setting MQL/lead-scoring criteria, launching into a new segment, or asks why "more leads" or "more MQLs" isn't fixing a pipeline problem. Trigger this proactively whenever someone proposes lead-volume as a fix without having stated the demand type — misclassifying this is the single most common cause of GTM strategies that generate activity without revenue.
full-audience-value-diagnostic
Diagnose or defend marketing's value across every audience it actually serves — buyers, existing customers, sales, product, executives, employees, and partners/influencers — not pipeline alone. Use whenever a user is defending a marketing budget, writing a marketing strategy or business case, responding to "what does marketing actually do," or planning marketing's role in a broader GTM motion. Trigger this whenever marketing's contribution is being evaluated using pipeline/lead metrics alone — that framing systematically undercounts real value and produces bad budget and headcount decisions.
gtm-metrics-architect
Design or audit a GTM/marketing measurement system using a metric-class ladder (Activity, Output, Outcome, Impact) applied at the right organisational level (Org, Programme, Function, Tactic-type, Tactic), so every metric on a dashboard is tied to an actual decision. Use whenever a user is building a reporting dashboard, defining KPIs, auditing an existing report before it goes to leadership, or asks why metrics "look fine but nothing changes." Trigger this whenever a metric or dashboard is proposed without a stated decision it drives, or when Activity-level numbers (clicks, opens, follows) are being presented as if they proved business Impact.
icp-buying-center-builder
Build an Ideal Customer Profile sized against the realistically obtainable market (not total market) and defined at the buying-centre level (the specific department/function with the need), keeping stable "fit" attributes separate from fast-changing "intent" signals. Use whenever a user is defining an ICP, sizing a market opportunity, building a target-account data model, or setting up intent/signal scoring. Trigger this whenever an ICP or market-sizing exercise is proposed at the whole-account or whole-market level — that's the most common sizing error and it silently inflates every projection built on top of it.
market-account-prioritizer
Build a defensible target-account or ABM list using a two-gate screen — first a market/segment attractiveness-and-readiness screen, then an account-level scoring screen — instead of jumping straight to naming accounts. Use whenever a user is building an ABM program, a target account list, a territory plan, or prioritizing which segments/accounts to pursue with sales or marketing effort. Trigger this whenever someone proposes an account list, a "who should we target" question, or an ABM program without first having screened the market/segment level — an account list built without that screen inherits "who could buy" waste that no amount of account-level scoring fixes afterward.
Bio shown is the top-scored skill's repo description as a fallback — real GitHub bios land in a future update.