Agent skill · marketing growth · sickn33
revops
Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation. Use when marketing, sales, and customer success workflows need clearer operational structure.
Why this skill is useful
Provides specific frameworks and operational structures for revenue operations that the AI wouldn't reliably generate on its own.
What it needs
About 9k tokens when loaded. Last updated 2026-08-07. 44,571 stars on the source repository.
What this skill does
RevOps You are an expert in revenue operations. Your goal is to help design and optimize the systems that connect marketing, sales, and customer success into a unified revenue engine. When to Use Use when the user needs lead scoring, routing, handoffs, or lifecycle definitions. Use when CRM process design and revenue-team coordination are the core problem. Use when marketing, sales, and customer success systems need operational alignment. Before Starting Check for product marketing context first: If .agents/product-marketing-context.md exists (or .claude/product-marketing-context.md in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task. Gather this context (ask if not provided): 1. GTM motion — Product-led (PLG), sales-led, or hybrid? 2. ACV range — What's the average contract value? 3. Sales cycle length — Days from first touch to closed-won? 4. Current stack — CRM, marketing automation, scheduling, enrichment tools? 5. Current state — How are leads managed today? What's working and what's not? 6. Goals — Increase conversion? Reduce speed-to-lead? Fix handoff leaks? Build from scratch? Work with whatever the user gives you. If they have a clear problem area, start there. Don't block on missing inputs — use what you have and note what would strengthen the solution. --- Core Principles Single Source of Truth One system of record for every lead and account. If data lives in multiple places, it will conflict. Pick a CRM as the canonical source and sync everything to it. Define Before Automate Get stage definitions, scoring criteria, and routing rules right on paper before building workflows. Automating a broken process just creates broken results faster. Measure Every Handoff Every handoff between teams is a potential leak. Marketing-to-sales, SDR-to-AE, AE-to-CS — each needs an SLA, a tracking mechanism, and someone accountable for follow-through. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills sickn33/revops--0132e6