Claude GitHub is the most comprehensive collection of Claude Code skills for GitHub repository optimization. One command gives you a 0-100 health score with prioritized fixes. Follow-up commands generate the files, rewrite the README, select the right license, and configure your metadata, all using live keyword data from DataForSEO so every recommendation is specific and measurable.
Most GitHub repos are invisible - no keywords in the description, no structured README, missing license files, zero community health signals. Search engines skip them. Developers scroll past them.
Built with the Agent Skills open standard for Claude Code. Scaffolded with AgriciDaniel/skill-forge. SEO methodology adapted from AgriciDaniel/claude-seo.
- What You Get
- Skill Examples
- How the Audit Works
- How to Add Skills to Claude Code
- Getting Started
- Standard Operating Procedure
- How Claude Code Skills Communicate
- Architecture
- Best Practices
- Frequently Asked Questions
- Contributing and Security
- Community
- Other Projects
- Disclaimer
- License
| Command | What It Does |
|---|---|
/github audit |
Score any repo 0-100 across 6 categories with prioritized fixes |
/github legal |
Select a license, generate SECURITY.md, CITATION.cff by default, handle fork compliance |
/github community |
Generate issue templates, CONTRIBUTING.md, CODE_OF_CONDUCT.md, .gitattributes, CI workflow, devcontainer |
/github release |
Plan release strategy, CHANGELOG, badges, versioning, and package distribution |
/github seo |
Run keyword research with real search volume and difficulty data |
/github meta |
Optimize description, topics, homepage URL, feature toggles, and social preview |
/github readme |
Generate or rewrite your README with SEO-optimized headings and banner images |
/github empire |
Portfolio strategy, profile README, AI avatar generation, profile completeness, cross-linking |
Every recommendation cites its source: DataForSEO keyword volume, GitHub API metadata, codebase analysis, or reference guides. Nothing is guesswork.
Overall Score: 60/100
| Category | Score | Weight | Weighted |
|------------------------|-------|--------|----------|
| README Quality | 63 | 25% | 15.8 |
| Metadata & Discovery | 70 | 20% | 14.0 |
| Legal Compliance | 60 | 15% | 9.0 |
| Community Health | 52 | 15% | 7.8 |
| Release & Maintenance | 48 | 15% | 7.2 |
| SEO & Discoverability | 64 | 10% | 6.4 |
Top 3 Actions (by impact):
1. [Critical] Add badges to README (version, license, CI status)
2. [High] Create CONTRIBUTING.md with contribution guidelines
3. [High] Set up GitHub Releases with semantic versioning
Primary Keyword: "claude code skills" (5,400/mo, difficulty 34, Sweet Spot)
GitHub ranks #2 for this query. Recommended for H1, description, first paragraph.
Secondary Keywords:
- "claude code skills marketplace" (320/mo, difficulty 17, +171% quarterly)
- "best claude code skills" (110/mo, difficulty 1, +321% quarterly)
- "how to add skills to claude code" (70/mo, difficulty 32, +586% quarterly)
Topics recommended: claude-code, claude-code-skills, github-optimization...
Run /github audit and it generates a numbered Standard Operating Procedure with your scores. Run each skill in order: legal, community, release, seo, meta, readme. Each skill hands off to the next. Re-audit at the end to measure your improvement.
Run /github audit and 6 specialized agents score your repo in parallel:
| Category | Weight | What It Checks |
|---|---|---|
| README Quality | 25% | Structure, headings, badges, table of contents, code examples |
| Metadata and Discovery | 20% | Description keywords, topics, homepage URL, feature toggles |
| Legal Compliance | 15% | License file, SECURITY.md, CITATION.cff, fork obligations |
| Community Health | 15% | Issue templates, CONTRIBUTING, CODE_OF_CONDUCT, devcontainer |
| Release and Maintenance | 15% | Releases, CHANGELOG, CI badges, dependabot, recency |
| SEO and Discoverability | 10% | Keyword placement, GitHub Explore signals, AI citability |
Each agent uses a detailed rubric with specific point values per checkpoint, not subjective impressions. The final score is a weighted sum. Agents run simultaneously in a single message, so a full audit completes in under 2 minutes.
Audit an entire GitHub profile at once:
/github audit avalonreset
This quick-scans all public repos, selects the top candidates for deep analysis, spawns up to 6 agents per repo, and produces a cross-portfolio report with shared patterns and priorities.
Prerequisites: Claude Code and GitHub CLI (gh), both installed and authenticated.
macOS / Linux:
git clone https://github.com/avalonreset/claude-github.git
cd claude-github
bash install.shWindows (PowerShell):
git clone https://github.com/avalonreset/claude-github.git
cd claude-github
.\install.ps1The installer copies all skills, agents, and reference files to ~/.claude/skills/github/, then walks you through setting up two services:
- DataForSEO (strongly recommended) - powers live keyword research, SERP rankings, and AI visibility tracking. The installer configures the MCP server with your credentials automatically. Without it, SEO-dependent skills fall back to codebase-only analysis and all keyword recommendations are marked "unverified." A free account includes enough credits for hundreds of analyses. A single repo analysis costs about 15-30 cents.
- KIE.ai (strongly recommended) - generates AI banner images for READMEs and AI profile avatars for your GitHub profile. The installer saves your API key to
.env. Without it, image generation is skipped entirely. Each image costs about 4 cents.
Both services are technically optional, but without them you lose the two most differentiated features of the suite: data-backed keyword optimization and professional AI-generated visuals. Set them up during installation. It takes 5 minutes and makes every other skill dramatically more useful.
Restart Claude Code after installing. Skills register on startup.
Run these skills from inside the project you want to optimize. This is the single most important thing to get right.
The skills read your actual source code, configuration files, git history, and GitHub remote to understand what your project is and how to improve it. If you run them from an empty folder or from the wrong directory, Claude has no real data to work with and recommendations will be generic at best.
# Right - run from inside your project
cd ~/projects/my-awesome-tool
claude
> /github audit
# Wrong - running from a random directory
cd ~/Desktop
claude
> /github audit # Claude can't see your code, configs, or git remoteThe audit generates a numbered remediation plan tailored to your repo's scores. Run each skill in order. Each one hands off to the next when it's done.
Phase 1: Per-Repo Optimization (repeat for each repo)
| Step | Command | What It Does |
|---|---|---|
| 0 | /github audit |
Diagnose: scores 6 categories, generates your SOP |
| 1 | /github legal |
Foundation: license, compliance, fork obligations |
| 2 | /github community |
Infrastructure: templates, CoC, devcontainer |
| 3 | /github release |
Versioning: CHANGELOG, badges, catch-up releases |
| 4 | /github seo |
Research: keyword data for description and README |
| 5 | /github meta |
Settings: description, topics, features (uses SEO data) |
| 6 | /github readme |
Capstone: README optimization (uses everything above) |
| 7 | /github audit |
Measure: re-audit to verify improvement |
Skills scoring 90+ are skipped automatically. Each skill ends with a handoff telling you exactly what to run next. Each skill caches its findings in a .github-audit/ directory so downstream skills build on previous results instead of starting from scratch.
Phase 2: Portfolio Optimization (run once, after all repos are done)
| Command | What It Does |
|---|---|
/github empire |
Profile README, cross-linking, topic sync, branding, avatar |
Empire assumes each repo is already in good shape. Always finish Phase 1 on all your repos first.
| Source | Skills That Use It | Why |
|---|---|---|
| Source code and file structure | README, Community, Release | Detects language, frameworks, project type |
package.json, Cargo.toml, etc. |
Legal, Community, Release | Identifies dependencies, license conflicts, build tools |
| Git history and remotes | All skills | Determines repo owner, branch strategy, release cadence |
GitHub API (gh repo view) |
All skills | Reads description, topics, settings, stars, forks |
| Existing community files | Legal, Community | Checks what already exists before generating |
| DataForSEO (if configured) | SEO, README, Meta | Live keyword volume, difficulty, SERP rankings |
Every skill follows the GARE pattern: Gather, Analyze, Recommend, Execute.
- Gather data from the GitHub API, codebase scan, and DataForSEO
- Analyze the current state against the ideal for your repo type and intent
- Recommend specific changes with data sources cited
- Execute only after you approve, with a confirmation gate before any live changes
Skills share data through a .github-audit/ cache directory. When you run /github audit first, it writes audit-data.json and seo-data.json that downstream skills consume automatically. This means /github readme knows your keyword targets, /github meta knows your gaps, and /github legal knows your fork status without re-gathering anything.
| Cache File | Written By | Consumed By |
|---|---|---|
repo-context.json |
Orchestrator | All skills |
seo-data.json |
Orchestrator or /github seo |
/github readme, /github meta |
audit-data.json |
/github audit |
All downstream skills |
legal-data.json |
/github legal |
/github readme (badge selection) |
claude-github/
├── github/ # Orchestrator skill
│ ├── SKILL.md # Routing, intent capture, SEO data pass
│ └── references/ # 9 reference guides (loaded on-demand)
├── skills/ # 8 sub-skills
│ ├── github-audit/ # 0-100 health scoring with 6 parallel agents
│ ├── github-legal/ # License selection, SECURITY.md, fork compliance
│ ├── github-community/ # Community health files and templates
│ ├── github-release/ # Release strategy, CHANGELOG, versioning
│ ├── github-seo/ # Keyword research and content strategy
│ ├── github-meta/ # Description, topics, settings, social preview
│ ├── github-readme/ # README generation, SEO optimization, banner images
│ └── github-empire/ # Portfolio strategy, profile README, cross-linking
├── agents/ # 6 scoring agents (parallel audit)
├── extensions/
│ └── dataforseo/ # DataForSEO MCP server setup
├── install.sh # macOS/Linux installer
└── install.ps1 # Windows installer
1 orchestrator, 8 sub-skills, 6 scoring agents, 9 reference files. The orchestrator detects your repo type (library, CLI tool, API, application, framework, documentation, or skill/plugin) and adjusts recommendations for each.
Getting the most out of the skill suite comes down to running from the right place, in the right order, with the right services configured.
Always run from your project folder. The skills analyze your actual codebase, git history, and GitHub remote. Running from an empty or unrelated directory gives Claude nothing real to work with. Open Claude Code in the root of the repo you want to optimize.
Set up DataForSEO and KIE.ai during installation. Both are technically optional, but without DataForSEO every keyword recommendation is guesswork, and without KIE.ai you skip banner and avatar generation entirely. Five minutes of setup unlocks the most powerful features in the suite.
Run audit first. Always start with /github audit. It produces the baseline score and caches findings that every other skill reads. Without it, downstream skills gather data from scratch, which works but takes longer and misses cross-category insights.
Follow the SOP. After the audit, run skills in the order shown in the Standard Operating Procedure: legal, community, release, seo, meta, readme. Each skill hands off to the next and builds on the cache from previous steps.
Review before executing. Every skill pauses at a confirmation gate before making live changes (pushing releases, editing repo settings, creating files). Read the proposal, adjust if needed, then approve.
Re-audit after changes. Run /github audit again when you finish. The score delta shows exactly what improved and what still needs attention.
Claude Code skills are markdown instruction files that extend Claude Code with specialized capabilities. They follow the Agent Skills open standard, which means any SKILL.md file placed in ~/.claude/skills/ is automatically loaded when Claude Code starts. Skills can define triggers, reference files, and sub-agents.
Run the installer (bash install.sh or .\install.ps1). It copies all skill files to ~/.claude/skills/github/ and configures the DataForSEO MCP server. After installation, restart Claude Code and the skills are available immediately. Type /github to see available commands.
Skills are instruction files (SKILL.md) that Claude loads based on triggers in your message. They define what to do and how. Agents are sub-processes that skills can spawn to run tasks in parallel. In this suite, the /github audit skill spawns 6 scoring agents simultaneously, one per category, so a full audit completes in a single pass instead of running checks sequentially.
No. Every skill works without DataForSEO by falling back to codebase analysis, GitHub API data, and built-in reference guides. However, keyword recommendations will be marked "unverified" without live search data. DataForSEO adds real volume numbers, difficulty scores, and SERP verification for about 15-30 cents per repo analysis.
It is the only skill suite that combines live keyword research (via DataForSEO), AI image generation (via KIE.ai), and a structured audit across 6 categories into a single workflow. Most Claude Code skills handle one task. Claude GitHub handles eight, and they share data through a cache so each step builds on the last. The audit-to-readme pipeline takes a repo from zero community health signals to a fully optimized public project in under an hour.
Contributions are welcome. If you find a bug or have a feature request, open an issue. Pull requests are encouraged - see CONTRIBUTING.md for guidelines.
For security vulnerabilities, do not open a public issue. Email benjamin@rankenstein.pro directly. See SECURITY.md for the full disclosure policy and response timelines.
Join AI Marketing Hub Pro for access to exclusive projects (referral link).
gemini-seo - 14 professional SEO workflows for Gemini CLI. Technical audits, schema markup, Core Web Vitals, E-E-A-T, and AI search readiness.
BenjaminTerm - Hacker-styled WezTerm distribution for Windows. Smart clipboard, paste undo, 86 curated dark themes, borderless glass mode.
wan2gp-operator - CLI operator for Wan2GP text-to-video. VRAM-aware compose, headless batch runs, and a music video pipeline.
This tool provides automated recommendations for GitHub repository optimization, including license selection and compliance guidance. It is not legal, financial, or professional advice. All recommendations are generated by AI-driven analysis and should be reviewed with your own due diligence before applying. For complex licensing or compliance situations, consult a qualified attorney. The authors assume no liability for decisions made based on this tool's output. See LICENSE for full terms.
MIT. Free and open source. See LICENSE for full terms.