GitHub Sample or Teaser
Publish a public repo with keyword-optimized README and CTA to attract developers who search GitHub for solutions in your problem space. Converts repo visitors into product leads.
npx gtm-skills add marketing/problem-aware/github-sample-teaserOutcome
≥ 20 stars or ≥ 100 unique visitors and ≥ 1 lead in 1 week
Leading Indicators
- Unique repo visitors
- Stars
- Clones
- README CTA clicks
- Leads
Instructions
-
Research the keyword landscape: run
gh search repos "<problem domain>" --limit 20 --json fullName,description,stargazersCount,repositoryTopics --sort starsto find competing repos, common topics, and gaps. -
Create a public repo with a keyword-rich name and description using
gh repo create. Set 8-12 topics based on keyword research. License: MIT. -
Write a README following the structure: Title + Badges, Problem Statement (3 sentences), Quick Start (copy-pasteable), What It Does (3-5 bullets), CTA Block (with UTM parameters: ?utm_source=github&utm_medium=readme&utm_campaign=<repo-slug>), Contributing, License.
-
Add working sample code that runs from a fresh clone without errors. Must be useful standalone, not just a product demo.
-
Upload a 1280x640 social preview image via repo settings. Set homepage URL to your product site with UTM parameters.
-
Seed distribution: share in 1 relevant subreddit, personal LinkedIn, and 1 Discord/Slack community. Do not run a full launch campaign.
-
Monitor daily for 7 days:
gh api repos/<org>/<repo>/traffic/views,gh api repos/<org>/<repo>/traffic/clones,gh api repos/<org>/<repo> --jq ".stargazers_count". Check PostHog for CTA click-throughs. -
Evaluate after 1 week: >=20 stars or >=100 unique visitors AND >=1 lead. If PASS, proceed to Baseline. If FAIL with >50 visitors but 0 CTA clicks, rewrite CTA. If FAIL with <30 visitors, research new keywords and rename repo.
Recommendations
Time
3 hours over 1 week
Play-specific cost
Free