← marketplace
marketingconceptsha:591dbd7bf7873f13manual
revops
Use when connecting marketing, sales, CRM, attribution, pipeline, and revenue operations workflows so the agent follows the marketingskills playbook instead of producing generic marketing advice.
source: https://github.com/coreyhaines31/marketingskills/tree/main/skills/revops ↗coreyhaines31/marketingskills· ★ 35k
Install confidence
curl --create-dirs -fsSL https://skillmake.xyz/i/revops -o ~/.claude/skills/revops/SKILL.md
Pinned content
sha:591dbd7bf7873f13
Generated with
manual
Source
github.com
The file served at /api/marketplace/revops-591dbd7b/raw matches this hash. Inspect before install, then copy the command.
3,156 chars · ~789 tokens
--- name: revops description: Use when connecting marketing, sales, CRM, attribution, pipeline, and revenue operations workflows so the agent follows the marketingskills playbook instead of producing generic marketing advice. source: https://github.com/coreyhaines31/marketingskills/tree/main/skills/revops generated: 2026-06-29T18:01:31.974Z category: concept audience: marketing --- ## When to use - The user asks for help connecting marketing, sales, CRM, attribution, pipeline, and revenue operations workflows - A marketing task needs product, audience, positioning, and channel context before execution - The agent should create a repeatable revops workflow instead of a one-off generic answer - The work needs clear success metrics, deliverables, and next steps for a growth or GTM motion ## Key concepts ### 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. ### Core Principles Core part of the revops workflow; use it to keep the agent focused on concrete marketing inputs, decisions, and outputs instead of vague recommendations. ### 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. ### Revenue Team Alignment 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. ## API reference ``` npx skills add coreyhaines31/marketingskills --skill revops ``` Install the revops skill from coreyhaines31/marketingskills. ``` npx skills add coreyhaines31/marketingskills --skill revops ``` ## Gotchas - Read product-marketing context first when present; otherwise the agent may ask repeated setup questions or make weak positioning assumptions. - Do not ship generic best practices without tying recommendations to the product, audience, channel, and conversion goal. - Separate strategy from execution: clarify the campaign decision before drafting assets or implementation steps. - Pick a primary metric before launch so the result can be judged without retrofitting success criteria. - Respect channel mechanics; copy, cadence, and format should change between email, ads, social, SEO, and sales collateral. --- Generated by SkillMake from https://github.com/coreyhaines31/marketingskills/tree/main/skills/revops on 2026-06-29T18:01:31.974Z. Verify against source before relying on details.
File: ~/.claude/skills/revops/SKILL.md