service-validate

Validate service documentation against predefined standards for frontmatter, sections, and changelog compliance.

Updated Apr 2, 2026
One-click install
npx skills add https://github.com/oogDZ/2 --skill service-validate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: service-validate
Source: https://github.com/oogDZ/2/tree/main/.claude/skills/service-validate
Command: npx skills add https://github.com/oogDZ/2 --skill service-validate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This tool validates service documentation against a defined standard to ensure consistency, completeness, and quality across specs/docs.

Core Features & Use Cases

  • Enforces required frontmatter and documentation structure.
  • Validates tables, subsections for API/Data Model, autonomy, and changelog.
  • Supports per-service checks and batch validation across all specs/docs.

Quick Start

Run /service-validate [service-name | --all] to validate a single service or all services.

Frequently Asked Questions about service-validate

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

FAQPage Schema
How do I automate service documentation standard checks across a repository?

You can automate service documentation standard checks by running a batch validation command across all specs to ensure repository-wide conformance with required frontmatter, sections, tables, and changelog compliance.

What documentation structure is required to pass service quality validation?

Service documentation validation requires frontmatter presence, required sections, properly formatted tables, API and Data Model subsections, autonomy declarations, and changelog compliance to pass quality checks.

Can I validate a single service document instead of checking all specs at once?

Yes, you can validate a single service document by passing the specific service name to the validation command, which checks frontmatter, required sections, tables, API/Data Model subsections, autonomy, and changelog for that service.

What is the best way to enforce frontmatter and changelog compliance in service docs?

The best way to enforce frontmatter and changelog compliance is using an automated validation tool that checks service documentation against predefined standards, ensuring consistency and completeness across all repository specs.

Why does my service documentation fail quality checks for missing API subsections?

Service documentation fails quality checks when required API and Data Model subsections are missing, as validation enforces specific structural standards including these subsections, frontmatter, tables, autonomy, and changelog entries.

Do I need any dependencies to run batch validation on service documentation standards?

No external dependencies are required to run batch validation on service documentation standards. The validation tool operates standalone to check frontmatter, sections, tables, API/Data Model subsections, autonomy, and changelog compliance across all services.