tachikoma-frontmatter

Validate entity frontmatter against schema.yaml and generate decision files.

1|1|Updated Nov 19, 2025
One-click install
npx skills add https://github.com/joshuacook/motoko --skill tachikoma-frontmatter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tachikoma-frontmatter
Source: https://github.com/joshuacook/motoko/tree/main/.claude/skills/tachikoma-frontmatter
Command: npx skills add https://github.com/joshuacook/motoko --skill tachikoma-frontmatter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill analyzes entity frontmatter and proposes fixes to ensure consistency with the defined schema, improving data quality and downstream tooling.

Core Features & Use Cases

  • Validation: Check for missing required fields and invalid values.
  • Suggestions: Propose updates to frontmatter to meet the schema.
  • Batch decisions: Create decisions for multiple entities when issues are similar.

Quick Start

Run tachikoma-frontmatter to review entities and propose fixes in decisions/.

Frequently Asked Questions about tachikoma-frontmatter

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

FAQPage Schema
How do I validate and fix frontmatter metadata across entity files?

Frontmatter validation checks entities against a schema to detect missing required fields, invalid values, and formatting inconsistencies. This Skill reads your schema definition and entity files, identifies issues, and generates decision files proposing concrete fixes to standardize metadata across tasks, notes, roles, and other entity types.

What is frontmatter schema validation and why do I need it?

Schema validation ensures entity metadata follows a defined structure, enabling consistent data quality and reliable downstream tooling. This Skill detects deviations—missing fields, wrong types, inconsistent formatting—and proposes corrections in batch decisions rather than manual entity-by-entity edits.

Can I batch frontmatter fixes across multiple entities at once?

Yes. When multiple entities have similar frontmatter issues, this Skill batches them into single decision files, reducing manual review overhead. It creates decisions proposing grouped updates and tracks changes in the tachikoma-summary file.

How does this Skill work with my existing schema and entity structure?

The Skill reads .claude/schema.yaml to understand required and optional fields, then globs your entity directories to validate against that schema. It respects your existing structure and proposes changes aligned to your defined metadata requirements.

What output does this Skill generate and where does it go?

It generates decision files in decisions/ proposing frontmatter changes, updates the tachikoma-summary.yaml file to track validation results, and leaves original entities unchanged until you review and apply the proposed fixes.

Do I need to manually edit each entity or can fixes be automated?

Fixes are proposed as decisions you can review first, allowing you to inspect and approve changes before applying them. This prevents unwanted overwrites while automating detection and batching of common metadata problems.