structured-doc-validate

Validate YAML artifacts for schema shape, reference integrity, and evidence quality.

80|2|Updated May 14, 2026
One-click install
npx skills add https://github.com/PriNova/pi-agent-codebase-workflows --skill structured-doc-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: structured-doc-validate
Source: https://github.com/PriNova/pi-agent-codebase-workflows/tree/main/skills/structured-doc-validate
Command: npx skills add https://github.com/PriNova/pi-agent-codebase-workflows --skill structured-doc-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit canonical structured YAML artifacts to ensure they are trustworthy, repairable, and free from stale context, enabling safer agent prompts and decisions.

Core Features & Use Cases

  • Validate schema shape, reference integrity, evidence quality, coverage, and granularity across repo docs root.
  • Enforce read-only stance on non-structured prose docs and rely on structured YAML as source of truth.
  • Use four-layer validation to surface actionable findings with paths, IDs, severities, and remediation.

Quick Start

Inspect the repo's resolved structured docs root and report findings for repo-level and scoped artifacts.

Frequently Asked Questions about structured-doc-validate

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

FAQPage Schema
How do I validate YAML schema shape and reference integrity in a repository?

Validate YAML schema shape and reference integrity by auditing canonical structured artifacts within a repository's resolved docs root. The process applies a four-layer validation workflow to surface actionable findings with artifact paths, severities, and recommended repairs.

What is the best way to check structured YAML artifacts for evidence quality and coverage?

Checking structured YAML artifacts for evidence quality and coverage requires auditing both repo-level and scoped artifacts. This validation enforces a read-only stance on non-structured prose docs, ensuring the structured YAML remains the trustworthy source of truth for safer agent prompts.

How does structured YAML validation help prevent stale context in codebase review workflows?

Structured YAML validation prevents stale context in codebase review workflows by auditing canonical artifacts for correctness and granularity. It ensures artifacts are trustworthy and repairable, applying runtime schemas to output findings with IDs, severities, and evidence for remediation.

Can I use this validation process for both repo-level and scoped structured docs?

Yes, you can use this validation process for both repo-level and scoped structured docs. It operates within the repository's resolved structured docs root and audits both artifact levels to ensure schema correctness, reference integrity, and evidence quality across the entire documentation structure.

What do I need to set up before validating canonical structured YAML artifacts?

Before validating canonical structured YAML artifacts, you need a resolved structured docs root containing the YAML files. The validation operates within this specific repository directory, applying runtime schemas to audit the artifacts and enforce a four-layer validation workflow.

Why does my structured YAML artifact validation report reference integrity errors?

Structured YAML artifact validation reports reference integrity errors when canonical artifacts contain broken or misaligned references. The four-layer validation workflow detects these issues during the schema shape audit, outputting findings with artifact paths and severities to guide recommended repairs.