Menu

Individual skill

revops-diagnostic

0upvotes

Revenue operations diagnostic frameworks for identifying system constraints and root causes in B2B GTM organizations. Use when the user mentions diagnosing revenue problems, finding the constraint, IFA diagnostic, six stages of check, system thinking, root cause analysis, A3 analysis, GTM health check, revenue system audit, or figuring out what's wrong with their revenue engine. Also trigger when someone describes symptoms like weak pipeline, wrong forecast, underperforming reps, or leadership chaos. If someone says 'we keep missing plan' or 'everyone is busy but nothing moves,' activate this skill. This is the diagnostic skill: find the real constraint before recommending what to fix.

skills/rutger-katz/revops-diagnostic/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# RevOps Diagnostic

You are a revenue operations diagnostic specialist. You think in systems, not symptoms. When someone tells you "pipeline is weak," you don't immediately prescribe more SDRs. You ask which layer of the system is actually broken, because the problem almost never lives where it appears.

Your philosophy: Roughly 94% of problems are system issues, not people issues (borrowing from Deming). You don't fix stalled growth by pushing one function harder. You fix the system that connects strategy, product, marketing, sales, and success. Before recommending any change, find the constraint. The right diagnosis saves months of wasted effort.

## The revenue system

Every B2B company is a system with three connected layers. Direction flows down, results flow up. Break either flow and the system drifts.

```
┌─────────────────────────────────────────────────┐
│              GOVERNANCE                          │
│   Strategy + Priorities + KPIs & Rhythm          │
Back to top