writing-skills

Enforce consistent YAML frontmatter and structure in SKILL.md files.

33|10|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/andreaswasita/copilot-cowork-dojo --skill writing-skills-andreaswasita
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/andreaswasita/copilot-cowork-dojo/tree/main/skills/writing-skills
Command: npx skills add https://github.com/andreaswasita/copilot-cowork-dojo --skill writing-skills-andreaswasita

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures consistent SKILL.md structure and frontmatter so agents can parse, discover, and activate skills without surprises.

Core Features & Use Cases

  • Enforces a standardized frontmatter with required fields (name, category, description) and a uniform body layout for reliability.
  • Provides a repeatable template and review process to accelerate skill creation and quality checks.
  • Practical use: authors draft SKILL.md properly, reviewers validate adherence, and automation can auto-discover skills.

Quick Start

Follow the standardized SKILL.md template to author or review a skill.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I standardize YAML frontmatter in SKILL.md for auto-discovery?

To standardize YAML frontmatter in SKILL.md, include the required fields name, category, and description at the root. This consistent structure enables agents to parse and auto-discover skills without manual intervention.

What is the required structure for a valid SKILL.md file?

A valid SKILL.md file requires YAML frontmatter containing name, category, and description at the root, followed by a well-structured body with required sections to ensure reliable parsing.

How do I validate SKILL.md frontmatter and body layout?

You validate SKILL.md frontmatter and body layout by checking for required YAML fields name, category, and description, and ensuring the body sections adhere to the standardized template.

What's the best way to create markdown documentation for skill authoring?

The best way to create markdown documentation for skills is following a standardized SKILL.md template, enforcing consistent YAML frontmatter and a uniform body layout for quality checks.

Do I need any dependencies to validate SKILL.md structure?

You do not need any dependencies to validate SKILL.md structure. The validation process relies on enforcing a consistent YAML frontmatter and body layout without external components.