Revops
AvdLee/RocketSimApp
When the user wants help with revenue operations, lead lifecycle management, or marketing-to-sales handoff processes.
Suede-owned revenue-operations discipline. An agent skill from JasonColapietro/suede-creator-skills.
Install Suede Revops
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-revops -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-revops --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/suede-revops .claude/skills/suede-revops && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "suede-revops" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-revops into .claude/skills/suede-revops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-revops", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-revopsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-revops -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-revops --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/suede-revops .agents/skills/suede-revops && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "suede-revops" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-revops into .agents/skills/suede-revops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-revops", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-revops -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-revops --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/suede-revops .cursor/skills/suede-revops && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "suede-revops" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-revops into .cursor/skills/suede-revops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-revops", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/JasonColapietro/suede-creator-skills.git --path skills/suede-revops--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-revops -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-revops --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/suede-revops .gemini/skills/suede-revops && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "suede-revops" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-revops into .gemini/skills/suede-revops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-revops", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install JasonColapietro/suede-creator-skills suede-revopsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-revops -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/suede-revops .github/skills/suede-revops && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "suede-revops" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-revops into .github/skills/suede-revops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-revops", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add JasonColapietro/suede-creator-skills --skill suede-revops -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install JasonColapietro/suede-creator-skills suede-revops --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/JasonColapietro/suede-creator-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/suede-revops .opencode/skills/suede-revops && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "suede-revops" agent skill from https://github.com/JasonColapietro/suede-creator-skills/tree/main/skills/suede-revops into .opencode/skills/suede-revops/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "suede-revops", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
suede-revops- GitHub stars
- 127
- Token cost
- ~3.8k tokens
- SKILL.md length
- 1,825 words
- Files
- 8 (incl. references)
- Skills in repo
- 78
- Repo updated
- First seen
- Licence
- MIT
At a glance
Suede-owned revenue-operations discipline. An agent skill from JasonColapietro/suede-creator-skills.
- Works in 6 steps: GTM motion: Product-led (PLG),… → ACV range: What's the average contract… → Sales cycle length: Days from first… → …
- Defining lead scoring and routing
- SKILL.md covers Before Starting, Core Principles, Lead Lifecycle Framework and Lead Scoring, plus 5 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Suede Revops is an agent skill from JasonColapietro/suede-creator-skills. 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.
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 10 other files, including reference files (for example `CARD.md`, `agents/openai.yaml` and `evals/evals.json`).
It sits in Sales & Support, covering Lead generation, Cold outreach and Pricing strategy. It works with SQL. The repository describes itself as: Open-source AI skills for SEO, AI search visibility, conversion copy, marketing strategy, and business operations. Reusable workflows for Claude Code and Codex, plus code review… The licence is MIT.
When your agent uses it
- Defining lead scoring and routing
- Pipeline stages
- Deal-desk rules
- Marketing-to-sales handoffs
Example prompts
- “/suede-revops”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- GTM motion: Product-led (PLG), sales-led, or hybrid?
- ACV range: What's the average contract value?
- Sales cycle length: Days from first touch to closed-won?
- Current stack: CRM, marketing automation, scheduling, enrichment tools?
- Current state: How are leads managed today? What's working and what's not?
- Goals: Increase conversion? Reduce speed-to-lead? Fix handoff leaks? Build from scratch?
What it can do on your machine
Read from SKILL.md and the folder at commit e5f94d7. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Suede Revops loads about 3.8k tokens when it runs, and up to ~12k if it reads all its reference files. Until then it costs about 98 tokens; SKILL.md has 1,825 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from JasonColapietro/suede-creator-skills at commit e5f94d7, republished under its MIT licence (© JasonColapietro). 1,825 words, ~3,769 tokens.
Download SKILL.mdSave it as
.claude/skills/suede-revops/SKILL.md (or your agent's skills folder). This skill also uses 7 other files; get the full folder from GitHub.- name
- suede-revops
- description
- 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.
- metadata.version
- 2.0.0
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):
- GTM motion: Product-led (PLG), sales-led, or hybrid?
- ACV range: What's the average contract value?
- Sales cycle length: Days from first touch to closed-won?
- Current stack: CRM, marketing automation, scheduling, enrichment tools?
- Current state: How are leads managed today? What's working and what's not?
- 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 there. Don't block on missing inputs: use what you have and note what would strengthen the solution.
Core Principles
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.
Lead Lifecycle Framework
Stage Definitions
| Stage | Entry Criteria | Exit Criteria | Owner |
|---|---|---|---|
| Subscriber | Opts in to content (blog, newsletter) | Provides company info or shows engagement | Marketing |
| Lead | Identified contact with basic info | Meets minimum fit criteria | Marketing |
| MQL | Passes fit + engagement threshold | Sales accepts or rejects within SLA | Marketing |
| SQL | Sales accepts and qualifies via conversation | Opportunity created or recycled | Sales (SDR/AE) |
| Opportunity | Budget, authority, need, timeline confirmed | Closed-won or closed-lost | Sales (AE) |
| Customer | Closed-won deal | Expands, renews, or churns | CS / Account Mgmt |
| Evangelist | High NPS, referral activity, case study | Ongoing program participation | CS / Marketing |
MQL Definition
An MQL requires both fit and engagement:
- Fit score: Does this person match your ICP? (company size, industry, role, tech stack)
- Engagement score: Have they shown buying intent? (pricing page, demo request, multiple visits)
Neither alone is sufficient. A perfect-fit company that never engages isn't an MQL. A student downloading every ebook isn't an MQL.
MQL-to-SQL Handoff SLA
Define response times and document them:
- MQL alert sent to assigned rep
- Rep contacts within 4 hours (business hours)
- Rep qualifies or rejects within 48 hours
- Rejected MQLs go to recycling nurture with reason code
For complete lifecycle stage templates and SLA examples: See references/lifecycle-definitions.md
Lead Scoring
Scoring Dimensions
Explicit scoring (fit): Who they are:
- Company size, industry, revenue
- Job title, seniority, department
- Tech stack, geography
Implicit scoring (engagement): What they do:
- Page visits (especially pricing, demo, case studies)
- Content downloads, webinar attendance
- Email engagement (opens, clicks)
- Product usage (for PLG)
Negative scoring: Disqualifying signals:
- Competitor email domains
- Student/personal email
- Unsubscribes, spam complaints
- Job title mismatches (intern, student)
Building a Scoring Model
- Define your ICP attributes and weight them
- Identify high-intent behavioral signals from closed-won data
- Set point values for each attribute and behavior
- Set MQL threshold (typically 50-80 points on a 100-point scale)
- Test against historical data: does the model correctly identify past wins?
- Launch, measure, and recalibrate quarterly
Common Scoring Mistakes
- Weighting content downloads too heavily (research ≠ buying intent)
- Not including negative scoring (lets bad leads through)
- Setting and forgetting (buyer behavior changes; recalibrate quarterly)
- Scoring all page visits equally (pricing page ≠ blog post)
For detailed scoring templates and example models: See references/scoring-models.md
Lead Routing
Routing Methods
| Method | How It Works | Best For |
|---|---|---|
| Round-robin | Distribute evenly across reps | Equal territories, similar deal sizes |
| Territory-based | Assign by geography, vertical, or segment | Regional teams, industry specialists |
| Account-based | Named accounts go to named reps | ABM motions, strategic accounts |
| Skill-based | Route by deal complexity, product line, or language | Diverse product lines, global teams |
Routing Rules Essentials
- Route to the most specific match first, then fall back to general
- Include a fallback owner: unassigned leads go cold fast and waste pipeline
- Round-robin should account for rep capacity and availability (PTO, quota attainment)
- Log every routing decision for audit and optimization
Speed-to-Lead
Response time is one of the largest controllable factors in lead conversion. Widely cited vendor studies (Lead Connect, InsideSales) report order-of-magnitude differences; treat the ordering as reliable and the multipliers as unverified until measured on your own data:
- Contact within 5 minutes: the target; qualification rates fall steeply after it
- After 30 minutes, conversion drops sharply
- After 24 hours, the lead is effectively cold
Build routing rules that prioritize speed. Alert reps immediately. Escalate if SLA is missed.
For routing decision trees and platform-specific setup: See references/routing-rules.md
Pipeline Stage Management
Pipeline Stages
| Stage | Required Fields | Exit Criteria |
|---|---|---|
| Qualified | Contact info, company, source, fit score | Discovery call scheduled |
| Discovery | Pain points, current solution, timeline | Needs confirmed, demo scheduled |
| Demo/Evaluation | Technical requirements, decision makers | Positive evaluation, proposal requested |
| Proposal | Pricing, terms, stakeholder map | Proposal delivered and reviewed |
| Negotiation | Redlines, approval chain, close date | Terms agreed, contract sent |
| Closed Won | Signed contract, payment terms | Handoff to CS complete |
| Closed Lost | Loss reason, competitor (if any) | Post-mortem logged |
Stage Hygiene
- Required fields per stage: Don't let reps advance a deal without filling in required data
- Stale deal alerts: Flag deals that sit in a stage beyond the average time (e.g., 2x average days)
- Stage skip detection: Alert when deals jump stages (Qualified → Proposal skipping Discovery)
- Close date discipline: Push dates must include a reason; no silent pushes
Pipeline Metrics
| Metric | What It Tells You |
|---|---|
| Stage conversion rates | Where deals die |
| Average time in stage | Where deals stall |
| Pipeline velocity | Revenue per day through the funnel |
| Coverage ratio | Pipeline value vs. quota (target 3-4x) |
| Win rate by source | Which channels produce real revenue |
Show full SKILL.md (792 more words)Show less
CRM Automation Workflows
Platform-agnostic build list: the set to design before the stack is decided, in build order:
- MQL alert + assignment: instant rep notification with lead context
- SLA escalation: notify the manager when response time is missed
- Score-driven stage promotion: advance lifecycle stage when criteria are met
- Meeting booked / no-show: notify the AE; auto-follow-up on a miss
- Closed-won handoff: create the CS task and update the forecast
- Stale deal alert: flag a deal past 2x average days in stage
- Recycled-lead nurture: return disqualified leads to marketing with a reason code
- Activity digest + re-engagement: daily high-intent summary; alert on a dormant lead's return
For the trigger and action definitions per platform: HubSpot workflows, Salesforce Flow equivalents, Calendly/SavvyCal, and Zapier patterns, including round-robin, routing by criteria, and pre-meeting enrichment: See references/automation-playbooks.md. Read it once the CRM is known; build from the list above when it is not.
Deal Desk Processes
When You Need a Deal Desk
- ACV above $25K (or your threshold for non-standard deals)
- Non-standard payment terms (net-90, quarterly billing)
- Multi-year contracts with custom pricing
- Volume discounts beyond published tiers
- Custom legal terms or SLAs
Approval Workflow Tiers
| Deal Size | Approval Required |
|---|---|
| Standard pricing | Auto-approved |
| 10-20% discount | Sales manager |
| 20-40% discount | VP Sales |
| 40%+ discount or custom terms | Deal desk review |
| Multi-year / enterprise | Finance + Legal |
Non-Standard Terms Handling
Document every exception. Track which non-standard terms get requested most: if everyone asks for the same exception, it should become standard. Review quarterly.
Data Hygiene & Enrichment
Dedup Strategy
- Matching rules: Email domain + company name + phone as primary match keys
- Merge priority: CRM record wins over marketing automation; most recent activity wins for fields
- Scheduled dedup: Run weekly automated dedup with manual review for edge cases
Required Fields Enforcement
- Enforce required fields at each lifecycle stage
- Block stage advancement if fields are empty
- Use progressive profiling: don't require everything upfront
Enrichment vendors are listed under Tool Integrations below, with the provenance, freshness, lawful-basis, and credit-cost checks that apply before proposing any of them.
Quarterly Audit Checklist
- Review and merge duplicates
- Validate email deliverability on stale contacts
- Archive contacts with no activity in 12+ months
- Audit lifecycle stage distribution (look for bottlenecks)
- Verify enrichment data accuracy on a sample set
RevOps Metrics Dashboard
Key Metrics
| Metric | Formula / Definition | Benchmark |
|---|---|---|
| Lead-to-MQL rate | MQLs / Total leads | 5-15% |
| MQL-to-SQL rate | SQLs / MQLs | 30-50% |
| SQL-to-Opportunity | Opportunities / SQLs | 50-70% |
| Pipeline velocity | (# deals x avg deal size x win rate) / avg sales cycle | Varies by ACV |
| CAC | Total sales + marketing spend / new customers | LTV:CAC > 3:1 |
| LTV:CAC ratio | Customer lifetime value / CAC | 3:1 to 5:1 healthy |
| Speed-to-lead | Time from form fill to first rep contact | < 5 minutes ideal |
| Win rate | Closed-won / total opportunities | 20-30% (varies) |
Dashboard Structure
Build three views:
- Marketing view: Lead volume, MQL rate, source attribution, cost per MQL
- Sales view: Pipeline value, stage conversion, velocity, forecast accuracy
- Executive view: CAC, LTV:CAC, revenue vs. target, pipeline coverage
Output Format
When delivering RevOps recommendations, provide:
- Lifecycle stage document: Use the stage template shape in references/lifecycle-definitions.md for each stage: Entry criteria / Exit criteria / Owner / Actions on entry / SLA / Required fields / Recycle path. Do not invent a different shape.
- Scoring specification: Fit and engagement attributes with point values and MQL threshold
- Routing rules document: Decision tree with assignment logic and fallbacks
- Pipeline configuration: Stage definitions, required fields, and automation triggers
- Metrics dashboard spec: Key metrics, data sources, and target benchmarks
Format each as a standalone document the user can implement directly. Include platform-specific guidance when the CRM is known.
Tool Integrations
These are evaluation examples, not guaranteed integrations. Verify the live schema, authenticated account, permissions, API limits, pricing, and vendor documentation before proposing implementation.
| Tool Category | Examples | Verify Before Use |
|---|---|---|
| CRM | HubSpot, Salesforce | Objects, fields, ownership, automation, permissions |
| Scheduling | Calendly, SavvyCal | Routing logic, availability, privacy |
| Enrichment | Clearbit, Apollo | Provenance, freshness, lawful basis, credit cost |
| Automation | ActiveCampaign, Zapier | Trigger scope, retries, rollback, secrets |
| Partner operations | Introw, Crossbeam | Account matching, deal rules, commissions |
Boundaries
- Do not change production CRM fields, routing, automations, permissions, SLAs, ownership, or records without reading the live schema, previewing the exact effect, and receiving explicit approval.
- Do not delete, merge, deduplicate, enrich, or reassign records as a planning step, and do not expose personal data in reports.
- Do not redefine lifecycle stages or claim pipeline impact from modeled data; document assumptions and the stakeholders who must approve the operating rule.
Routing
- Use
suede-prospectingto build and qualify the source list. - Use
suede-cold-emailfor approved outbound sequence copy. - Use
suede-sales-enablementfor collateral and rep-facing materials. - Use
suede-analyticsfor pipeline measurement and attribution. - Use
suede-pricingwhen deal-desk work turns into a pricing decision: discount tiers that keep getting overridden, a non-standard term everyone requests, or list-price and packaging changes.
© JasonColapietro, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 7 other files (references) in skills/suede-revops of JasonColapietro/suede-creator-skills.
- SKILL.md
- CARD.md
- agents/openai.yaml
- evals/evals.json
- references/automation-playbooks.md
- references/lifecycle-definitions.md
- references/routing-rules.md
- references/scoring-models.md
Open the folder on GitHubat commit e5f94d7
Compare with similar skills
Suede Revops next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Suede Revops this skillJasonColapietro/suede-creator-skills | 127 | — | ~3.8k | Automated safety check: Pass | MIT | |
| RevopsAvdLee/RocketSimApp | 805 | 6 repos | ~3.7k | Automated safety check: Pass | Custom licence | |
| B2B Lead Generationminhnv0807/ai-business-skills | 609 | — | ~1.2k | Automated safety check: Pass | MIT | |
| Sf Datacloud RetrieveJaganpro/sf-skills | 424 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Cold Outreachericrisco/rsc-harness | 180 | — | ~4.1k | Automated safety check: Pass | MIT | |
| Lead Genericrisco/rsc-harness | 180 | — | ~2.6k | Automated safety check: Pass | MIT |
Similar skills
B2B Lead Generation
minhnv0807/ai-business-skills
Plans B2B pipeline work from ICP definition and prospecting through lead scoring, outbound sequences, sales assets and MQL to SQL handoff, aiming at qualified pipeline.
Sf Datacloud Retrieve
Jaganpro/sf-skills
Salesforce Data Cloud Retrieve phase. An agent skill from Jaganpro/sf-skills.
Cold Outreach
ericrisco/rsc-harness
A skill your agent uses when writing a cold email or LinkedIn DM to a stranger and its cadence: first-touch copy under a word ceiling, 4-7 step bump sequences, per-inbox volume and warm-up limits…
Lead Gen
ericrisco/rsc-harness
A skill your agent uses when building and qualifying a prospect list before anyone reaches out — a falsifiable ICP, named accounts/contacts from Apollo/ZoomInfo/Clay, deduped against the CRM, tiered…
Sales Pipeline
ericrisco/rsc-harness
A skill your agent uses when an operator runs deals out of a spreadsheet or Notion and wants real stages, win probabilities, deal hygiene, a weekly follow-up sweep, and a defensible roll-up forecast…
More from JasonColapietro/suede-creator-skills
All 78 skills in this repoSuede Release Linter
JasonColapietro/suede-creator-skills
Lints a local music or media release folder and scores its readiness, flagging missing files, weak metadata, artwork and stem problems, split gaps and rights blockers.
Creator Rights Passport
JasonColapietro/suede-creator-skills
Turns messy creator materials into an offline rights-and-provenance transfer package: hashed asset inventory, intake manifest, credits, license notes and a missing-information report.
Suede Clip to Guide
JasonColapietro/suede-creator-skills
Turns a video clip, interview moment or transcript into a package that bridges viewers to a long-form guide, with rights, claim and approval gates along the way.
Suede MCP Release QA
JasonColapietro/suede-creator-skills
Checks a Suede AI MCP server release against a live process: the full JSON-RPC lifecycle, schemas, annotations, malformed input, catalog agreement and install docs.
Android App Factory
JasonColapietro/suede-creator-skills
Takes a native Android app from product idea to Google Play release, covering Compose architecture, policy checks, privacy, billing, testing, signing and rollout.
Suede Ad Creative
JasonColapietro/suede-creator-skills
Suede-owned paid-media creative system for hooks, headlines, primary text, static and motion concepts, platform specs, review pages, and test-ready variant batches.
Related
Works with
Categories
Questions about Suede Revops
What does Suede Revops do?
Suede-owned revenue-operations discipline. An agent skill from JasonColapietro/suede-creator-skills. Suede Revops is an agent skill from JasonColapietro/suede-creator-skills. Suede-owned revenue-operations discipline.
When should I use Suede Revops?
Suede Revops fits situations like: defining lead scoring and routing; pipeline stages; deal-desk rules; marketing-to-sales handoffs.
How do I install Suede Revops in Claude Code?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-revops -a claude-code`. Or copy the skill folder (skills/suede-revops in JasonColapietro/suede-creator-skills) into .claude/skills/suede-revops in your project. Claude Code loads it when a task matches its description.
How do I install Suede Revops in Codex?
Run `npx skills add JasonColapietro/suede-creator-skills --skill suede-revops -a codex`. Or copy the skill folder (skills/suede-revops in JasonColapietro/suede-creator-skills) into .agents/skills/suede-revops in your project. Codex loads it when a task matches its description.
Can I use Suede Revops in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add JasonColapietro/suede-creator-skills --skill suede-revops -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/suede-revops, .gemini/skills/suede-revops, .github/skills/suede-revops and .opencode/skills/suede-revops in your project.
What does Suede Revops need to run?
SKILL.md names no scripts, command-line tools or credentials: Suede Revops is instructions for the agent only.
Does Suede Revops access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Suede Revops safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Suede Revops use?
Suede Revops is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Suede Revops use?
About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8k tokens, read only when the agent opens those files.
What are the alternatives to Suede Revops?
Skills that share tags, products or a category with Suede Revops: Revops (AvdLee/RocketSimApp, 805 stars), B2B Lead Generation (minhnv0807/ai-business-skills, 609 stars), Sf Datacloud Retrieve (Jaganpro/sf-skills, 424 stars) and Cold Outreach (ericrisco/rsc-harness, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Suede Revops?
JasonColapietro (a GitHub user) maintains it in JasonColapietro/suede-creator-skills, which has 127 GitHub stars. The repository holds 78 skills in this directory. The repository was last updated on October 10, 2026.
Source: JasonColapietro/suede-creator-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.