writing-skills

Create, edit, and validate skill documentation with YAML frontmatter and RED-GREEN-REFACTOR workflow.

Updated Jan 17, 2026
One-click install
npx skills add https://github.com/brmatola/gremlins --skill writing-skills-brmatola
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/brmatola/gremlins/tree/main/skills/writing-skills
Command: npx skills add https://github.com/brmatola/gremlins --skill writing-skills-brmatola

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill standardizes the process of creating, editing, and validating skill documentation, ensuring every skill has a consistent frontmatter and structure.

Core Features & Use Cases

  • Enforces a YAML frontmatter with required fields (name and description) at the top of SKILL.md.
  • Provides a structured template for skill body including sections like Overview, When to Use, and Quick Start.
  • Supports a RED-GREEN-REFACTOR workflow to maintain quality and prevent regression when skills are updated.

Quick Start

Create a new skill directory (e.g., skills/<skill-name>), add SKILL.md with the required frontmatter, fill in the sections described, and validate the skill by running the RED-GREEN-REFACTOR cycle.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I standardize skill documentation structure across multiple projects?

Standardize skill documentation by enforcing a YAML frontmatter with required name and description fields, followed by a structured body template including Overview, When to Use, and Quick Start sections. This ensures every skill maintains a consistent format across your library.

What is the RED-GREEN-REFACTOR workflow for skill creation?

The RED-GREEN-REFACTOR workflow is a test-driven development cycle used to validate and maintain skill documentation quality. It prevents regression when skills are updated by enforcing structured testing phases throughout the creation and editing process.

How do I create a new reusable skill with test-driven quality?

Create a new skill directory, add a SKILL.md file with required YAML frontmatter, fill in the prescribed body sections, and validate the skill by running the RED-GREEN-REFACTOR cycle to ensure test-driven quality and reusability.

What frontmatter fields are required for valid skill documentation?

Valid skill documentation requires YAML frontmatter at the top of the SKILL.md file containing at minimum the name and description fields. These mandatory fields ensure proper skill identification and standardized documentation structure.

Does this skill creation framework work for individual developers and teams?

Yes, the skill creation framework applies to both individuals and teams building a library of reusable skills. It standardizes documentation structure and enforces test-driven quality across projects regardless of team size.

When should I use a standardized framework for creating skill documentation?

Use a standardized framework when building a library of reusable skills across multiple projects to ensure consistent structure. It prevents documentation fragmentation and maintains quality through test-driven validation during updates.