JasonColapietro/suede-creator-skills / skills/suede-revops
suede-revops
VerifiedDefine lifecycle stages, fit and engagement scores, MQL/SQL handoffs, routing SLAs, pipeline hygiene, CRM automation, deal-desk tiers, and dashboard metrics. Use when asked to "fix our lead routing" or specify revenue operations. Returns implementation-ready rules with owners and measurement. NOT FOR: prospect lists (use suede-prospecting), outbound copy (use suede-cold-email), lifecycle campaigns (use suede-emails), pricing strategy (use suede-pricing), or unapproved production CRM changes.
| File | Kind | Size |
|---|---|---|
| CARD.md | markdown | 4.4 KB |
| SKILL.md | skill md | 16.6 KB |
| agents/openai.yaml | config | 606 B |
| evals/evals.json | config | 6.0 KB |
| references/automation-playbooks.md | markdown | 10.9 KB |
| references/lifecycle-definitions.md | markdown | 7.1 KB |
| references/routing-rules.md | markdown | 7.1 KB |
| references/scoring-models.md | markdown | 7.3 KB |
| references/worked-handoff.md | markdown | 1.7 KB |
references/worked-handoff.md
View on GitHub# Suede Revenue Operations Skills: Worked Handoff
## Inputs
Request: “Fix leads getting lost between marketing and sales.” Supply a CRM
field export, lifecycle definitions, an ownership roster, available working
hours, current assignment rules, and a dated sample of handoffs. Synthetic
failure: the segment is known, but the named owner is unavailable and no fallback
queue is defined. No authority to alter production records is included.
## Expected output
Return a lifecycle definition sheet, routing decision table, SLA proposal,
implementation build list, and dashboard spec. The decision table has ordered
conditions, owner or queue, fallback, notification, timestamp, and escalation.
For the unavailable-owner case, route the proposed rule to the team's existing
fallback queue if one exists; otherwise leave a named decision for its owner.
Define time-to-assignment from a specific event timestamp and report business
hours, timezone, exclusions, and denominator. Separate fit from engagement scores.
## Failure case
A lead matches two regions, lacks an account ID, or has no consent basis for
follow-up. Specify a review queue and reason; do not guess territory ownership,
merge identities, or trigger outreach. If the sample lacks a handoff timestamp,
report SLA measurement unavailable rather than estimating response speed.
## Validation
Dry-run the table on a normal lead, missing region, duplicate account, unavailable
owner, and outside-hours arrival. Each case must resolve to exactly one proposed
route or explicit review state. Check that the CRM schema supports every field,
the build list has an owner and rollback plan, and no production mutation is
represented as complete.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |