savarez-agent-skill-authoring

Validate in-repo SKILL.md files for frontmatter and structure.

Updated Jun 19, 2026

Search Tags:#documentation #validation #frontmatter #skill-authoring #in-repo #skills-management

Ready to run

npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill savarez-agent-skill-authoring

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: savarez-agent-skill-authoring
Source: https://github.com/AnandaAnugrahHandyanto/savarez_agent/tree/main/skills/software-development/hermes-agent-skill-authoring
Command: npx skills add https://github.com/AnandaAnugrahHandyanto/savarez_agent --skill savarez-agent-skill-authoring

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a formal blueprint and validator-driven process for authoring in-repo SKILL.md files, ensuring consistency and discoverability across Savarez Skills.

Core Features & Use Cases

Enforces required frontmatter fields (name, description) and repository conventions.
Defines a peer-aligned structure to guide in-repo skill creation and updates.
Guides validation steps and best-practice references for skill maintenance.

Quick Start

Follow the in-repo skill-writing guidelines to create or update SKILL.md and validate it with the repository validator.

Frequently Asked Questions about savarez-agent-skill-authoring

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

FAQPage Schema

How do I validate in-repo skill definitions for correct frontmatter and structure?▼

To validate in-repo skill definitions, enforce required frontmatter fields like name and description, and apply a peer-matched outline to ensure standardized documentation across the repository.

What frontmatter fields are required when authoring SKILL.md files?▼

Required frontmatter fields for authoring SKILL.md files include name and description, ensuring your YAML structure meets presence and description length limits for repository consistency.

What's the best way to standardize skill documentation across a repository?▼

The best way to standardize skill documentation is to apply a peer-aligned structure and validator-driven process, enforcing frontmatter presence, naming conventions, and standardized outlines across all skills.

How do I set up a standardized outline for skills-management in software development?▼

Set up a standardized outline for skills-management by following in-repo skill-writing guidelines that define a peer-matched structure, guiding creation and updates for software-development skills.

Are there description length limits for YAML frontmatter in skill authoring?▼

Yes, skill authoring enforces description length limits within the YAML frontmatter to maintain consistency and discoverability, requiring validation to ensure compliance before repository integration.

Why does my in-repo skill validation fail during the authoring process?▼

In-repo skill validation fails when SKILL.md files lack required frontmatter fields, violate YAML structure rules, exceed description length limits, or miss the standardized peer-matched outline.