Loading...
Loading...
Found 18 Skills
When the user wants to create detailed production schedules, develop MPS, manage production planning, or translate S&OP to execution. Also use when the user mentions "MPS," "production plan," "available-to-promise," "master schedule," "rough-cut capacity planning," "time-phased planning," "planned orders," or "MRP input." For shop floor scheduling, see production-scheduling. For aggregate planning, see sales-operations-planning.
Designs how sales quotas are derived for a team or company - top-down vs bottom-up reconciliation, ramp-adjusted capacity modeling (Ramped Rep Equivalents), over-assignment cushion, territory-weighted fair-share allocation, ramp relief policy, and validation against current attainment benchmarks. A macro planning exercise for VP Sales, CRO, and sales ops, covering B2B and B2C. Use whenever the user mentions quotas, targets, attainment, ramping new hires, annual planning, or "how much quota should an AE carry", even without the word quota. Do NOT use for pipeline coverage math (mbfinotti/sales-skills@sales-pipeline-coverage-modeling) or the comp plan that pays against it (mbfinotti/sales-skills@sales-comp-design).
Diagnose why an existing sales forecast is unreliable and recommend fixes - stage inflation and happy ears, sandbagging, deals without verifiable buyer evidence, stale or mass-pushed close dates, wrong forecast-category assignment, zombie and duplicate opportunities, late-created deals, manager roll-up overrides, and comp incentives that reward bias - separating data-quality from behavioral from genuine demand problems. Use whenever the user mentions forecast accuracy, a forecast miss, reps sandbagging, deals that keep slipping, "why did we miss the number", or "our commit is never right" - even if they never say "forecast". Covers B2B deal-based and B2C/high-volume. Do NOT use for pipeline coverage modeling - use mbfinotti/sales-skills@sales-pipeline-coverage-modeling instead.
Before starting any RevOps or Sales Ops task, and at the start of every session on an ongoing RevOps project, run this first - it routes the task to exactly one skill of the revops-skills collection or says plainly that none fits, and bootstraps or resumes the project's shared, versioned context artifact so the next session starts warm instead of cold, ending in a short-list plus an ordered skill chain. Run it even when the collection's other skills are already used daily - a new project is a new context. Also use whenever the user mentions a revops kickoff, a new RevOps project, a revops project start, revops or crm skill routing, a periodic RevOps check-in, a recurring RevOps review, "which revops skill do I need", or "where do I start with RevOps" - even if they never name a skill, and even if the request looks like it already belongs to one specific skill. Do NOT use for routing quota-carrying sales tasks - use mbfinotti/sales-skills@sales-kickoff instead.
Run a periodic, checklist-based hygiene audit over an active pipeline snapshot - stale deals (no stage, close date, or amount change, not logged touches) flagged against segment-specific stage medians, close-date push-count anomalies, and missing forecast-critical fields - producing an exception list with a disposition per flagged deal, a remediation plan, and a pass threshold. Use whenever the user mentions pipeline hygiene, a stale deal audit, pipeline cleanup before a QBR, deals that keep pushing, a close date that keeps slipping, missing fields on deals, or "our pipeline is full of junk" - even if they never say "hygiene". Covers B2B and B2C/high-velocity/PLG. Do NOT use for rewriting stage definitions - use mbfinotti/revops-skills@pipeline-stage-definition-audit instead.
Build and validate revenue forecasts with pipeline coverage and gap analysis. Use when forecasting revenue, validating a commit, analyzing pipeline coverage, preparing for a forecast call, doing gap analysis, calculating weighted pipeline, or reviewing deal confidence levels. Do NOT use for individual deal analysis (use /sales-deal-inspect), portfolio pipeline management (use /sales-pipeline), or building outbound cadences (use /sales-cadence).
Account assignment by revenue potential, geography, relationship. Workload balancing, TAM/SAM calculation, coverage models.
4 production-ready business and growth skills: customer success manager with health scoring and churn prediction, sales engineer with RFP analysis, revenue operations with pipeline and GTM metrics, and contract & proposal writer. Python tools included (all stdlib-only). Works with Claude Code, Codex CLI, and OpenClaw.
Nutshell integration. Manage Leads, Persons, Organizations, Deals, Projects, Activities and more. Use when the user wants to interact with Nutshell data.
Weighted pipeline forecast by probability. Historical accuracy tracking, commit vs best-case scenarios, deal slippage patterns.
Strategic sales leadership guidance for B2B SaaS and enterprise software companies. Covers sales strategy, team building, pipeline management, enterprise selling, discovery calls, demos, proposals, negotiations, and sales operations. Use when building sales teams, designing sales processes, improving win rates, or scaling revenue operations. Use for "sales strategy", "sales process", "pipeline review", "deal strategy", "sales hiring", "quota planning".
Revenue operations analyst specializing in pipeline health diagnostics, deal velocity analysis, forecast accuracy, and data-driven sales coaching. Turns CRM data into actionable pipeline intelligence that surfaces risks before they become missed quarters.