Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →sickn33/revops
Design and improve revenue operations, lead lifecycle rules, scoring, routing, handoffs, and CRM process automation.
Passed 15 of 22 test cases with the skill, and 10 of 22 without it.
and 3 more in the full report
5 fixed10 passed either way7 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
Our mid-market B2B SaaS startup is scaling up our sales team and needs a unified revenue process. Please map out a complete RevOps operational blueprint for us. We need detailed documentation that covers our lifecycle stages from initial contact to customer advocate (including criteria and ownership), a formal lead scoring model covering fit and engagement criteria, a lead assignment decision tree with fallback rules, pipeline deal stage requirements with automation triggers, and a tracking dashboard specification for our key funnel metrics.
| Checked | Without skill | With skill |
|---|---|---|
| Includes a pipeline configuration section specifying required fields per stage | Passed | Passed |
| Includes stage automation triggers in the pipeline configuration | Passed | Passed |
| Includes a metrics dashboard specification section with key metrics and target benchmarks | Missed | Passed |
The instructions your model reads when the skill loads.
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-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):
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.
test cases passed, vs 10 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.