frontmatter-guard

Name: frontmatter-guard
Availability: InStock
Author: starlink-awaken

Validate and repair YAML frontmatter in markdown files for brain runtime compatibility.

Updated Jun 10, 2026

Search Tags:#automation #linting #markdown #validation #yaml #data-integrity

Ready to run

npx skills add https://github.com/starlink-awaken/omostation-gbrain --skill frontmatter-guard-starlink-awaken

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: frontmatter-guard
Source: https://github.com/starlink-awaken/omostation-gbrain/tree/main/skills/frontmatter-guard
Command: npx skills add https://github.com/starlink-awaken/omostation-gbrain --skill frontmatter-guard-starlink-awaken

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill resolves silent data corruption and structural inconsistencies in brain pages, such as malformed YAML, null bytes, and slug mismatches, which can cause synchronization failures or search errors.

Core Features & Use Cases

Automated Validation: Scans brain pages against seven canonical integrity classes to detect structural errors before they impact system performance.
Safe Auto-Repair: Provides a non-destructive fix mechanism that generates backups before modifying files, ensuring data safety during remediation.
Use Case: Use this to audit a large collection of markdown files after a migration or batch import to ensure all frontmatter is correctly formatted and ready for the gbrain runtime.

Quick Start

Run the frontmatter audit command to scan your current brain directory for any structural errors.

Frequently Asked Questions about frontmatter-guard

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

FAQPage Schema

How do I validate and fix YAML frontmatter in markdown files?▼

To validate and fix YAML frontmatter, you can run an automated audit that scans markdown files for structural errors and applies non-destructive repairs with backups. This ensures headers are machine-readable and compatible with runtime requirements.

What causes silent data corruption in markdown frontmatter?▼

Silent data corruption in markdown frontmatter is caused by malformed YAML, null bytes, and slug mismatches. These structural inconsistencies can lead to synchronization failures or search errors if not caught by validation.

How do I audit markdown files for missing delimiters and binary corruption?▼

You audit markdown files by running an automated validation scan that targets integrity issues like missing delimiters and binary corruption. This process detects structural errors before they impact system performance.

Can I safely repair malformed YAML frontmatter without losing data?▼

Yes, you can safely repair malformed YAML frontmatter using a non-destructive fix mechanism. This auto-repair workflow generates backups before modifying files, ensuring complete data safety during remediation.

What's the best way to ensure markdown frontmatter integrity after a batch import?▼

The best way to ensure frontmatter integrity after a batch import is to run an automated audit across your documentation repositories. This validates that all frontmatter is correctly formatted and ready for the runtime.