Launchsmith

LaunchSmith

Launch repositories as products without inventing claims. Run deterministic checks first, improve the highest-value gaps, capture real proof, then prepare launch materials.

Workflow

1. Confirm the repository root and intended audience.
2. Run LaunchSmith before editing:

``bash gh launchsmith audit --json-file .launchsmith/audit-before.json --html .launchsmith/report-before.html ``

If the extension is unavailable but this repository is checked out, run node ./gh-launchsmith audit.

1. Read failing and partial findings in priority order. Fix substance before presentation:

• working quick start;
• observable output or demo;
• tests/CI and honest limitations;
• concise positioning and audience;
• license, security, contribution, and issue paths;
• release and distribution assets.

1. Capture proof from actual files, commands, screenshots, tests, releases, or GitHub metadata. Read [references/evidence-standard.md](references/evidence-standard.md) when deciding whether a claim is supported.
2. Rerun the audit. Target at least 80, and do not hide unresolved high-weight findings.
3. Generate the launch pack:

``bash gh launchsmith pack ``

1. Replace every [ADD: ...] placeholder with supported material or leave it visibly unresolved. Validate the pack:

``bash python3 skills/launchsmith/scripts/validate_launch_pack.py .launchsmith ``

1. Read [references/launch-channels.md](references/launch-channels.md) before adapting copy for Hacker News, Reddit, X, or Chinese developer communities.
2. Show the user the final repository changes, verification results, unresolved risks, and prepared drafts. Publish releases or external posts only when the user has authorized those side effects.

Evidence Rules

• Tie every performance, compatibility, adoption, and security claim to a reproducible receipt.
• Prefer one real screenshot or command result over several adjectives.
• Keep limitations near the capability they constrain.
• Never buy, trade, automate, or fabricate stars, followers, comments, downloads, testimonials, or benchmarks.
• Never copy another project's branding, screenshots, or launch copy as if it were original.
• Treat generated channel drafts as editable starting points, not finished posts.

Quality Gate

Before calling a repository launch-ready, verify:

• a new user can reach the first useful result from a clean checkout;
• the README shows what happens, not only what is promised;
• CI runs the documented verification command;
• the license and reporting paths are unambiguous;
• GitHub description, topics, release, and homepage fields match the README;
• the social preview remains readable at small size;
• public copy asks for specific feedback instead of generic engagement.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

• Author: Lwu0rup
• Source: Lwu0rup/gh-launchsmith
• License: MIT
• Homepage: https://lwu0rup.github.io/gh-launchsmith/

Install and usage instructions live in the source repository linked above.