agentleFS
alexzhu0alexzhu0/agent-ready-skills/skills/repo-launch-readiness-review/SKILL.md

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.

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
  1. Distinctive:

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

    line 10
  2. Distinctive:

    Use when a repo is close to public release and needs a final trust/readiness review.

    line 14
  3. Distinctive:

    Do not use when the repo still lacks a working artifact or the task is deep implementation.

    line 15
  4. Distinctive:

    Check install, quickstart, examples, license, security, and contribution paths.

    line 26

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.