# Github Installer

> Classify and install GitHub repos correctly. Use when the user pastes a GitHub URL or asks to install, add, clone, or use a repo. Distinguishes between plugins, skills, MCP servers, and standalone tools.

- Skill: `enc0ding/github-installer` (Agent Skill)
- Install (CLI): `npx skillmds@latest add enc0ding/github-installer`
- Raw SKILL.md: https://api.skillmd.com/api/skills/enc0ding/github-installer/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: enc0ding (https://skillmd.com/u/enc0ding)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/enc0ding/github-installer

---


# GitHub Repo Installation Skill

When a GitHub URL is pasted, follow this process. Do NOT install before classifying.

## Step 1 — Clone and classify

Clone the repo to `/tmp/` (or `$env:TEMP` on Windows) and inspect the structure:

- **`SKILL.md` at the root** → it's a skill
- **`.claude-plugin/plugin.json`** → it's a plugin
- **`package.json` with an MCP server entry point** (look for `mcp`, `bin`, or server config) → it's an MCP server
- **None of the above** → standalone tool, framework, or app

## Step 2 — Handle by type

### Skill
Copy the entire skill directory to `.claude/skills/[skill-name]/`. The directory name should match the `name` field in the skill's frontmatter.

### Plugin
Use the plugin marketplace if it's listed:
```
/plugin install [name]@[marketplace]
/reload-plugins
```
If not on a marketplace, the user must add it as a custom plugin source.

### MCP Server
Add the server to `.claude/settings.json` under a `mcpServers` key. Format depends on the server — read its README.

### Standalone Tool
Don't install into `.claude/`. Clone it to the project root or a sibling directory, depending on what makes sense.

## Rules

- NEVER install before classifying
- NEVER dump an entire repo into `.claude/skills/`
- Verify the install worked by checking for the expected files
- If anything is ambiguous, ask the user before proceeding