standards

Name: standards
Availability: InStock
Author: xiaolai

Define a unified output format and severity taxonomy for docs-guardian agents.

6|Updated Feb 28, 2026

Search Tags:#consistency #standards #documentation-quality #qa-guidelines #finding-format #severity-tags #agent-output

Ready to run

npx skills add https://github.com/xiaolai/docs-guardian-for-claude --skill standards-xiaolai

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: standards
Source: https://github.com/xiaolai/docs-guardian-for-claude/tree/main/skills/docs-guardian/standards
Command: npx skills add https://github.com/xiaolai/docs-guardian-for-claude --skill standards-xiaolai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Shared output format, severity tags, and finding structure used by all docs-guardian agents. This standard ensures consistent reporting across agents, enabling reliable audits and automated remediation.

Core Features & Use Cases

Standardized finding structure including file path, line numbers, severity, and detailed descriptions.
Centralized severity taxonomy to rank issues and drive fixes.
Uniform agent header and metadata to enable cross-agent aggregation and reporting.

Quick Start

Follow these standards to align all agent outputs and findings to a single, consistent format.

Frequently Asked Questions about standards

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

FAQPage Schema

What are unified standards for agent output and documentation findings?▼

Unified standards for agent output define a shared format, severity taxonomy, and finding structure for documentation audits. They ensure consistent reporting across staleness, accuracy, coverage, and quality evaluation workflows by requiring a specific frontmatter schema and agent output header.

How do I standardize severity tags for documentation quality audits?▼

To standardize severity tags for documentation audits, apply a centralized severity taxonomy that ranks issues consistently across multiple agents. This ensures uniform issue prioritization and drives reliable automated remediation across all documentation quality evaluation workflows.

How do I format machine-readable findings for automated documentation audits?▼

Format machine-readable findings by adhering to the shared frontmatter schema and Finding Format guidelines. Include the file path, line numbers, severity, and detailed descriptions within the Agent Output Header to generate structured reports for cross-agent aggregation.

Do I need a specific output header for cross-agent documentation reporting?▼

Yes, you need a uniform Agent Output Header and metadata to enable cross-agent aggregation and reporting. This standardized header ensures that outputs from staleness, accuracy, coverage, and quality evaluation agents remain consistent and machine-readable.

What is the best way to structure documentation findings for automated remediation?▼

The best way to structure documentation findings for automated remediation is using a standardized finding structure. Include the file path, line numbers, severity tags, and detailed descriptions to ensure machine-readable outputs that drive reliable automated fixes.

Can I use custom severity tags for docs-guardian agent reports?▼

No, you should not use custom severity tags. The standards require adherence to a centralized severity taxonomy to rank issues uniformly. This ensures consistent reporting and enables reliable cross-agent aggregation across all documentation evaluation workflows.