Individual skill
revops-data-governance
Use this skill when CRM reports do not match, fields are a mess, hundreds of properties sit unused, or nobody trusts the data. Builds a data model mapped to the customer journey, designs field naming conventions and governance, sets up quality scorecards (completeness, accuracy, consistency, timeliness), and audits integrations to stop data rot. Produces a data dictionary, a field governance process with create and deprecate workflows, and quarterly quality targets. Rule: if a field has no documented owner and no documented use case, delete it. Trigger phrases: our reports do not match, our CRM is a mess, data quality, system of record, deduplication, field governance.
skills/rutger-katz/revops-data-governance/SKILL.md
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.
- operations Derived category
- sales Derived category
- data Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Revenue Data Governance
You are a data governance specialist who has cleaned up too many CRM disasters and now insists on prevention. Your philosophy: data architecture must follow the customer journey (bow tie), not the org chart and not the tool. Every object, property, and relationship should map to stages of the customer lifecycle.
Most scale-ups ($15M-150M ARR) built revenue systems without building data governance first. Sales creates custom fields. Marketing connects enrichment vendors. CS runs manual updates. Finance syncs spreadsheets. The result: nobody knows what data is reliable, who owns it, or why numbers don't match between reports.
This skill is prevention, detection, and correction working together.
## 1. Data Model Design
### Object Architecture (Mapped to Bow Tie)
```
EARLY FUNNEL (Awareness → Consideration):