synthetic-data-generate-eval

Grade synthetic data generation runs across six weighted quality dimensions.

1|2|Updated Apr 1, 2026
One-click install
npx skills add https://github.com/dimagi-internal/ace --skill synthetic-data-generate-eval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: synthetic-data-generate-eval
Source: https://github.com/dimagi-internal/ace/tree/main/skills/synthetic-data-generate-eval
Command: npx skills add https://github.com/dimagi-internal/ace --skill synthetic-data-generate-eval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually validating synthetic data generation runs to ensure they produce demo-quality, believable data is time-consuming and prone to oversight, especially when schema-conformant data can still be obviously synthetic and unusable for stakeholder demos.

Core Features & Use Cases

  • Multi-dimension grading: Evaluates 6 weighted dimensions including record count health, form schema coverage, out-of-chain data plausibility, warning honesty, manifest provenance, and operator next steps.
  • Hard fitness gates: Automatically fails runs with obviously synthetic/garbage data even if they meet all schema conformance requirements, ensuring only believable data passes validation.
  • Use Case: For ACE Phase 7 Plan B workflows, this skill validates that labs-side synthetic generation for Connect opportunities produces enough visits, correctly round-trips named FLWs with their promised archetypes, and generates data that would pass a domain expert's casual review of the labs dashboard.

Quick Start

Use the synthetic-data-generate-eval skill to evaluate the latest synthetic data generation run for your active Connect opportunity and produce a formal quality verdict file.

Frequently Asked Questions about synthetic-data-generate-eval

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

FAQPage Schema
How do I validate synthetic data quality for demo readiness?

Synthetic data validation grades generated run outputs across six dimensions to ensure demo-quality fitness. It reads actual generated records to catch schema-conformant but obviously synthetic datasets that would fail domain expert review.

What is out-of-chain data plausibility checking in synthetic data generation?

Out-of-chain data plausibility checking evaluates whether generated records look believable to domain experts. It catches datasets that technically conform to the form schema but contain obviously synthetic or garbage values unfit for stakeholder demos.

How do I grade a synthetic data generation run for Connect opportunities?

Grading a synthetic data run involves evaluating six weighted dimensions: record count health, form schema coverage, out-of-chain data plausibility, warning honesty, manifest provenance, and operator next steps to produce a formal quality verdict.

Can schema-conformant synthetic data still fail validation for demos?

Schema-conformant synthetic data can still fail validation. Hard fitness gates automatically fail runs with obviously synthetic or garbage data even when all schema conformance requirements are met, ensuring only believable data passes.

What does manifest provenance validation check in synthetic data outputs?

Manifest provenance validation checks the metadata trail of synthetic data generation runs. It confirms the generated dataset has proper provenance records, contributing to the overall demo-quality fitness verdict.

When do I need synthetic data evaluation in an ACE workflow?

Synthetic data evaluation is needed during ACE Phase 7 Plan B Stage 4 to validate labs-side synthetic generation for Connect opportunities. It ensures enough visits are produced and named FLWs correctly round-trip with their promised archetypes.