The Problem

Your code might be great, but nobody finds it. GitHub search ranks repos by metadata quality. Google indexes your README. LLMs cite repos with clear structure. If your README reads like a technical spec, you're invisible to all three.

Stars compound -- a repo with 50 stars gets recommended more than one with 5, which gets recommended more than one with 0. The gap widens every day you wait.

Before vs After

Install

One step. Drop the skill into your Claude Code skills directory:

# Clone into your Claude Code skills folder
git clone https://github.com/199-biotechnologies/github-optimization-skill.git \
  ~/.claude/skills/github-optimization

Then tell Claude Code: "optimize this repo" or "use the github-optimization skill" on any repository.

On first run, the skill asks for your name, X handle, company, and website -- then saves a config file so it never asks again. Every repo you optimize gets your branding, not ours.

How It Works

The skill runs an 8-step pipeline on your repo:

┌──────────────────────────────────────────────────────────┐
│                                                          │
│  0. CONFIG     Load or create your user config (once)    │
│       ↓                                                  │
│  1. AUDIT      Read current README, metadata, tags       │
│       ↓                                                  │
│  2. KEYWORDS   Find target search terms                  │
│       ↓                                                  │
│  3. METADATA   Optimize description + 10-20 topics       │
│       ↓                                                  │
│  4. README     Rewrite as a landing page                 │
│       ↓                                                  │
│  5. HUMANISE   Strip AI patterns from all prose          │
│       ↓                                                  │
│  6. EXTRAS     Add LICENSE, CONTRIBUTING if missing       │
│       ↓                                                  │
│  7. PUBLISH    Commit, push, apply gh repo edit           │
│                                                          │
└──────────────────────────────────────────────────────────┘

Step 5 chains into the humanise-text skill automatically -- every README passes through de-slopping before it ships.

Features

Star Growth Knowledge Base

The skill includes a comprehensive knowledge base on how to grow GitHub stars. Ask "how do I get more stars?" or "launch strategy" and it draws from research across 50+ tactics:

The full knowledge base covers: HN/Reddit/PH detailed playbooks, the stacked launch strategy, GitHub SEO, awesome lists, newsletter directory with submission links, 17 growth hacks, cold start strategy (first 100 stars), and GitHub Trending algorithm mechanics.

What's Inside

github-optimization-skill/
├── SKILL.md           # Skill definition + star growth knowledge base
├── README.md          # You're reading it
├── LICENSE            # MIT
└── CONTRIBUTING.md    # How to contribute

Dependencies

This skill chains into one other skill during execution:

Install both for the full pipeline:

git clone https://github.com/199-biotechnologies/humanise-text-skill.git \
  ~/.claude/skills/humanise-text

User Config

On first run, the skill creates ~/.claude/skills/github-optimization/.config.yml with your details:

# GitHub Optimization Skill -- User Config
author_name: "Your Name"
author_github: "yourusername"
x_handle: "yourhandle"          # leave "" to skip Follow badge
company_name: "Your Company"    # leave "" to skip
company_url: "https://yourcompany.com"
website_url: "https://yoursite.dev"

Edit this file anytime, or tell Claude Code "update my github-optimization config" to change it.

Writing Rules the Skill Enforces

The skill bans common AI writing patterns and enforces a direct, human voice:

Banned words: leverage, streamline, empower, seamlessly, robust, cutting-edge, revolutionize, harness, elevate, supercharge

Required style: Active voice, short sentences, "you/your" address, concrete examples, no filler words, no fake enthusiasm (no exclamation marks)

Contributing

Contributions welcome. If you've found a pattern that drives more stars, a README structure that converts better, or a growth tactic worth adding to the knowledge base, open a PR.

See CONTRIBUTING.md for the 3-step process.

License

MIT -- use it however you want.