writing-skills

Define skill-writing templates with YAML frontmatter and RED-GREEN-REFACTOR workflow.

2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill writing-skills-ahmedelhadarey
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/AhmedElhadarey/Gilfoyle/tree/main/skills/writing-skills
Command: npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill writing-skills-ahmedelhadarey

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined framework for authoring and validating skills using a test-driven approach, ensuring documentation becomes a reliable, reusable blueprint that resists ad-hoc rationalizations.

Core Features & Use Cases

  • Enforces RED-GREEN-REFACTOR cycles on skill creation and updates to improve quality and maintainability.
  • Establishes a canonical SKILL.md structure with mandatory frontmatter (name, description) and a concise body that guides discovery and usage.
  • Provides guidance on testing, rationalization capture, and deployment checkpoints to prevent regression and ensure repeatable results.
  • Use cases include creating new skills, editing existing ones, and verifying skills before deployment across teams.

Quick Start

Begin by reading the skill structure, then apply the RED-GREEN-REFACTOR workflow to a sample skill to validate behavior before deployment.

Frequently Asked Questions about writing-skills

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

FAQPage Schema
How do I use test-driven development to write skill documentation?

Test-driven documentation applies a RED-GREEN-REFACTOR cadence to skill authoring, enforcing structured SKILL.md templates with mandatory YAML frontmatter and concise descriptions to create reliable, reusable blueprints.

What is the RED-GREEN-REFACTOR cycle for skill authoring?

The RED-GREEN-REFACTOR cycle is a disciplined workflow for creating and updating skills, capturing rationalizations and running testing checkpoints to prevent regression and ensure repeatable documentation results.

How do I structure YAML frontmatter for skill discovery?

Structure YAML frontmatter by including mandatory name and description fields, followed by a three-section description with clear triggers and concise searchable metadata like keywords and category to optimize loading.

What's the best way to prevent regression when updating existing skills?

The best way to prevent regression is applying the RED-GREEN-REFACTOR workflow, which provides deployment checkpoints and rationalization capture to validate behavior before deploying updated skills across teams.

How do I validate skill behavior before deployment?

Validate skill behavior by reading the skill structure and applying the RED-GREEN-REFACTOR workflow to a sample skill, using the provided testing guidance and deployment checkpoints to verify quality and maintainability.