readme-writing

Generate standardized five-section READMEs for Gaia folders.

3|1|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/metraton/gaia --skill readme-writing-metraton
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: readme-writing
Source: https://github.com/metraton/gaia/tree/main/skills/readme-writing
Command: npx skills add https://github.com/metraton/gaia --skill readme-writing-metraton

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

READMEs for Gaia folders are often terse or inconsistent, making it hard for developers to understand activation, scope, and conventions. This Skill enforces a structured, comprehensive README template to guide contributors and onboard new team members.

Core Features & Use Cases

  • Standardized five-section template that covers intro, activation, file tree, conventions, and see also links.
  • Activation-first guidance that explains when and how a folder's contents are invoked at runtime or during setup.
  • Documentation drift and validation integration to keep READMEs up to date across folders.

Quick Start

Follow the 5-section template to write or update the folder README and include activation details.

Frequently Asked Questions about readme-writing

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

FAQPage Schema
How do I structure a README for a Gaia folder?

To structure a README for a Gaia folder, use a standardized five-section template covering Intro narrative, When activated, What's here, Conventions, and See also links to ensure activation clarity.

What is documentation drift and how does it affect Gaia components?

Documentation drift occurs when folder contents change but the README remains outdated, reducing onboarding clarity for Gaia components, which validation processes and drift-aware documentation aim to prevent.

How do I write activation guidance for a Gaia folder?

To write activation guidance for a Gaia folder, include an activation-first section explaining when and how the folder's contents are invoked at runtime or during setup within the standardized README template.

Can I use this README template for the Gaia repo root and config folders?

Yes, you can apply this README template to any Gaia folder including the repo root, config, agents, skills, hooks, commands, bin, tests, build, and templates folders to enforce consistent documentation across components.

What is the best way to enforce README consistency during CI checks?

The best way to enforce README consistency during CI checks is to validate the five-section template structure and frontmatter, ensuring standardized activation details and documentation quality across all Gaia folders.

Does the Gaia README template require frontmatter validation?

Yes, the Gaia README template requires frontmatter validation to enforce documentation standards, prevent drift, and maintain consistent activation clarity across all Gaia folders during feature development and CI checks.