Menu

Individual skill

readme-atlas

0upvotes

Write, improve, or review repository READMEs for accurate onboarding and polished visual presentation. Use for README creation, visual design, layout, badges, screenshots, project positioning, and translation, using repository evidence and patterns studied across open-source projects.

skills/readme-atlas/SKILL.md

Read pinned source

Source commit 18f60638764ce36910d5977c1cea4c47dce9990d

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
4
Repository last updated
Oct 23, 2026
License
MIT

Observed agent integration: claude-code

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# README Atlas

Help the intended reader recognize the project, enjoy a coherent presentation, decide whether it fits, and reach a useful first result. Treat visual quality, factual accuracy, and onboarding as complementary parts of README quality. Choose the structure and visual language from the project's actual distribution, audience, and identity. A popular project's README is evidence of one editorial choice, not a universal template.

## Choose the task

- **Create:** inspect the project, choose a reader journey, and write the requested README.
- **Improve:** preserve correct information, useful anchors, and the project's voice; fix the reader's actual obstacles. Avoid a full rewrite for a narrow edit.
- **Review:** report concrete problems with evidence and proposed fixes. Do not edit unless requested.
- **Translate:** preserve commands, identifiers, URLs, requirements, and feature status. Keep language files mutually discoverable and flag factual drift separately from translation.

Use the requested language. Otherwise follow the existing README or the user's language for a new one. Create multiple language files only when requested or already part of the project.

## Establish the facts before the prose
Back to top