repo-launch-readiness-review
Skill0 starsChanged 5 months agoMITView on GitHub
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.
In this repository19 other files it gives its agents.
- agent-handoff-briefSkill
- api-doc-to-tool-specSkill
- architecture-rfc-reviewSkill
- bug-report-to-reproSkill
- changelog-to-upgrade-planSkill
- competitive-research-briefSkill
- customer-call-to-prdSkill
- database-migration-risk-reviewSkill
- dependency-upgrade-risk-reviewSkill
- incident-log-to-postmortemSkill
- messy-notes-to-decision-logSkill
- privacy-data-flow-mapSkill
- prompt-to-eval-rubricSkill
- roadmap-to-release-planSkill
- security-review-checklistSkill
- support-ticket-to-evalSkill
- telemetry-to-product-insightsSkill
- tool-permission-auditSkill
- workflow-automation-scoutSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Check whether a small repository is understandable, usable, and safe to publish.
- Distinctive: line 14
Use when a repo is close to public release and needs a final trust/readiness review.
- Distinctive: line 15
Do not use when the repo still lacks a working artifact or the task is deep implementation.
- Distinctive: line 26
Check install, quickstart, examples, license, security, and contribution paths.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
- Review whether a new visitor can understand the repo in under one minute.
- Check install, quickstart, examples, license, security, and contribution paths.
- Identify missing trust signals and confusing claims.
- Score readiness and list launch blockers separately from polish.
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

