claude

doddle-gtm-skills

Doddle GTM OS — go-to-market orchestration: 32 skills and 7 agents (strategy, positioning, ICP, demand, pipeline, enablement, pricing, advocacy, international, measurement). Deterministic Python toolkit (dgtm) computes funnel math, unit economics, pricing, market sizing, scoring and pipeline audit; skills narrate. Synced from DoddleHQ/doddle-go-to-market-skills.

6 on GitHubby Doddle Teamv2.0.0MITupdated 17 days agogtm

Not in a marketplace yet, so it loads for one session with --plugin-dir.

Plugin doddle-gtm-skills in DoddleHQ/DoddleOS. Commands read from the repo's manifest — 17 days ago.

What it installs

Skills (32)

  • gtm-abm

    When the user wants to tier target accounts and run account-based plays — Tier 1/2/3, effort matched to value, owners and a success metric. Use for 'ABM tiers', 'tier our target accounts', 'account-based plan', 'which accounts get 1:1', 'score our target list'. Tiering criteria are user assumptions.

  • gtm-advocacy

    Design or review a customer advocacy program — references, reviews, referrals and community proof. Use when the user wants more proof assets, a reference program, review flywheel or referral motion.

  • gtm-battlecards

    When the user wants a competitive battlecard for a specific competitor — their pitch, where they win, where we win, landmines, objection handling and proof. Use for 'battlecard', 'compete against X', 'competitive one-pager', 'objection handling vs X', 'how do we beat X'. Never invents competitor cla

  • gtm-case-study

    When the user wants to turn a customer win into proof — a case study, a customer story, a reference narrative. Use for 'write a case study', 'customer story', 'success story', 'turn this win into proof'. Uses only user-supplied, verified results.

  • gtm-channel

    When the user wants to compare acquisition channels on unit economics — CAC, LTV:CAC and payback. Use for 'which channel is best', 'compare channels', 'channel economics', 'paid vs organic vs partner', 'where should we spend'. Inputs are assumptions the user supplies.

  • gtm-competitive

    When the user wants to analyse the competitive landscape or locate positioning gaps. Use for 'competitive analysis', 'competitive landscape', 'teardown a competitor', 'how do we position against them', 'build a battlecard'. Uses only facts the user supplies; never invents competitor statistics.

  • gtm-demand-gen

    When the user wants a demand generation plan against a pipeline target — funnel math, channel mix and cadence. Use for 'demand gen plan', 'how do we hit our pipeline target', 'plan our channels', 'funnel math for next quarter', 'pipeline target plan'. Defaults to the SMB segment.

  • gtm-enablement

    When the user wants to build a sales enablement program for the field team — onboarding, training, certification, content and a plan to close known skill gaps. Use for 'enablement program', 'train the sales team', 'ramp new reps', 'close skill gaps', 'field readiness'.

  • gtm-expansion

    When the user wants to grow revenue from existing customers — upsell, cross-sell and renewal plans built from recorded deals. Use for 'expansion plan', 'how do we grow accounts', 'upsell and cross-sell', 'renewal strategy', 'NRR plan', 'review our expansion deals'. Defaults to the SMB segment.

  • gtm-experimentation

    When the user wants to design a test before it runs — a hypothesis, metric and decision rule over a baseline funnel. Use for 'design an experiment', 'A/B test brief', 'what should we test', 'experimentation brief', 'set up a funnel test before we spend'. Baseline funnel counts are inputs.

  • gtm-forecasting

    When the user wants a revenue forecast built from recorded pipeline — coverage, commit cases and stage probabilities. Use for 'build a forecast', 'forecast from pipeline', 'commit and best case', 'will we hit number', 'forecast model'. Stage probabilities are the user's assumptions.

  • gtm-icp

    When the user wants to define or score an ideal customer profile. Use for 'define our ICP', 'ideal customer profile', 'who should we target', 'score these accounts', 'qualify our best-fit customers'. Weights and 0-100 scores are the user's assumptions; this skill never presents them as facts.

  • gtm-intl

    Rank candidate international markets and design a minimum launch pack for the winners. Use when the user asks about going international, localization, geo expansion or which country to enter next.

  • gtm-launch

    When the user wants to plan a product or feature launch or check launch readiness — objective, narrative, assets, channels, enablement and a readiness gate. Use for 'launch plan', 'GTM launch checklist', 'are we ready to launch', 'plan the launch of X', 'launch readiness'. Advisory; defaults to the

  • gtm-lead-scoring

    When the user wants to build or audit weighted fit-and-intent lead scoring. Use for 'lead scoring model', 'score our leads', 'fit and intent weights', 'which leads should sales work', 'weight these criteria'. Weights and scores are the user's assumptions.

  • gtm-market-sizing

    When the user wants to size a market — TAM, SAM, SOM — bottom-up from their own inputs. Use for 'how big is this market', 'TAM/SAM/SOM', 'how many accounts could we sell to', 'size the SMB opportunity'. Computes only from inputs the user provides.

  • gtm-messaging

    When the user wants to turn positioning into messaging — a messaging house, value proposition pillars, or persona and stage messages. Use for 'build a messaging house', 'messaging framework', 'value proposition pillars', 'what is our core message', 'message by persona'. Uses only the agreed position

  • gtm-metrics

    When the user wants a KPI scorecard for go-to-market — funnel conversion and unit economics in one place. Use for 'build our metrics scorecard', 'what KPIs matter', 'funnel and LTV in one view', 'track GTM performance', 'which numbers should we watch'. Distinguishes measured from assumed inputs.

  • gtm-onboarding

    When the user wants a customer onboarding plan that reaches first value fast — success criteria, milestones, owners, risks and an expansion path. Use for 'onboarding plan', 'customer onboarding', 'time to value', 'ramp this customer', 'implementation plan for a new customer'.

  • gtm-outbound

    When the user wants an outbound sequence and copy — cadence, channels and messaging for a target profile. Use for 'outbound sequence', 'cold email sequence', 'LinkedIn outreach plan', 'write our outbound cadence', 'prospecting copy'. The plan and copy are advisory.

  • gtm-packaging

    When the user wants to design or review packaging — tiers built on a value metric, with blended margin across the mix. Use for 'how should we package', 'good better best tiers', 'value metric', 'blended margin', 'tier mix', 'which plan should we sell'. Mix is an assumption supplied by the user.

  • gtm-partnerships

    When the user wants to design a partnership or channel alliance with clear mutual value. Use for 'partnership model', 'partner strategy', 'should we partner with X', 'co-marketing / reseller / integration partner', 'alliance plan'. Advisory work backed by the partnership-model framework.

  • gtm-persona

    When the user wants to define buyer personas for a segment. Use for 'define buyer personas', 'who are our buyers', 'persona template', 'what does the buyer care about', 'message to the economic buyer'. Uses only inputs the user supplies and never invents quotes or metrics.

  • gtm-pipeline-analytics

    When the user wants to audit their sales pipeline or deal export — win rate, cycle time, stage conversion, data hygiene. Use for 'pipeline audit', 'why is our pipeline weak', 'review our deals', 'sales metrics from this export'. Defaults to the SMB segment.

  • gtm-plg

    When the user wants a product-led growth loop from activation funnel counts — signup, activation, habit, monetization and referral. Use for 'product led growth', 'PLG loop', 'activation funnel', 'freemium conversion', 'self-serve growth plan'. Funnel counts are the user's inputs.

  • gtm-positioning

    When the user wants to define or sharpen positioning — who you serve, the alternative, the differentiated value and the proof. Use for 'positioning statement', 'how should we position', 'positioning canvas', 'why are we different', 'category narrative'.

  • gtm-pricing

    When the user wants to set or stress-test a price — gross margin and break-even from their own inputs. Use for 'what should we charge', 'pricing model', 'what is our margin', 'break-even units', 'is this price profitable'. Computes only from inputs the user provides.

  • gtm-reporting

    When the user wants a shareable GTM report from their deals — pipeline health rendered to markdown they can send. Use for 'write a GTM report', 'monthly revenue report', 'share our pipeline results', 'report on the export', 'turn this audit into a report'. Defaults to the SMB segment.

  • gtm-sales-narrative

    When the user wants to build or sharpen a sales narrative or pitch — a story that moves from the buyer's status quo, through the cost of inaction and the shift, to our approach, proof and the ask. Use for 'sales narrative', 'pitch structure', 'story for reps', 'problem to proof', 'why change now'.

  • gtm-segmentation

    When the user wants to define and prioritize market segments. Use for 'segment the market', 'segmentation', 'which segment first', 'prioritize segments', 'split the market into segments'. Sizes each segment only from inputs the user provides and defaults to SMB-first.

  • gtm-strategy

    When the user wants to assemble a whole go-to-market plan or GTM strategy — segment, positioning, funnel math and unit economics in one place. Use for 'build our GTM plan', 'go-to-market strategy', 'GTM plan', 'how do we take this to market', 'assemble the launch plan'. Defaults to the SMB segment.

  • gtm-win-loss

    When the user wants to explain why deals were won or lost — win/loss analysis from closed deals and interview notes. Use for 'win loss analysis', 'why do we lose deals', 'review closed deals', 'win loss interview', 'why did we win'. Interview evidence is user-supplied, never invented.

View source on GitHub doddlehq.com

More from DoddleHQ/DoddleOS

All 21 plugins →

Doddle B2B OS — b2B agency skills for outbound, proposals, cases, retainers, partnerships (DoddleOS v2 blueprints) - 5 skills

16 skills

6

Doddle SaaS OS — saaS marketing skills for homepage, pricing, trial, retention, expansion (DoddleOS v2 blueprints) - 5 skills

14 skills

6

Doddle DevOps OS — Linux server administration: processes, storage, LVM/RAID, boot/systemd, cron/logging, monitoring, packages, networking/SSH, kernel modules, backup (DoddleOS v2 blueprints) - 10 skills

10 skills

6

DoddleOS core — agents, commands, skills, workflows, and training for agentic task execution

10 skills

6

Doddle Travel OS — leisure + corporate travel: search, itineraries, booking, support, reviews (DoddleOS v2 blueprints) - 5 skills

6 skills

6

Similar plugins

Automated code review for pull requests using multiple specialized agents with confidence-based scoring to filter false positives

1 command

anthropics/claude-code 155,476

clay

claudecodex

Work with Clay from Claude Code: set up and sign in to the clay CLI, query and analyze Clay tables, search Clay's GTM database for people and companies, manage audiences, signals, routines and workflows, and draft and review Sequencer campaigns. Includes hooks that auto-approve the plugin's own clay CLI calls and Clay skills; requires a Clay account.

