research-data-governance

Designs research-data governance operating models with steward roles, policy-as-code, and certification.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill research-data-governance-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: research-data-governance
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/research-data-platform/skills/research-data-governance
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill research-data-governance-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Centralized, manual data governance becomes a bottleneck as research organizations scale, creating approval queues, shadow datasets, and governance theater where policies exist on paper but are never enforced. This Skill designs a right-sized governance operating model that centralizes policy definition while automating enforcement, so researchers keep shipping without routing around the rules. ## Core Features & Use Cases - Governance spectrum placement: Positions the organization between a lightweight steward council and federated computational (data-mesh) governance, with a recommended blend for research divisions. - Steward taxonomy and council design: Maps business and technical steward roles onto existing researchers, defines council charter, cadence, and decision remit. - Certification over gatekeeping: Replaces pre-publication approval with producer self-certification against centrally defined policies, splitting failures into hard-stop (security, PII, license, retention) versus visibility-only quality gaps. - Global vs domain-local rule split: Minimizes global rules and requires each retained rule to ship with automated enforcement as policy-as-code. - Use Case: A research division lead needs to stand up data governance without hiring a bureaucracy. The Skill produces a governance design doc, steward roster, council charter, certification spec, six-step bootstrap plan, and fitness functions for quarterly review. ## Quick Start Use the research-data-governance skill to design a governance operating model for my research division, including steward roles, a global-versus-local rule split, and a certification spec.

Frequently Asked Questions about research-data-governance

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I design data governance for a research organization?

Start by assessing current maturity and de facto data owners, then place the organization on the spectrum between a lightweight steward council and federated computational governance. Follow the six-step bootstrap: write a data mission statement, adopt a framework, select stewards, stand up the council, automate the first policies, and operate with quarterly reviews.

What is governance-by-certification for datasets?

Governance-by-certification replaces pre-publication approval with producer self-attestation against centrally defined policies, similar to UL marks for physical products. Each dataset publishes certification status through a standard interface, and certification checks largely run as data-contract checks in CI.

Which data governance failures should block dataset publication?

Security, access-control, privacy/PII, license/provenance, legal-hold, retention, consent, and eval-contamination failures are hard stops that block publication and access expansion. Noncritical quality and documentation failures are visibility-only, flagged and ranked down rather than blocking.

When should an organization not adopt federated data-mesh governance?

Federated computational governance presumes at least Predictive-stage engineering practice with CI/CD, APIs, and a modern stack. Never recommend Governed-level certification to an organization without working data contracts, since skipping the Data-as-a-product maturity level causes certification to fail.

How do I avoid data governance becoming a bottleneck?

Keep the council small at five to eight members and restrict its remit to defining rules, never approving individual datasets. Require every global rule to ship with automated enforcement as policy-as-code, and measure fitness functions like policy-adoption lead time and time-to-access.