# Repo Launch Readiness Review

> Use when reviewing a small repository before public launch for README clarity, examples, license, metadata, validation commands, issue hygiene, release notes, and obvious trust gaps.

- Skill: `alexzhu0/repo-launch-readiness-review` (Agent Skill)
- Install (CLI): `npx skillmds@latest add alexzhu0/repo-launch-readiness-review`
- Raw SKILL.md: https://api.skillmd.com/api/skills/alexzhu0/repo-launch-readiness-review/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: alexzhu0 (https://skillmd.com/u/alexzhu0)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/alexzhu0/repo-launch-readiness-review

---


# Repo Launch Readiness Review

## Purpose

Check whether a small repository is understandable, usable, and safe to publish.

## Fit

- Use when a repo is close to public release and needs a final trust/readiness review.
- Do not use when the repo still lacks a working artifact or the task is deep implementation.

## Inputs

- Repository README, file tree, metadata, examples, license, and release notes.
- Target audience, launch channel, and install path if available.
- Known validation commands and open issues.

## Workflow

1. Review whether a new visitor can understand the repo in under one minute.
2. Check install, quickstart, examples, license, security, and contribution paths.
3. Identify missing trust signals and confusing claims.
4. Score readiness and list launch blockers separately from polish.
5. Recommend the smallest changes before publishing.

## Output

Produce Markdown with:

- Readiness Score
- Visitor Summary
- Launch Blockers
- Trust And Metadata Checks
- Example Quality
- Polish Tasks
- Recommendation

## Validation

- Score rationale is visible.
- Blockers are separated from nice-to-have tasks.
- Claims in README are checked against files.
- Missing license or unsafe instructions are treated as blockers.
- Recommendations are small and release-oriented.