Agent skill · Databases

suede-revops

Suede-owned revenue-operations discipline. Use when defining lead scoring and routing, MQL or SQL criteria, pipeline stages, CRM hygiene, automation, deal-desk rules, or marketing-to-sales handoffs. NOT FOR: writing outreach (use suede-cold-email), lifecycle campaigns (use suede-emails), pricing strategy (use suede-pricing), or mutating production CRM records without approval.

JasonColapietrogithub.com/JasonColapietroGitHub ↗
claude-codecodexMIT
Install
npx skills add JasonColapietro/suede-creator-skills --skill suede-revops --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 7
SKILL.md size: 15 KB
Bundled scripts: none
Version: 2.0.0
Path: skills/suede-revops/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 165
Language: JavaScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Suede Revenue Operations Suede RevOps maps the lifecycle rules, data contracts, scoring, routing, and handoffs that connect acquisition, sales, and customer success. It produces implementation-ready operating logic while keeping production CRM mutation behind live-schema review and approval. ## 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. Gather this context (ask if not provided): 1. **GTM motion** — Product-led (PLG), sales-led, or hybrid? 2. **ACV range** — What's the average contract value? 3. **Sales cycle length** — Days from first touch to closed-won? 4. **Current stack** — CRM, marketing automation, scheduling, enrichment tools? 5. **Current state** — How are leads managed today? What's working and what's not? 6. **Goals** — Increase conversion? Reduce speed-to-lead? Fix handoff leaks? Build from scratch? Work with whatever the user gives you. If they have a clear problem area, start t

What's inside
Steps it walks through
  1. Before Starting
  2. Core Principles
  3. Single Source of Truth
  4. Define Before Automate
  5. Measure Every Handoff
  6. Revenue Team Alignment
  7. Lead Lifecycle Framework
  8. Stage Definitions
  9. MQL Definition
  10. MQL-to-SQL Handoff SLA
  11. Lead Scoring
  12. Scoring Dimensions
  13. Building a Scoring Model
  14. Common Scoring Mistakes
Ships with 6 files
  • agents/openai.yaml
  • evals/evals.json
  • references/automation-playbooks.md
  • references/lifecycle-definitions.md
  • references/routing-rules.md
  • references/scoring-models.md
More from suede-creator-skills
All skills →
About this skill
What does the suede-revops skill do?

Suede-owned revenue-operations discipline. Use when defining lead scoring and routing, MQL or SQL criteria, pipeline stages, CRM hygiene, automation, deal-desk rules, or marketing-to-sales handoffs. NOT FOR: writing outreach (use suede-cold-email), lifecycle campaigns (use suede-emails), pricing strategy (use suede-pricing), or mutating production CRM records without approval.

How do I install it?

Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-revops --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From JasonColapietro/suede-creator-skills, a repository with 165 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going