readme-standards

Define and enforce README conventions for Esposter monorepo packages.

23|3|Updated Jun 28, 2022
One-click install
npx skills add https://github.com/Esposter/Esposter --skill readme-standards-esposter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: readme-standards
Source: https://github.com/Esposter/Esposter/tree/main/.agents/skills/readme-standards
Command: npx skills add https://github.com/Esposter/Esposter --skill readme-standards-esposter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Esposter README conventions — template, badge rules, and section standards for package READMEs. Apply when creating or updating any README.md file in this monorepo.

Core Features & Use Cases

  • Provides a standard README template for all packages
  • Defines badge rules, license references, and section structure
  • Helps private vs public packages maintain appropriate content

Quick Start

Apply this standard when creating or updating any README.md file in this monorepo to ensure compliance with Esposter conventions.

Frequently Asked Questions about readme-standards

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

FAQPage Schema
How do I standardize README conventions for monorepo packages?

You can standardize README conventions by applying a shared template that enforces badge usage, license references, and section structure across all internal and public monorepo packages. This ensures consistency and readability for every package README.

What sections should a package README template include?

A package README template should include a Quick Start one-liner, license badges, and structured sections aligned with SKILL.md frontmatter requirements. These standard sections improve readability and maintain consistent documentation across packages.

How do badges and license references work in documentation?

Badges and license references in documentation provide quick visual indicators of package status and legal terms. Standard rules define exactly which badges to display and how to reference licenses to maintain consistency across all package READMEs.

Does this README standard apply to both private and public packages?

Yes, this README standard applies to both private and public packages within the monorepo. It helps maintain appropriate content distinctions, ensuring private versus public packages display the correct documentation elements.

When do I need to update an existing README.md file?

You need to update an existing README.md file whenever creating or modifying package documentation in the monorepo. Applying the standard conventions during any update ensures ongoing compliance with template structure, badge rules, and section requirements.

What is the best way to ensure README compliance with SKILL.md frontmatter?

The best way to ensure README compliance is to align your README content directly with the SKILL.md frontmatter and detailed section requirements. This includes implementing the Quick Start one-liner and proper license badges to meet the standardized conventions.