One report, one meaning
The skill opens with a single question. If your head of marketing and your head of sales opened the same CRM report today, would they agree on what it means? If not, it treats the gap as an operations problem, not a marketing or a sales problem.
A lifecycle with five parts
Every stage gets an entry and an exit rule, and every stage gets an owner, including the handoff moments where leads are often lost. Each move between stages is time stamped so you can measure speed. Rejected leads follow a defined path instead of sitting untouched, and a returning contact is recognized as a returning contact, not logged as a brand new lead.
MQL, SQL, and the agreement between them
A marketing qualified lead needs both fit and intent. A sales qualified lead is one a rep has reviewed and accepted after confirming authority, a real problem, a timeline, and a path to budget. The skill puts the handoff in a one page agreement: how fast sales reviews a new lead, what acceptance means, the rejection codes, and who decides on re-engagement.
Scores that fade and routes without gaps
The score has two layers. Fit covers company size, industry, role, and seniority. Behavior covers actions, where a demo request outweighs a blog read. Old scores decay, so a contact from six months ago does not look as warm as one from last week. The skill sets the qualification threshold from the scores of your last 50 closed deals.
Routing maps every lead to exactly one territory and sends contacts at existing accounts to the account owner. It sets overflow rules for absent reps and alerts the rep at once instead of in a daily digest.
Lifecycle rules in the revops file
The lifecycle, the agreement, scoring layers, routing logic, pipeline stages, and automations are documented in the revops skill file on GitHub. It is released under the MIT License, “Copyright (c) 2026 ScayverGraphix.” The skills follow the Agent Skills spec published by vercel-labs/skills.
Stages tied to buyer actions
A pipeline of six to eight stages replaces labels like “In Progress” with moments such as a completed discovery call or a proposal sent. Each stage carries an exit rule and a probability taken from your own win rates, not a guess. The first automations the skill builds are lead alerts, a timer that escalates a missed review, reminders for stalled deals, and a nurture path for closed lost contacts.
Start with three moves.
The skill recommends three first steps. Get written sign off on MQL and SQL definitions from both leaders, add score decay, and share a weekly report on how quickly sales reviews new leads. Ask about lead scoring, routing, or pipeline stages, and it loads. The readme links it with sales-enablement, so add both with npx skills add scayver/marketing-skills --skill revops sales-enablement.
Rules a team understands
Our CRM Automation service maps the event, the data, the owner, and the exception before it configures a workflow. A lead that arrives without the field that decides its owner stays visible to a person instead of landing in the wrong queue.