Dimensional model validator

Skill a5c-ai/babysitter/library/specializations/data-engineering-analytics/skills/dimensional-model-validator

Babysitter enforces obedience on agentic workforces and enables them to manage extremely complex tasks and workflows through deterministic, hallucination-free self-orchestration

Install

npx -y skills add a5c-ai/babysitter --skill dimensional-model-validator

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

What its author says it does

Copied from the file, not written here

Validates dimensional models against Kimball methodology best practices

SKILL.md

2.2 KB, as published. Nobody here has run it

Dimensional Model Validator

Overview

Validates dimensional models against Kimball methodology best practices. This skill ensures dimensional models conform to proven design patterns for analytical workloads.

Capabilities

Star/snowflake schema validation
Grain definition verification
Surrogate key design validation
SCD type appropriateness check
Conformed dimension analysis
Fact table type validation (transaction, periodic, accumulating)
Degenerate dimension identification
Role-playing dimension detection
Bus matrix compliance checking

Input Schema

{
  "model": {
    "facts": ["object"],
    "dimensions": ["object"],
    "relationships": ["object"]
  },
  "businessProcess": "string",
  "busMatrix": "object"
}

Output Schema

{
  "validationScore": "number",
  "issues": [{
    "severity": "error|warning|info",
    "element": "string",
    "rule": "string",
    "message": "string"
  }],
  "suggestions": ["string"],
  "conformedDimensionOpportunities": ["object"]
}

Target Processes

Dimensional Model Design
Data Warehouse Setup
OBT Creation

Usage Guidelines

Provide complete model definition with facts, dimensions, and relationships
Include business process context for grain validation
Supply bus matrix if checking conformed dimension compliance
Review all issues, prioritizing errors before warnings

Best Practices

Validate grain definition before proceeding with implementation
Ensure surrogate keys are system-generated, not business keys
Check for conformed dimension opportunities across subject areas
Verify fact table type matches the business process characteristics
Document role-playing dimensions clearly