schema-sync

Regenerate JSON Schemas from catalog.ts variables and validate consistency.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/mariasebarespersona/Tum-AI --skill schema-sync-mariasebarespersona
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: schema-sync
Source: https://github.com/mariasebarespersona/Tum-AI/tree/main/.claude/skills/schema-sync
Command: npx skills add https://github.com/mariasebarespersona/Tum-AI --skill schema-sync-mariasebarespersona

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Regenerates JSON Schemas from catalog.ts variables and validates consistency across the automation catalog after changes.

Core Features & Use Cases

  • Regenerate all schemas from catalog.ts using the provided script.
  • Validate counts against the catalog to detect drift.
  • Validate schema contents against catalog requirements (types, required fields, and $schema references).
  • Ensure schema-catalog consistency before releases.

Quick Start

Regenerate schemas and verify alignment with the catalog.

Frequently Asked Questions about schema-sync

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

FAQPage Schema
How do I keep JSON Schemas in sync with my catalog variables?

Keep JSON Schemas in sync by regenerating them from catalog.ts variables and validating consistency. The process compares counts and verifies required fields, types, and $schema references to detect drift.

How do I validate JSON Schema contents against a catalog?

Validate JSON Schema contents against catalog requirements by checking required fields, verifying data types, and confirming the presence of the $schema reference to detect any inconsistencies or drift.

When should I regenerate JSON Schemas from my catalog?

Regenerate JSON Schemas after making changes to automation variables or before releases. This ensures the catalog and schemas are aligned, preventing inconsistencies from drifting into production environments.

What do I need to validate schema-catalog consistency before a release?

Validating schema-catalog consistency requires access to catalog.ts, existing JSON Schemas, and the generation script. The script compares counts and validates required fields, types, and $schema references.

Why does my JSON Schema drift from my automation catalog?

JSON Schema drift occurs when automation variables in catalog.ts are modified without regenerating the corresponding schemas. Running the generation script and validating counts and field types resolves this misalignment.