Repo to Skill
Generate an agent skill from a GitHub open-source repository. Use when asked to create a skill from a repo URL, turn a GitHub project into a usable skill, or generate skill files for a CLI/library/framework. Triggers on phrases like "create a skill from this repo", "make a skill for vllm", "turn this GitHub project into a skill", "generate a skill from repo". Also use when asked to "skillify" a tool or generate usage instructions from source code. Command usage — `/skill repo-to-skill <github-repo-url>`.
Install
npx skills add shuyhere/repo-to-skill --skill repo-to-skillgit clone --depth 1 https://github.com/shuyhere/repo-to-skill.git /tmp/repo-to-skill
mkdir -p ~/.claude/skills
cp -r /tmp/repo-to-skill/. ~/.claude/skills/repo-to-skillPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Repo-to-Skill Generator Generate a complete, tested, and evaluated agent skill from any GitHub repository. ## Command ``` /skill repo-to-skill <github-repo-url> ``` Example: ``` /skill repo-to-skill https://github.com/vllm-project/vllm ``` ## Overview Given a GitHub repo URL, this skill: 1. Clones and analyzes the repository 2. Extracts usage patterns from README, docs, examples, CLI help 3. Generates a working skill (SKILL.md + resources) 4. Tests the skill by running basic operations 5. Evaluates the skill with test prompts and assertions ## Process ### Step 1: Clone & Analyze ```bash # Clone repo (shallow for speed) git clone --depth 1 <repo-url> /tmp/repo-to-skill/<repo-name> ``` Analyze in this order (stop when you have enough): 1. **README.md** — primary source for installation, quickstart, features 2. **docs/** or **documentation/** — detailed usage guides 3. **examples/** — concrete usage patterns (high value) 4. **CLI help** — if it's a CLI tool, check `--help` output 5. **setup.py / pyproject.toml / package.json** — dependencies and entry points 6. **Source code** — only if docs are insufficient; focus on public API Extract: - **What it does** (one sentence) - **Installation method** (pip, npm, cargo, etc.) - **Core commands/API** (the 5-10 most common operations) - **Configuration** (env vars, config files, required setup) - **Input/Output formats** (what goes in, what comes out) - **Common patterns** (from examples/ or README)
Details
- Skill name
repo-to-skill- Repository
- shuyhere/repo-to-skill
- License
- MIT
- Repo updated
- 13 March 2026
FAQ
What does the Repo to Skill skill do?
Generate an agent skill from a GitHub open-source repository. Use when asked to create a skill from a repo URL, turn a GitHub project into a usable skill, or generate skill files for a CLI/library/framework. Triggers on phrases like "create a skill from this repo", "make a skill for vllm", "turn this GitHub project into a skill", "generate a skill from repo". Also use when asked to "skillify" a tool or generate usage instructions from source code. Command usage — `/skill repo-to-skill <github-repo-url>`.
How do I install the Repo to Skill skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add shuyhere/repo-to-skill --skill repo-to-skill. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Repo to Skill popular?
It lives in shuyhere/repo-to-skill, which has 19 GitHub stars and 1 forks.
Related skills
Github Demand Radar
16geekjourneyx/github-demand-radar
Use when the user asks to analyze a GitHub repository's issues/PRs to identify high-value commercial demand opportunities. Triggers: 「扫issue」「扫PR」「找需求」「分析仓库」「找商业化点子」「独立开发者切入点」「需求雷达」「扫一下明星项目」「生成需求报告」. Outputs scored demand cards with JTBD analysis, RICE scoring, Ugly Workaround evidence, and fake-door probe drafts. Also works in PR scan mode (Phase 1B) to find rejected/stale PRs as market gap signals.
Github Stars Curator
22Leexunhuan743/github-stars-curator
Organize starred GitHub repos into stable, clear lists: detect new stars, download READMEs into a local corpus, classify each repo against the taxonomy, and sync the approved mapping back to GitHub via gh. Use this when a user wants their starred repos sorted into lists, a recent batch of new stars filed incrementally, or their star-list taxonomy reviewed and refined. Do not use for general GitHub issue/PR management, repo code search, or bookmarking non-GitHub resources.
Address PR Review
15mnapoli/skill-address-pr-review
Look at the pull request review comments and address any issues raised.
Oss Launch
16AnayDhawan/oss-launch
Use when taking a repo open source, or hardening one that already is. Run /oss-launch and it scans the repo (stack, existing files, git remote, secrets), asks only what it cannot infer, then generates a tailored OSS file collection (README, LICENSE, CONTRIBUTING, CODE_OF_CONDUCT, SECURITY, CHANGELOG, .gitignore, .github/ issue + PR templates, CI/CD). Also covers launch (GitHub metadata, badges, Show HN, Reddit, YouTube), release cadence (SemVer + CHANGELOG), and demo-GIF generation. Triggers on "open source this", "OSS checklist", "prep for launch", "make this repo public", "add a license / co
Build It
16DevOtts/build-it
Autonomous goal-to-DoD delivery orchestrator — the build stage of the *-it lifecycle ("plan-it plans it, build-it builds it"); formerly named fable-it. Hand it a goal and a numbered Definition of Done and it runs the whole job to completion, typically unattended, enforcing checkable gates (turn-end, claim, state-change, phase-boundary, delegation, and safe-parallel: interlock, worktree, integration), disk-backed run state, an evidence ledger that makes VERIFIED a lookup, a fresh-eyes verification pass, and an honest per-criterion report. Model-adaptive for Sonnet 5 and Opus 4.8; host-agnostic
Remote Computer
22paoloanzn/remote-computer
Configure and provision a remote development VM on AWS EC2 or Google Cloud Compute Engine, or a local SSH-ready Linux development container with apple/container on an Apple silicon Mac. Verify provider context, size the machine (host-aware container resource suggestions and Dockerfile configurations saved under ~/Documents/Containers), create dedicated VM-access SSH keys, optionally discover and port local Git/GitHub/GPG configuration with shared GitHub authentication keys, maintain the ~/.vms.json live-VM registry, reconcile status, and prepare direct SSH access. Use when a user asks to creat
Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.