output-style-governance

Validate output-style manifests for frontmatter and protocol compliance.

10|Updated Oct 18, 2025
One-click install
npx skills add https://github.com/CsHeng/dot-claude --skill output-style-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: output-style-governance
Source: https://github.com/CsHeng/dot-claude/tree/main/skills/output-style-governance
Command: npx skills add https://github.com/CsHeng/dot-claude --skill output-style-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill validates and governs output-style manifests to ensure consistency with core rules and safety invariants, guiding style adoption without weakening protocol guarantees.

Core Features & Use Cases

  • Frontmatter Validation: Ensure required fields exist and maintain naming conventions.
  • Protocol Compliance: Detect and prevent instructions that violate governance rules.
  • Integration: Works with governance workflows to surface findings and suggested fixes.

Quick Start

Validate an output-style manifest under output-styles and review any compliance warnings.

Frequently Asked Questions about output-style-governance

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

FAQPage Schema
How do I validate output-style manifests for compliance?

Output-style governance validates manifests in your output-styles/ directory against frontmatter requirements, protocol rules, and safety invariants. It checks required fields, detects rule violations, and surfaces actionable findings to ensure styles meet governance standards without weakening protocol guarantees.

What happens if my output-style manifest violates governance rules?

The Skill performs protocol compliance checks to detect instructions that violate governance constraints. It produces actionable findings and suggested fixes, allowing you to review violations and correct them before integrating styles into your workflow.

Can I use output-style governance with existing governance workflows?

Yes. Output-style governance integrates seamlessly with governance workflows, surfacing compliance findings and suggested fixes so manifest validation fits naturally into your existing governance processes and approval chains.

What frontmatter fields are required in an output-style manifest?

Output-style governance validates frontmatter to ensure required fields exist and maintain naming conventions. Specific requirements depend on your governance protocol; the Skill checks conformance and flags missing or malformed fields with suggested fixes.

How does output-style governance assess the clarity of style behavior?

The Skill evaluates behavior clarity as part of its validation process, ensuring style descriptions are unambiguous and actionable. This assessment integrates with compliance checks to guide safe style adoption and consistency across your output standards.

What's the difference between output-style governance and manual style documentation?

Output-style governance automates validation and compliance checking against protocol rules and safety invariants, surfacing violations and fixes programmatically. Manual documentation alone cannot enforce consistency or detect rule violations without automated checks.