meta-agent-templates

To validate a workflow.json v1 schema for Gemini runtime artifacts, enforce JSON Schema checks that verify required fields, frontmatter presence, mandatory sections, and forbidden patterns. This prevents structural drift and ensures format consistency across build and runtime stages.

Generating a SYSTEM_PROMPT.md template requires defined validation rules including frontmatter presence, required sections, and the absence of forbidden patterns. Enforcing these consistent runtime templates ensures standardization for meta-level generation tasks.

SKILL.md template lint checks fail during meta-level generation when generated artifacts violate schema rules by missing required frontmatter, omitting mandatory sections, or including forbidden patterns. Enforcing consistent runtime templates blocks this format drift.

Gemini-Harness workflow supports JSON Schema validation rules for v1 schemas by enforcing frontmatter presence, required sections, and forbidden pattern checks. These rules apply to meta-level generation tasks for SYSTEM_PROMPT.md and SKILL.md templates.

The best way to standardize runtime templates and prevent format drift is by applying consistent JSON Schema checks and lint rules across generated artifacts. This enforces field validation, structural integrity, and required frontmatter for Gemini-Harness.