write-readme

Generate ready-to-publish Markdown README documents with YAML frontmatter from project context.

1|Updated Apr 22, 2026
One-click install
npx skills add https://github.com/terencefan/inority-workspace --skill write-readme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-readme
Source: https://github.com/terencefan/inority-workspace/tree/main/skills/write-readme
Command: npx skills add https://github.com/terencefan/inority-workspace --skill write-readme

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This workflow solves the problem of turning vague project ideas and scattered notes into coherent, well-structured README documents that communicate boundary, purpose, and usage.

Core Features & Use Cases

  • Analyze repository structure to determine the appropriate README boundary (root, module, API, or docs index).
  • Load relevant templates from references and preserve existing terminology when rewriting.
  • Generate a frontmatter block (name and description) and a ready-to-publish Markdown body based on local context.

Quick Start

Provide the project context and requested boundary, and let this skill produce a ready-to-publish README draft.

Frequently Asked Questions about write-readme

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

FAQPage Schema
How do I generate a README from rough project notes and repository context?

To generate a README from rough context, provide your scattered project notes and specify the repository boundary. The skill analyzes the available context, applies markdown templates, and outputs a ready-to-publish document with YAML frontmatter.

What types of README documents can I create for different repository sections?

You can create README documents for root projects, individual modules, APIs, and documentation indexes. The skill adapts to the specified boundary and available local context to produce appropriately scoped markdown files.

Does the generated README markdown include YAML frontmatter for repository metadata?

Yes, the generated README markdown includes a YAML frontmatter block containing the project name and description. This ensures the documentation maintains standard repository metadata alongside the published content.

How do I preserve existing terminology when refining documentation from scattered notes?

To preserve existing terminology when refining documentation, the skill loads relevant templates from its references directory and retains your original project vocabulary while restructuring the rough context into coherent markdown.

What is the best way to structure a docs index for a complex repository?

The best way to structure a docs index is to define the documentation boundary and provide local context. The skill evaluates the repository structure and generates a markdown index that communicates boundary, purpose, and usage clearly.

Can I use existing markdown templates to automate repository documentation creation?

Yes, you can automate repository documentation creation using existing markdown templates. The skill leverages templates from its references directory to transform rough project ideas into structured, ready-to-publish README files.