- name
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,' 'o
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add coreyhaines31/marketingskills --skill revops -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add coreyhaines31/marketingskills --skill revops -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add coreyhaines31/marketingskills --skill revops -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add coreyhaines31/marketingskills --skill revops -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/coreyhaines31/marketingskills/tree/HEAD/skills/revopsFrom the publisher
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.
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):
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.
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.
Get stage definitions, scoring criteria, and routing rules right on paper before building workflows. Automating a broken process just creates broken results faster.
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.
Marketing, sales, and customer success must agree on definitions. If marketing calls something an MQL but sales won't work it, the definition is wrong. Alignment meetings aren't optional.
Outbound contacts follow their own stages (targeted → in sequence → replied → positive → meeting booked → meeting held → opportunity), with fields for signal, tier, sequence, and channel so meetings can be attributed. See references/lifecycle-definitions.md.
An MQL requires both fit and engagement:
Neither alone is sufficient. A perfect-fit company that never engages isn't an MQL. A student downloading every ebook isn't an MQL.
Define response times and document them:
For complete lifecycle stage templates and SLA examples: See references/lifecycle-definitions.md
Explicit scoring (fit) — Who they are:
Implicit scoring (engagement) — What they do:
Negative scoring — Disqualifying signals:
For detailed scoring templates and example models: See references/scoring-models.md
Response time is the single biggest factor in lead conversion:
Build routing rules that prioritize speed. Alert reps immediately. Escalate if SLA is missed.
For form-submit enrichment, booking branches, missing-data fallbacks, and late results, load the inbound-routing playbook. Use it alongside the ownership and territory rules below.
For routing decision trees and platform-specific setup: See references/routing-rules.md
For platform-specific workflow recipes: See references/automation-playbooks.md
Document every exception. Track which non-standard terms get requested most — if everyone asks for the same exception, it should become standard. Review quarterly.
Build three views:
When delivering RevOps recommendations, provide:
Format each as a standalone document the user can implement directly. Include platform-specific guidance when the CRM is known.
For implementation, see the tools registry. Key RevOps tools:
© 2026 Skills Rack.
---name: revopsdescription: When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff…---# skills/revops/SKILL.mdOverview
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.
FAQ
Download skills/revops/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/coreyhaines31/marketingskills.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.