validate-data

Validates JSON data files for syntax errors, schema consistency, and cross-file integrity.

1|Updated Feb 1, 2025
One-click install
npx skills add https://github.com/TiagoDanin/TiagoDanin.github.io --skill validate-data-tiagodanin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate-data
Source: https://github.com/TiagoDanin/TiagoDanin.github.io/tree/main/.claude/skills/validate-data
Command: npx skills add https://github.com/TiagoDanin/TiagoDanin.github.io --skill validate-data-tiagodanin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual edits to JSON data files often introduce syntax errors, duplicate slugs, malformed dates, or inconsistent tags that only surface as build failures. This Skill catches those issues early by validating all data files before builds or commits. ## Core Features & Use Cases - JSON Syntax & Schema Validation: Parses all files in src/data/ and checks required fields, date formats, slug uniqueness, and URL formats for posts, talks, timeline, and project data. - Cross-File Integrity Checks: Detects duplicate slugs across collections, inconsistent date formats, and tag capitalization mismatches. - Structured Validation Report: Outputs a per-file report with errors, warnings, entry counts, and file size anomalies, plus optional guided fixes. - Use Case: After bulk-editing posts.json, run validation before yarn build to catch a duplicate slug and two malformed dates instead of debugging a failed static export. ## Quick Start Ask the assistant to validate all JSON data files in src/data and report any errors or warnings before the next build.

Frequently Asked Questions about validate-data

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

FAQPage Schema
How do I validate JSON data files before a build?

Run the validate-data skill to parse all JSON files in src/data and check syntax, required fields, date formats, and slug uniqueness. It reports errors and warnings per file so you can fix issues before running yarn build.

How to check for duplicate slugs across JSON content files?

The validation performs cross-file checks comparing slugs in posts.json, talks.json, and timeline.json. Any duplicate slug is reported with the conflicting entry numbers so you can rename one of them.

What date formats are supported in the data files?

Posts use the format "MMM DD, YYYY" such as "Jan 26, 2026" with valid English month abbreviations. Timeline entries accept ISO dates like 2024-11-15, "MMM YYYY", or a plain year.

Can validation automatically fix errors in JSON files?

Validation is non-destructive by default and only reports issues. After the report, it can optionally offer fixes such as correcting date formats, sorting entries chronologically, generating missing slugs, or normalizing tag capitalization with confirmation.

When should I run data validation in my workflow?

Run it before builds, after manual JSON edits, before commits, or as part of a CI/CD pipeline. It can also be integrated into a git pre-commit hook to catch data errors early.