skills-guide

Define and validate SKILL.md frontmatter conventions for reliable skill discovery.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/tvishwanadha/skills --skill skills-guide-tvishwanadha
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skills-guide
Source: https://github.com/tvishwanadha/skills/tree/main/.claude/skills/skills-guide
Command: npx skills add https://github.com/tvishwanadha/skills --skill skills-guide-tvishwanadha

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill defines and enforces standardized frontmatter and content-structure guidelines for SKILL.md files, enabling reliable discovery and consistent authoring across skills.

Core Features & Use Cases

  • Provides a formal specification for required fields (name, description, user-invocable, disable-model-invocation) and optional extensions.
  • Guides authors on content structure, frontmatter formatting, and validation during skill creation, updates, or reviews.
  • Supports consistent documentation of skills across projects, improving automation, tooling, and quality control.

Quick Start

Load this skill to learn and apply standardized frontmatter rules when creating or editing SKILL.md files.

Frequently Asked Questions about skills-guide

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

FAQPage Schema
What frontmatter fields are required in a SKILL.md file?

Required SKILL.md frontmatter fields include name, description, user-invocable, and disable-model-invocation. Defining these fields ensures reliable skill discovery, consistent metadata, and proper automation across projects.

How do I validate skill documentation structure during creation?

You validate skill documentation by applying standardized frontmatter conventions and content-structure guidelines when creating or updating SKILL.md files. This enforces consistent naming, descriptions, and metadata for quality control.

What is the best way to standardize skill metadata for discovery?

Standardizing skill metadata involves enforcing formal frontmatter specifications and optional extensions in SKILL.md files. This provides consistent authoring, improves tooling, and enables reliable skill discovery across projects.

When do I need to review SKILL.md content structure?

Review SKILL.md content structure when creating, updating, or reviewing skills to ensure consistent naming, descriptions, and metadata. Applying validation rules enforces required fields and safety guidance for reliable automation.

Can I include optional extensions in SKILL.md frontmatter?

Yes, SKILL.md frontmatter supports optional extensions alongside required fields like name and description. These extensions allow you to document skills comprehensively while maintaining consistent validation and content structure.