crafting-effective-readmes

Write and improve README files using audience-specific templates and section checklists.

Updated Nov 7, 2024
One-click install
npx skills add https://github.com/jeremysball/dotfiles --skill crafting-effective-readmes-jeremysball
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crafting-effective-readmes
Source: https://github.com/jeremysball/dotfiles/tree/main/.pi/skills-archive/crafting-effective-readmes
Command: npx skills add https://github.com/jeremysball/dotfiles --skill crafting-effective-readmes-jeremysball

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? READMEs often fail because they are written for the wrong audience, missing key sections, or left stale after a project changes. This Skill guides you through creating, updating, adding to, and reviewing README files with templates matched to your project type. ## Core Features & Use Cases - Project-type templates: Ready-to-use structures for open source, personal, internal/team, and config/dotfiles projects. - Task-based workflows: Distinct question sets for creating a new README, adding a section, updating stale content, or reviewing accuracy against the actual project state. - Curated references: Includes the Art of README philosophy, Make a README section guidance, and the Standard Readme specification with minimal and maximal examples. - Use Case: You just built a CLI tool and need documentation. The Skill asks about your audience, applies the open source template, and produces a README with installation, usage examples, contributing, and license sections. ## Quick Start Ask the assistant to write a README for your project and answer its questions about project type and audience.

Frequently Asked Questions about crafting-effective-readmes

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

FAQPage Schema
How do I write a good README for my project?

Start by identifying your audience and project type, then include at minimum a name, a one-to-two sentence description, and usage examples. Add installation steps, contributing guidelines, and a license for open source projects.

What sections should a README have?

Every README needs a name, description, and usage section. Open source projects add badges, installation, contributing, and license; internal projects add architecture and runbooks; config directories add a what's-here table and gotchas.

How do I update a stale README after code changes?

Read the current README, compare it against the actual project state such as package.json and main source files, then flag outdated sections and propose specific edits. Adding a last-reviewed date helps track freshness.

What is the difference between an open source and internal project README?

Open source READMEs target worldwide users with installation, usage, contributing, and license sections. Internal READMEs target teammates with setup steps, architecture notes, environment variables, runbooks, and troubleshooting guides.

What are common README mistakes to avoid?

Common mistakes include missing installation steps, no usage examples, walls of text without headers or tables, stale content, and a generic tone that ignores the actual audience.