← ClaudeAtlas

oss-readinesslisted

Audits a repository for public-release ("open source") readiness: README front-door quality (Why/How/Benefits, badges, quick example, section order), doc deduplication, community-health files (LICENSE, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT, issue/PR templates), and repo signals (description, topics, CI badge, releases, .gitignore, secrets). Fans out 4 parallel dimension agents into outputs/OSS-Readiness.md, P0-P3 findings. --apply-fixes drafts missing community-health files tailored to the repo, adds a CI badge, reorders README, dedups docs — escalates subjective calls (tagline, license choice, prose voice) as TODOs, never guesses. Use for "oss readiness", "prep for public release", "audit my repo for open source", "make this repo public-ready", "readme tuning", "make it presentable", or German "fit für open source", "repo veröffentlichen", "readme aufhübschen", "public-ready machen", "oss-check". Does NOT review source-code quality/security — use /branch-review or /full-project-review.
lx-wnk/skills · ★ 1 · AI & Automation · score 71
Install: claude install-skill lx-wnk/skills
# OSS Readiness Audits a repository's public-release front door — README, docs, community-health files, and discoverability signals — and, on opt-in, drafts the missing pieces. ## Scope **In** - README front-door quality: Why/How/Benefits, inverted-pyramid section order, badges, quick example. - Docs single-source / deduplication across all Markdown docs in the repo. - OSS community-health files: `LICENSE`, `CONTRIBUTING.md`, `SECURITY.md`, `CODE_OF_CONDUCT.md`, issue/PR templates. - Repo discoverability signals: GitHub description + topics, CI presence + badge, releases/tags, `.gitignore` sanity, no committed secrets. **Out** - Marketing, social, or website copy. - Source-code quality or security of the codebase itself — that is `/branch-review` (diff-scoped) or `/full-project-review` (whole-project). - Release execution (tagging, publishing) — stays manual or `gh`. ## Examples ```bash # Read-only audit of the current repo /oss-readiness # Read-only audit of a different path /oss-readiness ../other-repo # Apply safe fixes: draft missing community-health files, add a CI badge, # reorder the README, dedup docs — subjective calls become TODOs /oss-readiness --apply-fixes ``` ## Workflow / Phases ```mermaid flowchart TD A[Phase 0: Probe existing state + detect stack] --> B[Phase 1: Fan out 4 dimension agents in parallel] B --> C[Phase 2: Consolidate into OSS-Readiness.md] C --> D{--apply-fixes flag?} D -->|No| E[Done — read-only report] D -->|Yes|