📦

revops

Name: revops
Author: coreyhaines31

v2.0.0 Content revision r1 Safe ⚙️ External commands📁 Filesystem access

Optimize Revenue Operations and Lead Handoffs

Disconnected lifecycle rules create slow handoffs and unreliable pipeline data. This skill designs scoring, routing, automation, and dashboard specifications for aligned revenue teams.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "revops" from https://skillstore.io/skills/coreyhaines31-revops.md and its manifest at https://skillstore.io/api/skills/coreyhaines31-revops/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/coreyhaines31-revops.md Signed manifest GET /api/skills/coreyhaines31-revops/manifest Signed lockfile GET /api/skills/coreyhaines31-revops/lockfile

Test it

Using "revops". Create lifecycle stages for a hybrid B2B SaaS company with a four-hour MQL response SLA.

Expected outcome:

Stage: MQL. Entry requires ICP fit and demonstrated buying intent.
Owner: Marketing until assignment. Sales accepts or rejects within 48 hours.
Automation: Alert the assigned representative immediately and escalate after four business hours.

Using "revops". Build a scoring model for a mid-market software company with a 70-point MQL threshold.

Expected outcome:

Fit: Company size, target industry, and decision-maker role contribute 45 points.
Engagement: Demo requests, pricing visits, and webinar attendance contribute 55 points.
MQL threshold: 70 points. Review false positives and missed wins each quarter.

Using "revops". Design routing for named accounts, enterprise territories, and a general sales pool.

Expected outcome:

Priority order: Named account, enterprise territory, regional team, then round-robin.
Capacity rule: Exclude unavailable representatives and preserve assignment history.
Fallback: Route unmatched leads to the RevOps queue and alert the owner.

Security Audit

Safe

v7 • 7/13/2026 Open versioned report

All 20 static findings are false positives caused by ordinary prose, Markdown formatting, and relative documentation links. The cited passages contain no executable commands, traversal operations, prompt injection, or data-exfiltration behavior.

Files scanned

1,460

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (1)

SKILL.md:15

📁 Filesystem access (11)

SKILL.md:321 SKILL.md:325 SKILL.md:326 SKILL.md:327 SKILL.md:328 SKILL.md:329 SKILL.md:330 SKILL.md:331 SKILL.md:332 SKILL.md:333 SKILL.md:334

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/coreyhaines31-revops/audits/7?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/coreyhaines31-revops/security.svg)](https://skillstore.io/skills/coreyhaines31-revops?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/coreyhaines31-revops?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/coreyhaines31-revops/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/coreyhaines31-revops.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

coreyhaines31. (2026). revops security audit report (audit version 7) [Author version 2.0.0]. Skillstore. https://skillstore.io/skills/coreyhaines31-revops/audits/7

BibTeX citation

@techreport{coreyhaines31-coreyhaines31-revops-2026,
  author = {coreyhaines31},
  title = {revops security audit report (audit version 7)},
  institution = {Skillstore},
  year = {2026},
  number = {7},
  url = {https://skillstore.io/skills/coreyhaines31-revops/audits/7},
  note = {Author version 2.0.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "revops security audit report (audit version 7)"
version: "2.0.0"
type: report
authors:
  - name: "coreyhaines31"
date-released: "2026-07-13"
url: "https://skillstore.io/skills/coreyhaines31-revops/audits/7"
identifiers:
  - type: other
    value: "skillstore:coreyhaines31-revops:audit:7"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High

Architecture

100

Maintainability

Content

Community

Spec Compliance

What You Can Build

Redesign lifecycle handoffs

Document shared stages, owners, SLAs, and recycling rules for marketing, sales, and customer success.

Launch scoring and routing

Create an initial lead scoring model and routing decision tree for a growing inbound program.

Establish pipeline governance

Define opportunity stages, required fields, approval rules, and executive metrics for consistent forecasting.

Try These Prompts

Map our lifecycle

Map a lead lifecycle for [company type] using [GTM motion]. Define each stage, entry criteria, exit criteria, owner, and handoff SLA.

Build a lead scoring model

Create a 100-point lead scoring model for [ICP] with [ACV] and [sales cycle]. Include fit, engagement, negative signals, threshold, and calibration plan.

Design routing and automation

Design lead routing for [team structure] in [CRM]. Include precedence, capacity handling, fallback ownership, SLA alerts, recycling, and an audit log.

Audit the revenue engine

Audit this lifecycle, scoring, routing, pipeline, and automation setup: [details]. Identify leaks, conflicting rules, missing data, risks, priorities, and measurable fixes.

Best Practices

Use historical closed-won and disqualified lead data before assigning scoring weights.
Agree on stage definitions and ownership before implementing CRM automation.
Pilot changes with a small segment, monitor exceptions, and recalibrate quarterly.

Avoid

Do not automate undefined stages or conflicting handoff rules.
Do not treat one engagement event as sufficient qualification without fit.
Do not launch routing without fallback ownership, capacity checks, and decision logging.