tonone
claudeFull company team — 140 agents, 15 teams. All agents and skills in one install.
200 skills · 140 agents · hooks
Revenue team — 9 agents: Bridge, Coach, Deal, Demo, Keep, Quota, Rev, Scout, Surge
Not in a marketplace yet, so it loads for one session with --plugin-dir.
Plugin revenue-team in tonone-ai/tonone. Commands read from the repo's manifest — 2 days ago.
bridge-cosellPlan co-sell and marketplace motions — target partners, listing, joint pipeline. Use when asked to "plan co-sell with AWS", "list us on a marketplace", or "build an alliance motion".
bridge-programDesign the partner program — types, tiers, economics, deal registration. Use when asked to "design a partner program", "set reseller margins", or "build a referral program".
bridge-reconRead-only audit of partnerships — partner roster, sourced pipeline, conflicts, program gaps. Use when asked to "audit our partnerships", "how is our channel performing", or "review our partner program".
coach-battlecardBuild battlecards and talk tracks from win/loss evidence. Use when asked to "write a battlecard", "build a competitor card", or "create talk tracks for objections".
coach-rampDesign the onboarding ramp — 30/60/90 plan, certifications, quota ramp. Use when asked to "build a sales onboarding plan", "design a ramp for new AEs", or "create a 30-60-90 plan".
coach-reconRead-only audit of enablement — ramp time, call quality, content usage, win/loss insight. Use when asked to "audit our sales enablement", "why do new reps ramp slowly", or "review our sales training".
deal-closeClose a specific deal — diagnose why a deal is stalling, answer an objection reply, write a tailored proposal, design the closing sequence, or navigate procurement. Use when a specific deal is stuck, "how do I close this", "write a proposal for this customer", "help me get to yes", or "how do I answ
deal-outreachCold outbound sequence builder — multi-touch email + LinkedIn sequences (5-7 touchpoints) personalized by persona (technical buyer, economic buyer, champion). Use when asked to "write cold emails", "build an outbound sequence", or "write my LinkedIn outreach".
deal-pipelineDesign or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements. Use when asked to "design our pipeline", "audit our CRM stages", "define what qualified means", or "build a sales process".
deal-playbookWrite sales playbooks — outbound sequences, discovery call guides, objection handling scripts, and demo frameworks. Use when asked to "write a sales playbook", "build an outbound sequence", "help me handle objections", or "design a discovery call".
deal-pricingDesign pricing strategy and packaging — tiers, value metrics, enterprise pricing, freemium design, and pricing page copy. Use when asked to "design our pricing", "should we change our price", "how do we package the product", or "what should we charge enterprise".
deal-proposalB2B proposal generator — from deal context (ICP, pain, pricing, timeline) produces a full proposal (exec summary, solution, pricing, timeline, ROI, next steps). Use when asked to "write a proposal", "draft our deck for this deal", "build a proposal for this customer", or "generate a proposal".
deal-qualifyMEDDPICC-based deal qualification worksheet — guide Deal through structured qualification of any opportunity and produce a filled card + recommended next action. Use when asked to "qualify this deal", "run MEDDPICC on this opportunity", "should we pursue this", or "is this deal real".
deal-reconRevenue reconnaissance — audit current sales pipeline, deal patterns, ICP definition, and revenue motion to understand what's working and where the constraint is. Use when asked to "audit our sales", "where is revenue stuck", "what's our pipeline state", "before designing a playbook".
deal-signalsSignal-based prospecting — read target companies' public sites for buying signals (ads, incumbent agency, tech stack, hiring) with evidence URLs, then build a cohort. Use when asked to "find buying signals", "profile these companies", "which accounts should we target", or "build a target list from t
demo-pocRun a POC or pilot — success criteria, timebox, plan, exit decision. Use when asked to "scope a POC", "plan a pilot", or "set POC success criteria".
demo-reconRead-only audit of SE readiness — demo assets, POC history, questionnaire bank, technical win rate. Use when asked to "audit our sales engineering", "how good are our demos", or "review our POC process".
demo-scriptDesign a demo — discovery-driven narrative, flow, environment, failure handling. Use when asked to "design a demo", "prepare for the technical demo", or "write a demo script".
keep-churnChurn risk identification and intervention — scans health signals for at-risk accounts, classifies risk (CRITICAL/HIGH/MEDIUM), and produces an intervention sequence per risk type. Use when asked to "find at-risk accounts", "who might churn", "build a churn prevention plan", or "rescue this account"
keep-expandDesign expansion revenue playbooks — upsell triggers, seat expansion sequences, tier upgrade paths, and cross-sell motions. Use when asked to "grow existing customers", "increase NRR", "design upsell", or "how do we get customers to expand".
keep-healthDesign a customer health scoring model — define signals, weights, thresholds, and action triggers. Use when asked to "build health scoring", "how do we predict churn", "what signals indicate a customer is at risk", or "design our health model".
keep-onboardOptimize customer onboarding — map the activation sequence, identify drop-off points, design the aha moment, and produce the onboarding email sequence. Use when asked to "fix onboarding", "improve activation", "time-to-value is too slow", or "customers aren't getting started".
keep-playbookWrite churn prevention and win-back playbooks — risk intervention sequences, save conversation guides, and win-back email campaigns. Use when asked to "prevent churn", "save at-risk customers", "win back churned customers", or "build a save play".
keep-qbrQuarterly Business Review template generator — takes account info (ARR tier, adoption metrics, goals) and produces a complete QBR deck outline and talking points. Use when asked to "prepare a QBR", "build a quarterly review", "write our QBR agenda", or "create QBR talking points for this account".
keep-reconCustomer success reconnaissance — audit current onboarding completion, health signals, NRR, churn patterns, and CS motion. Use when asked to "audit our customer success", "why are customers churning", "what's our NRR", or before designing any CS playbook.
keep-segmentCustomer segmentation model — tiers customers by ARR, health and expansion potential, defines CS motion per tier, maps resource allocation. Use when asked to "segment our customers", "define our CS tiers", "how should we allocate CS resources", or "who gets high-touch vs. digital".
quota-forecastBuild the forecast — stage weights, commit/best-case/upside, accuracy tracking. Use when asked to "build a sales forecast", "set up forecast categories", or "forecast this quarter".
quota-reconRead-only audit of the CRM and forecast process — data quality, stage integrity, forecast accuracy. Use when asked to "audit our CRM", "why is our forecast off", or "check pipeline hygiene".
quota-territoryDesign territories and quotas — account segmentation, fairness, assignment rules. Use when asked to "design sales territories", "set quotas", or "rebalance territories".
rev-boardWrite the board revenue narrative — bookings, pipeline, forecast, risks, asks. Use when asked to "prep the board revenue update", "write the revenue section of the board deck", or "explain the quarter to the board".
rev-capacityBuild the bookings capacity model — ramped reps, quota, attainment, hiring plan. Use when asked to "build a capacity plan", "how many reps do we need", or "set quotas for next year".
rev-reconRead-only audit of the revenue engine — coverage, capacity, conversion, org gaps. Use when asked to "audit our revenue engine", "why are we missing the number", or "assess our GTM org".
scout-listBuild the target list — ICP scoring, triggers, enrichment, suppression. Use when asked to "build a prospect list", "define our ICP", or "find accounts to target".
scout-reconRead-only audit of the outbound engine — ICP, list quality, sequences, deliverability, handoff. Use when asked to "audit our outbound", "why is our SDR team not booking meetings", or "review our prospecting".
scout-sequenceWrite the outbound sequence — multi-touch cadence, copy, A/B plan, handoff rules. Use when asked to "write an outbound sequence", "draft cold emails", or "build a cadence".
surge-activationUse when asked to improve activation, map the growth funnel, identify growth levers, or design a referral program. Examples: "how do we grow faster", "improve our activation rate", "design a referral program", "what are our best growth levers", "map our growth funnel".
surge-experimentGrowth experiment design — structure a growth hypothesis, define metric, baseline, expected lift, and kill condition for a single experiment. Use when asked to "design a growth experiment", "test this growth idea", "experiment framework", "how do we test if this works", or "growth hypothesis".
surge-landingUse when asked to design growth-optimized landing pages, activation funnel layouts, or experiment-friendly page structures. Examples: "growth-optimized landing", "activation funnel layout", "A/B testable page
surge-plgPLG motion design — free tier, activation sequence, expansion triggers, viral mechanic assessment; makes the calls. Use when asked to "PLG strategy", "freemium model", "product-led growth plan", "self-serve motion", or "upgrade triggers".
surge-reconGrowth state reconnaissance — scan onboarding flows, acquisition channels, funnels, and experiment logs for current growth state. Use when asked to "what's our growth state", "audit the funnel", "what growth experiments have we run", or before designing new growth experiments.
surge-retentionRetention diagnosis and intervention plan — analyze the retention curve, find the primary drop-off, and produce a specific intervention plan with expected impact. Use when asked to "improve retention", "why are users churning", "reduce churn", "win-back campaign", or "users aren't coming back".
bridgePartnerships & Channel — partner program design, reseller/referral/alliance deals, co-sell motions, marketplace listings
coachSales Enablement — onboarding ramps, call coaching, battlecards, talk tracks, win/loss-driven training
dealRevenue & Sales engineer — B2B pipeline, deal strategy, pricing proposals, sales playbooks, and enterprise closing
demoSolutions Engineering — technical discovery, demo design, POCs and pilots, security questionnaires, RFP technical responses
keepCustomer Success engineer — onboarding optimization, health scoring, expansion revenue, churn prevention, and NRR growth
quotaRevenue Operations — forecasting, pipeline hygiene, CRM architecture, territory and quota design, sales-to-finance reconciliation
revChief Revenue Officer — revenue strategy, GTM org design, quota capacity, board revenue narrative, Revenue team orchestration
scoutSales Development — outbound prospecting, ICP and list building, sequences, lead qualification, handoff to AEs
surgeGrowth engineer — acquisition channels, activation funnels, retention playbooks, and PLG strategy
Full company team — 140 agents, 15 teams. All agents and skills in one install.
200 skills · 140 agents · hooks
Install all 27 Engineering Team + Product Team agents at once
173 skills · 27 agents · hooks
Install all 15 Engineering Team agents at once
90 skills · 15 agents · hooks
Engineering team for Claude Code: Apex (engineering lead) plus 14 specialists and 85 skills. The core of tonone, sized for the Anthropic plugin directory.
85 skills · 15 agents
Install all 12 Product Team agents at once
83 skills · 12 agents · hooks
Marketing team — 9 agents: Attrib, Buzz, Drip, Ink, Pitch, Reach, Stack, Stage, Vox
42 skills · 9 agents
Matt Pocock's agent skills for real engineering (grilling, spec/ticket flows, TDD, code review, domain modelling and more).
39 skills
Persistent memory for Claude Code: the next session starts where the last one left off.
29 skills · 1 MCP server · hooks
Cross-session memory and token savings for coding agents.
6 skills · 1 agent · 1 MCP server · hooks
Up-to-date documentation lookup. Pull version-specific documentation and code examples directly from source repositories into your coding agent's context.
1 MCP server
Automates browser interactions for web testing, form filling, screenshots, and data extraction
12 skills
Orchestrate multi-agent teams for parallel code review, hypothesis-driven debugging, and coordinated feature development using Claude Code's Agent Teams
6 skills · 7 commands · 4 agents
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.