validate

Update YAML frontmatter in Markdown files with review statuses and metadata.

7|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/hhellbusch/my-ai-workspace --skill validate-hhellbusch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/hhellbusch/my-ai-workspace/tree/main/.agents/skills/validate
Command: npx skills add https://github.com/hhellbusch/my-ai-workspace --skill validate-hhellbusch

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of tracking whether files have been reviewed and validated by humans, facilitating quality assurance and version control.

Core Features & Use Cases

  • Validation Recording: Mark individual Markdown files or directories with validation types such as 'read', 'fact-checked', or 'used-in-practice'.
  • YAML Frontmatter Updating: Automatically update or insert review metadata in files, including timestamps and commit SHAs.
  • Use Case: When maintaining a documentation repository, ensure each file has been reviewed by a human by adding or updating review status, with optional notes.

Quick Start

Use this skill to mark docs/api-reference.md as 'read' and 'voice-approved' with notes indicating the date of review.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I track which Markdown files have been human-reviewed in a documentation repository?

To track human-reviewed Markdown files, you can programmatically mark individual files or directories with validation types such as 'read' or 'fact-checked'. This process automatically inserts review metadata, including timestamps and commit SHAs, into YAML frontmatter for future reference.

How do I add review status and validation metadata to YAML frontmatter in Markdown files?

Adding review status to YAML frontmatter involves programmatically updating or inserting validation metadata directly into the file headers. You can mark files with specific validation types like 'read' or 'used-in-practice' and include optional notes indicating the review date.

Can I mark an entire directory of documentation files as validated at once?

Yes, you can mark an entire directory of documentation files as validated simultaneously. The validation recording feature supports applying review statuses and updating YAML frontmatter metadata across bulk file collections.

What types of validation statuses can I record for technical documentation?

You can record multiple validation types for technical documentation, including 'read', 'fact-checked', and 'used-in-practice'. These statuses track the specific human review actions performed on the content.

Does this YAML frontmatter validation process require external dependencies?

No, this YAML frontmatter validation process requires no external dependencies. It operates independently using scripts to parse Markdown files and update metadata headers.

What is the best way to maintain quality control standards for research notes?

The best way to maintain quality control for research notes is programmatically marking files as reviewed or approved. By updating YAML frontmatter with timestamps and commit SHAs, you ensure high content standards and facilitate version control.