write-readme

Generate a ready-to-commit README.md from project metadata using a fixed Markdown template.

5|Updated Jul 25, 2025
One-click install
npx skills add https://github.com/tomzx/agents --skill write-readme-tomzx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-readme
Source: https://github.com/tomzx/agents/tree/main/skills/write-readme
Command: npx skills add https://github.com/tomzx/agents --skill write-readme-tomzx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates a complete README.md for a project using a fixed template, saving time and ensuring consistent documentation.

Core Features & Use Cases

  • Template-driven README generation from project metadata and source files.
  • Supports badges, feature lists, roadmap, setup instructions, and licensing info.
  • Generates a ready-to-commit README.md at the project root.

Quick Start

Run the skill with the target project directory to generate a complete README.md in the project root.

Frequently Asked Questions about write-readme

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

FAQPage Schema
How do I auto-generate a README.md from project metadata?

Auto-generate a README.md by running this skill on a project directory containing a license file and package manifest like package.json or Cargo.toml. It applies a fixed Markdown template to produce a formatted, ready-to-commit README.md at the project root.

Does README generation work with different programming language ecosystems?

README generation works across software languages and ecosystems. The skill reads available manifests such as go.mod, package.json, Cargo.toml, or pyproject.toml to extract project metadata and populate the template accordingly.

What sections are included in a template-driven README?

A template-driven README includes badges, feature lists, roadmap, setup instructions, and licensing info. It extracts project metadata from manifests and source files to populate these sections, outputting a complete README.md.

Can I generate documentation for an existing repository, or is it only for new projects?

You can generate documentation for both new and existing repositories. The skill operates on a project directory containing manifests and license files, applying a fixed Markdown template to output a formatted README.md.

What's the best way to ensure consistent project documentation across multiple repositories?

The best way to ensure consistent project documentation is using a fixed Markdown template applied to project metadata. This skill generates a standardized README.md with badges, setup instructions, and licensing info for every repository.

Do I need a license file to generate a README with this template approach?

You need a license file and a package manifest to generate a README with this template approach. The skill operates on a project directory containing these files to extract metadata and output a formatted README.md.