data-product-reviewer

Review research datasets against the DAUTNIVS rubric to score data-as-a-product readiness.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Deciding whether a research dataset is a real, publishable data product or just shared files is usually subjective. This Skill replaces gut feel with an evidence-backed review: it scores a dataset against the DAUTNIVS usability attributes, audits its API affordances, and returns a verdict band with ranked gaps and remediation owners. ## Core Features & Use Cases - DAUTNIVS scoring: Rates Discoverable, Addressable, Understandable, Trustworthy, Natively accessible, Interoperable, Valuable, and Secure on a 0-2 scale with cited evidence from catalogs, contracts, SLO docs, and live product APIs. - Archetype classification: Distinguishes source-aligned, consumer-aligned, and aggregate datasets, adjusting the bar and recommending ownership for aggregates. - Cold-start and agent-consumability tests: Times how long a new user or programmatic agent takes to go from address to schema to sample data without human help. - Use Case: A research platform team wants to publish a training corpus to their internal data marketplace. Run the review to get a verdict band (publish, beta, or not a product), the top-3 gaps ranked by consumer impact, and routing to sibling skills for contract or SLO fixes. ## Quick Start Use the data-product-reviewer skill to assess whether the dataset at this catalog entry qualifies as a publishable data product and list its top gaps.

Frequently Asked Questions about data-product-reviewer

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

FAQPage Schema
How do I assess whether a dataset is a data product?

Score the dataset against the DAUTNIVS attributes (Discoverable, Addressable, Understandable, Trustworthy, Natively accessible, Interoperable, Valuable, Secure) on a 0-2 scale using evidence like catalog entries, contracts, and SLO docs. Totals of 14-16 with no zero in core attributes qualify for publication; below 10 it remains just a dataset.

What is the DAUTNIVS rubric for data product reviews?

DAUTNIVS is an eight-attribute usability rubric extending FAIR principles: Discoverable, Addressable, Understandable, Trustworthy, Natively accessible, Interoperable, Valuable, and Secure. Each attribute is scored 0 (absent), 1 (partial or manual), or 2 (present and self-serve) based on artifacts, not assurances.

How do I test if a dataset is consumable by AI agents?

Run an agent-consumability probe: check whether a programmatic client can resolve the dataset's address to metadata, schema, sample data, and access policy without human intervention. A product only navigable by humans scores at most 1 on Discoverable and Understandable.

What evidence is needed for a data product readiness review?

Pull the catalog or marketplace entry, the data contract and SLO document from Git with CI history, responses from the product's discovery and SLO APIs, storage snapshot history, and consumer records such as experiment trackers pinning checkpoints to dataset versions. Self-reported claims without artifacts score low.

When should a dataset not go through a data product review?

Only datasets intended for cross-team or agent consumption should enter review. Exploratory research data shared within one team should be excluded so the review process does not become gatekeeping theater for early-stage work.

What blocks a dataset from being published as a data product?

A zero score on Secure blocks publication regardless of total score, and any zero in a core attribute caps the verdict at beta or non-product. Scores below 10 mean the asset remains a dataset, and unresolved hard-stop policies prevent even beta publication.