38 skills · hooks

anthropics/claude-plugins-official 47,076

ZoomInfo

claudecodex

Search companies and contacts, enrich leads, find lookalikes, and get AI-ranked contact recommendations. Pre-built skills chain multiple ZoomInfo tools into complete B2B sales workflows.

35 skills · 1 MCP server

anthropics/knowledge-work-plugins 35,601

Per-deal-and-packaging Commercial domain. v2.8.0 ships 8 skills: orchestrator + pricing-strategist (model picker + Van Westendorp WTP + packaging) + deal-desk (deal scorer + discount approval routing + redline) + partnerships-architect (5-tier classifier + joint GTM + revshare modeler) + channel-economics (cost-to-serve + ROI + mix optimizer) + commercial-policy (data-backed discount matrix + exception flow + linter) + rfp-responder (Shipley structured RFP/RFI/RFQ + win-theme + winrate predictor, context: fork) + commercial-forecaster (4Q-weighted bookings + cohort NRR/GRR + funnel-confidence with mandatory assumption disclosure). Hard rules: pricing outputs model+range (never a single number), deal outputs route to named human approver (never auto-approve), forecast outputs surface conversion assumption, RFP never invents claims for GAP requirements. 21 stdlib Python tools, 28+ reference docs. Distinct from business-growth (sales execution), c-level-advisor/cro-advisor (strategic), finance (close+report).

8 skills · 9 commands · 1 agent

alirezarezvani/claude-skills 29,725

Go-to-market skills for PMs: GTM strategy, growth loops, GTM motions, beachhead segments, and ideal customer profiles.

6 skills · 3 commands

phuryn/pm-skills 27,939

fp-check

claude

Systematic false positive verification for security bug analysis with mandatory gate reviews

1 skill · 3 agents · hooks

trailofbits/skills 8,166

Maintain doddle-gtm-skills?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins21 plugins