skill-installer

Install Codex skills into $CODEX_HOME/skills from a curated list or a GitHub repo path. Use when a user asks to list installable skills, install a curated skill, or install a skill from another repo (including private repos).

22,826stars1,553forksUpdated 6/25/2026

Git & Version Control Productivity & Workflow #codex #skills #github #installer #automation

Security Assessment

Safe(100/100)

Security Score100/100

About skill-installer

Installs Codex skills into $CODEX_HOME/skills from a curated list or from an arbitrary GitHub repo path, including private repositories. By default skills come from the openai/skills repository's skills/.curated directory, but users can point at other locations. It is used when someone asks to list installable skills, install a curated skill by name, or install a skill from another repo. The work is performed through helper scripts rather than ad hoc commands, and because every script uses the network, escalation should be requested when running them in a sandbox.

Three helper scripts drive the behavior. scripts/list-skills.py prints the available skills with annotations marking which are already installed, accepts a --format json option, and can target other directories such as skills/.experimental via --path. scripts/install-skill-from-github.py installs by --repo with one or more --path values, or by a full --url to a tree path. Listing is done when the user asks what is available or invokes the skill without specifying an action, defaulting to .curated but switching to .experimental and labeling the source accordingly when experimental skills are requested.

Installation behavior is well defined: it defaults to direct download for public GitHub repos and falls back to git sparse checkout if download fails with auth or permission errors, trying HTTPS first then SSH. It aborts if the destination skill directory already exists, installs into $CODEX_HOME/skills/<skill-name> (defaulting to ~/.codex/skills), and supports multiple --path values to install several skills in one run, each named from the path basename unless --name is supplied. Options include --ref (default main), --dest, and --method auto, download, or git. Private repos can be accessed via existing git credentials or an optional GITHUB_TOKEN or GH_TOKEN. The curated listing is fetched via the GitHub API, and the skills under skills/.system are preinstalled so users do not need help installing them. After an install, the user is told the skill will be available on their next turn.

FAQ

Where are skills installed?

Into $CODEX_HOME/skills/<skill-name>, which defaults to ~/.codex/skills. The destination can be overridden with --dest, and installation aborts if the target skill directory already exists.

Can it install skills from private GitHub repositories?

Yes. Private repos can be accessed via existing git credentials or an optional GITHUB_TOKEN or GH_TOKEN. If direct download fails with auth or permission errors, it falls back to a git sparse checkout, trying HTTPS first and then SSH.

How do I see which skills are available?

Run scripts/list-skills.py, which prints the list with annotations showing which are already installed. It defaults to .curated and can target skills/.experimental with --path, and supports --format json.

Can multiple skills be installed in one run?

Yes. install-skill-from-github.py accepts multiple --path values and installs each in a single run, naming each from the path basename unless --name is supplied.

Do I need to install the .system skills?

No. The skills under skills/.system are preinstalled, so there is no need to help users install them. If a user insists, they can be downloaded and overwritten.