name: "repo-star-forge"
description: "Use when a user wants to make a GitHub repository more compelling to star, fork, or share. This skill audits positioning, README structure, demo proof, discoverability, and onboarding friction, then turns the findings into concrete repo improvements."
Repo Star Forge
Sharpen a repository's first impression so more visitors understand the value quickly and feel confident trying, sharing, or starring it.
When to use
- A repo has traction potential but weak star conversion.
- The README is accurate but vague, flat, or slow to activate.
- A launch is coming and the repo page needs to convert first-time visitors.
- The project is missing proof such as screenshots, examples, benchmarks, or trust signals.
Workflow
- Inspect the repository entry points first.
- Read
README.md, the repo description, topics, examples, docs landing page, and release notes. - Focus on what a stranger sees in the first screen on GitHub.
- Diagnose the highest-leverage conversion blockers.
- Unclear audience or unclear problem statement.
- Time-to-wow is too slow.
- Best feature is buried.
- There is no proof that the project works.
- Setup looks risky, expensive, or annoying.
- Fix the top of the funnel before the details.
- Improve the headline, subhead, quickstart, and first example.
- Move the best demo or screenshot above the fold.
- Make the first successful run feel small and safe.
- Strengthen trust honestly.
- Prefer concrete examples, limitations, compatibility notes, and crisp screenshots.
- Do not invent numbers, testimonials, logos, badges, or adoption claims.
- Leave a growth backlog.
- Recommend the next 3 to 5 experiments most likely to improve discoverability or star conversion.
Expected Deliverables
- A short diagnosis of the main conversion blockers.
- A rewritten or restructured README plan.
- Suggested repo description and GitHub topics.
- A screenshot, demo, or benchmark plan if the repo lacks proof.
- A small growth backlog ordered by likely impact.
Output Style
- Be practical, not hypey.
- Optimize for clarity in the first 20 seconds.
- Prefer concrete edits over generic marketing advice.
- If the repo should not be optimized for stars yet because the product is still unclear, say that directly.
References