← ClaudeAtlas

read-me-launcherlisted

Write audience-aware, repository-grounded GitHub README.md pages: inspect the real repo first, choose evidence (code/visual/behavioral), keep claims matched to manifests/scripts, render-safe Markdown, and scan for secret leaks. Use when writing or redesigning a README; when install docs drift from reality; when images fail on GitHub; or when the user wants trustworthy developer docs.
thatdudealso/read-me-launcher · ★ 0 · Code & Development · score 65
Install: claude install-skill thatdudealso/read-me-launcher
# Read Me Launcher Core promise: **a README that matches the repository.** Inspect first. Never invent stack facts. Choose the minimum honest proof for the audience. Lint for render breaks and secret-looking strings before finishing. ## Step 0: classify 1. Run `scripts/inspect-repo.sh`. 2. Resolve INTERFACE × AUDIENCE × PRIMARY_PROOF ([references/taxonomy.md](references/taxonomy.md)). 3. Map to a mode shorthand if useful ([references/audience.md](references/audience.md)). ## Hard rules (errors) - [ ] Claims about install/run/test match inspect output (✓ verified vs ? unknown) - [ ] No invented features, scripts, or runtimes - [ ] No code fences inside `<div>` / `<section>` / `<center>` - [ ] Local images referenced by the README exist - [ ] `scripts/check-readme.sh README.md` exits 0 (secret + render checks) - [ ] Privacy rules in [references/privacy.md](references/privacy.md) ## Strong defaults (not universal mandates) - Libraries lead with working code, not marketing murals - Internal repos optimize for runbooks, not launch theater - Public GUIs usually need one real screenshot - Add banner/preview/showcase only when each asset proves something - Prefer PNG when embedding raster heroes ([references/visuals.md](references/visuals.md)) ## Style preferences (warnings / prefs) - Em dashes are a preference (`PREF`); use `--strict-style` only if the user wants hard fails - Max ~3 badges above the fold by default - Avoid emoji spam and badge walls ## Workflow 1.