Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cbrock84/revenue-operations
Runs the mechanics of the revenue engine — lead lifecycle definitions, routing, CRM hygiene, forecasting process, pipeline reporting, and the marketing-to-sales handoff. Use this to fix a broken handoff, define lifecycle stages, improve forecast accuracy, clean up CRM data, design territory or routing rules, or diagnose why pipeline numbers are not trusted.
Passed 19 of 23 test cases with the skill, and 20 of 23 without it.
1 fixed18 passed either way2 still failing2 broke
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
Our sales reps spend hours every week dealing with duplicate lead records and outdated contact data in Salesforce because field validation is disabled. What technical CRM hygiene practices should be automated?
| Checked | Without skill | With skill |
|---|---|---|
| Recommends scheduled duplicate merges in the CRM | Missed | Passed |
| Mandates automated aging of stale records | Passed | Passed |
The instructions your model reads when the skill loads.
Most revenue reporting arguments are definitional. Write down and get agreement on, in one place:
Without these, every number is negotiable and forecasting is a genre of fiction.
Where most revenue leaks. Specify: the exact criteria for passing a lead, the SLA for first contact, what context transfers with it, and the route back when it is rejected — including the reason, recorded.
A rejection loop with no recorded reason means marketing keeps sending the same unqualified leads, and both sides believe the other is the problem.
Scoring exists to route attention, not to produce a number. If sellers do not change what they work on because of the score, it is decoration.
Score on two independent dimensions and keep them separate:
Collapsing the two into one score is the standard mistake: a perfect-fit account with no activity and a poor-fit account browsing aggressively land on the same number and get treated identically, which is wrong in both directions.
test cases passed, vs 20 / 23 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.