Reusable SKILL.md capabilities that give your agent new expertise — installed into .claude/skills/ and friends.
Build and advance a RevOps or Sales Ops career from the candidate's side - place the candidate on the ladder by scope rather than title, close competency gaps, build defensible evidence of structurally invisible work, and prepare the four exercises RevOps interview loops actually run. Produces a career plan with a gap roadmap, an evidence ledger, interview readiness, and a compensation ask. Use whenever the user mentions a RevOps career, a sales ops career path, RevOps interview prep, RevOps certifications,
Trace where deals and revenue silently exit one specific funnel and size the loss in recoverable (never gross) dollars - untracked steps, unworked leads, manual handoffs, mid-funnel stalls, paper-process drops, billing and renewal misses - separating real leaks from healthy disqualification and data-capture gaps. Use whenever the user mentions revenue leakage, funnel drop-off, a leaky funnel, deals disappearing, unworked leads, handoff gaps, "where are we losing deals", or "why did pipeline vanish" - even i
Design the org-wide revenue KPI framework at the macro level - which metrics matter at each org level from board to IC, how they roll up through a reconciling metric tree with explicit math, who owns each branch, which guardrail counter-metrics ride alongside each owned number, and how the set is gated by company stage and business model. Use whenever the user mentions a revenue KPI framework, a metric hierarchy, a KPI tree, a North Star metric, driver metrics, guardrail counter-metrics, NRR, or which reven
Skill for converting an installed Firebase Extension (or extension source) into a standalone Cloud Functions for Firebase codebase or publishable npm package, including V1 to V2 trigger upgrades, lifecycle hooks, and declarative security
Design a company's revenue funnel model from scratch, at the macro level - the stage set, the unit of analysis (lead, buying group, account), the model purpose (process vs planning vs forecast), the cohort-based conversion assumptions behind the plan, and the ownership handoffs between marketing, sales, and CS. Use whenever the user mentions funnel design, funnel stages, a funnel model, conversion rate assumptions, a bowtie model, a demand waterfall, MQL to SQL to opportunity definitions, or marketing-sales
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, dea
Search the web with LLM-optimized results via the Tavily CLI. Use this skill when the user wants to search the web, find articles, look up information, get recent news, discover sources, or says "search for", "find me", "look up", "what's the latest on", "find articles about", or needs current information from the internet. Returns relevant results with content snippets, relevance scores, and metadata — optimized for LLM consumption. Supports domain filtering, time ranges, and multiple search depths.
Audit existing sales pipeline stage definitions against buyer-verifiable milestones and flag the ones built on rep activity instead. Core test - does each stage exit criterion name something the buyer did, said, or agreed to, checkable by two managers independently? Adds stage aging, conversion decay, stage-skip rate, and close-date push diagnostics. Use whenever the user mentions stage definitions, stage exit criteria, stage inflation, stages named after rep activity ("demo scheduled", "proposal sent"), "o
Set org-wide revenue data governance policy - which system is source of truth per object class (account, contact, opportunity, subscription, usage event, revenue metrics), how cross-team data contracts bind producers to consumers, where revenue metric definitions live, and who arbitrates disputes. Produces a per-object SOR/SOT designation table, an identity-resolution spine, a data-contract register, and a federated ownership model. Use whenever the user mentions source of truth, "two ARR numbers", GTM data
Build a personalised, time-budgeted watch list of RevOps / Sales Ops information sources - revops podcasts, revops newsletters, revops communities, industry events, and revops people to follow - every source verified still active, with a periodic refresh routine that keeps the list fresh. Use whenever the user mentions a revops radar, staying current in revenue operations, which revops newsletters or podcasts to subscribe to, which revops communities or conferences deserve their time, or who to follow in th
Build the complete hiring packet for a RevOps or Sales Ops role - archetype and level decision, outcome scorecard, interview stage map with a competency question bank and anchored rating scales, a work-sample exercise with rubric and debrief, and a 30-60-90 ramp plan branched on seniority and archetype. For the hiring manager or founder recruiting the hire. Use whenever the user mentions hiring a RevOps manager, sales ops interview questions, a RevOps take-home exercise, a scorecard for a first ops hire, or
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 clos
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. A
Run a macro, periodic review of the full RevOps/GTM tool stack against the revenue workflows it serves and decide, tool by tool, what to keep, consolidate, replace, or cut - four-channel inventory, function-level overlap map, TIME scoring, a renewal-triggered action calendar, and re-sprawl governance. Use whenever the user mentions stack rationalization, GTM tool consolidation, a revops stack audit, a GTM stack review, SaaS sprawl, too many sales and marketing tools, cutting tooling spend, redundant GTM too
Define the metric set and narrative structure for an executive or board revenue report so it tells one coherent story - a small stable metric spine, locked definitions, an answer-first narrative around plan vs actual vs forecast, presenting a miss without surprising the board, the reconciliation and sign-off chain, and weekly vs monthly vs quarterly cadences. Use whenever the user mentions a board revenue report, exec deck metrics, the QBR revenue section, a monthly revenue review, an investor update, or a
Design and operate CRM field-level governance - who owns each CRM field, which system is authoritative for it, how often it must be refreshed, and how the rules are enforced. Produces a field dictionary, per-field ownership, a system-of-record map with write-precedence and conflict rules, freshness SLAs, an enforcement plan, a field lifecycle, and a governance cadence. Use whenever the user mentions field ownership, single source of truth, system of record per field, data dictionary, stale CRM data, custom
Quality review of a change: is the logic right, is it safe, does it hold under real load, is risky code tested, is it fast enough, and is every line needed. Reads the connected code, not only the diff. Each finding is explained in plain English. Use for "review this", "code review", "review the last commit", "review my PR", "is this over-engineered", /ponytail-review.
Design, validate, and recalibrate a lead scoring model - fit and engagement signals, weighting, negative scoring and exclusions, decay, MQL/PQL threshold and tier setting, backtesting against closed-won/closed-lost outcomes, and governance; also diagnoses an existing broken model. Use whenever the user mentions lead scoring, an MQL threshold, fit vs engagement scoring, product-qualified leads, score decay, "score my leads", "our lead scores are wrong", "sales rejects our MQLs", or "too many junk MQLs" - eve
Design the deal desk approval chain and exception-handling process for non-standard B2B SaaS deals - a tiered discount approval matrix and delegation of authority across five concession levers (price, payment terms, services, contract risk, security), margin floor policy, exception intake, two SLA clocks with a sales escalation path, and precedent control. Includes the rules-driven promo/discount-policy equivalent for PLG, self-serve, and B2C. Use whenever the user mentions deal desk, discount approval, quo