← ClaudeAtlas

github-project-launchlisted

This skill should be used when the user wants to create, launch, or grow a GitHub public repository. It provides battle-tested strategies for README optimization, launch burst tactics, sustained growth, contributor onboarding, and analytics iteration. Triggers include phrases like "new GitHub repo", "launch project", "get stars", "grow open source", "GitHub marketing", "repo promotion", or when the user is preparing to make a repository public.
ToussaintKnight/github-project-launch · ★ 0 · Code & Development · score 73
Install: claude install-skill ToussaintKnight/github-project-launch
# GitHub Project Launch Skill ## Purpose Provide a complete go-to-market playbook for GitHub repositories. Cover the full funnel from repo creation and README optimization through coordinated launch bursts, sustained content distribution, contributor community building, and data-driven iteration. Ensure the user avoids common pitfalls like deleting/recreating repos or treating GitHub as a passive code dump. ## When to Use - The user asks about launching a new GitHub project or making a private repo public - The user wants to grow stars, contributors, or visibility for an existing public repo - The user mentions GitHub marketing, repo promotion, open source growth, or community building - The user is preparing a README, demo, or release and wants optimization advice - The user is unsure whether to delete and recreate a repo for a "fresh launch" ## How to Use This Skill ### Step 1: Diagnose the Current State Determine which phase the repo is in: - **Pre-launch:** Repo is private or public but unannounced; README and community standards need work - **Ready to burst:** README is polished; user wants to drive the first 48-hour traffic spike - **Sustained growth:** Repo has initial traction; user wants long-term organic growth - **Contributor scaling:** Repo has stars but few contributors; user wants to build a community - **Analytics iteration:** Repo is live; user wants to optimize based on data ### Step 2: Load the Detailed Playbook Read `references/launch-playbook.md`