Writer Structure Guard

Validate article drafts against a canonical structure contract with one self-heal retry.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/JDL440/nfl-eval --skill writer-structure-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Writer Structure Guard
Source: https://github.com/JDL440/nfl-eval/tree/main/.squad/skills/writer-structure-guard
Command: npx skills add https://github.com/JDL440/nfl-eval --skill writer-structure-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validates and enforces a canonical article structure to prevent downstream conflicts in the publishing pipeline, enabling automated recovery loops when drafts deviate from the contract.

Core Features & Use Cases

  • Deterministic guard checks the draft against the canonical structure contract and produces precise failure reasons.
  • Single self-heal retry performs a targeted repair when a structure issue is detected, reducing manual edits.
  • Guarded progression ensures editors cannot advance until structure compliance is satisfied, preserving pipeline integrity.

Quick Start

Run the guard on an in-progress draft to verify structure and trigger a repair cycle if needed.

Frequently Asked Questions about Writer Structure Guard

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

FAQPage Schema
How do I validate article structure before passing drafts to an editor?

To validate article structure before editor handoffs, run drafts against a canonical contract to check structural compliance. This deterministic guard returns precise failure reasons, preventing downstream publishing pipeline conflicts when format requirements are not met.

What is a self-heal retry for draft structure validation?

A self-heal retry for draft structure validation is a targeted repair mechanism that automatically attempts to fix structural deviations once. If a draft fails the canonical contract check, it triggers a single repair cycle before halting on persistent violations.

How do I enforce deterministic article structure in a publishing pipeline?

Enforce deterministic article structure by applying guard rails during pipeline stages where content format is critical. The guard validates drafts against a canonical contract and blocks progression until structural compliance is satisfied, preserving pipeline integrity.

Can I stop editors from advancing drafts with structural violations?

Yes, you can stop editors from advancing drafts with structural violations using guarded progression. The structure guard ensures editors cannot advance content until compliance with the canonical contract is satisfied, preventing malformed drafts from moving forward.

What happens when a draft fails structure validation and the repair fails?

When a draft fails structure validation and the single self-heal repair attempt also fails, the guard halts the pipeline. It stops on persistent violations to prevent malformed content from reaching downstream publishing stages.

Do I need to manually edit drafts when structural issues are detected?

No, manual edits are reduced because the guard performs a single self-heal retry to automatically resolve detected structure issues. You only need manual intervention if the draft fails validation after the automated repair cycle halts.