营销与写作

revops

coreyhaines31/m…ngskills

When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes. Also use when the user mentions 'RevOps,' 'revenue operations,' 'lead scoring,' 'outbound pipeline stages,' 'lead routing,' 'MQL,' 'SQL,' 'pipeline stages,' 'deal desk,' 'CRM automation,' 'marketing-to-sales handoff,' 'data hygiene,' 'leads aren't getting to sales,' 'pipeline management,' 'lead qualification,' or 'when should marketing hand off to sales.' Use this for anything involving the systems and processes that connect marketing to revenue. For cold outreach emails, see cold-email. For email drip campaigns, see emails. For pricing decisions, see pricing.

  • 11.6万 次安装
  • 5.7万 星标
  • 收录于

安装命令

npx skills add https://github.com/coreyhaines31/marketingskills --skill revops

要点

Design and optimize systems connecting marketing, sales, and customer success into a unified revenue engine.

  • Covers lead lifecycle stages (Subscriber → Lead → MQL → SQL → Opportunity → Customer), stage definitions with entry/exit criteria, and ownership accountability across teams
  • Includes lead scoring frameworks combining fit (ICP attributes) and engagement (behavioral signals) with negative scoring to filter unqualified leads
  • Provides lead routing methods (round-robin, territory, account-based, skill-based) with speed-to-lead optimization and SLA enforcement for handoffs
  • Details pipeline stage hygiene, required fields per stage, stale deal detection, and key metrics (conversion rates, velocity, coverage ratio, win rate by source)
  • Covers CRM automation workflows, deal desk approval tiers, data dedup and enrichment strategies, and quarterly audit checklists

SKILL.md

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.

Before Starting

Check for product marketing context first: If .agents/product-marketing.md exists (or .claude/product-marketing.md, or the legacy product-marketing-context.md filename, 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.