How to install skills from GitHub

Claude Code can install skill bundles straight from a GitHub repository. This guide walks through the full flow end-to-end using the real bundles published in this marketplace.

Prerequisites

• A working Claude Code installation. If you have not set it up, see the Claude Code docs.
• Network access to github.com. Private repos additionally need gh auth login or a GitHub personal access token configured for Claude Code.
• Read what agent skills are first if the terminology is unfamiliar.

Step 1. Register the marketplace

Tell Claude Code where to find skill bundles. Either command below works — the first references this GitHub repository directly, the second loads the published catalog JSON:

/plugin marketplace add alisonaquinas/llm-skills

/plugin marketplace add https://llm-skills.alisonaquinas.com/marketplace.json

Claude Code stores the marketplace reference in its configuration. You only do this once per machine, not once per bundle.

Step 2. Install a bundle

Once the marketplace is registered, install any bundle by name. For example, to install the Shared Skills bundle:

/plugin install shared-skills@llm-skills

Or the CI/CD bundle:

/plugin install ci-cd@llm-skills

The syntax is /plugin install <pluginName>@llm-skills. You can find the exact install command on every bundle page — there are 5 bundles total. See the home page for the full list.

Step 3. What happens after install

Claude Code downloads the bundle at the version pinned in the marketplace (every bundle on this site is tagged — the catalog records the exact ref), unpacks it into your Claude Code plugin directory, and loads every skill inside the bundle into the trigger table. The next time you start a conversation, the agent sees each skill's trigger description. When your request matches, Claude Code pulls the skill into context automatically — you do not normally call skills by name.

Updating an installed bundle

Bundles are versioned. When a new release is published, re-run /plugin install with the same identifier — Claude Code will fetch the latest pinned version from the marketplace and replace the installed copy. You can also refresh the marketplace first with /plugin marketplace update to pull the newest catalog entries before installing.

Uninstalling a bundle

Remove a bundle with /plugin uninstall <pluginName>@llm-skills. That removes the bundle from Claude Code's plugin directory and drops all skills it contained from the trigger table in new sessions.

Troubleshooting

• GitHub rate limits. Unauthenticated GitHub API calls cap out at 60 requests per hour. If install fails with a rate-limit error, authenticate with gh auth login or export a GITHUB_TOKEN in your environment before retrying.
• Private repositories. If you are installing from a private fork of this marketplace, make sure your GitHub token has repo scope and that Claude Code is configured to use it. Public installs do not need auth at all.
• Unknown plugin name. The pluginName must match exactly. Copy the command from the bundle's page rather than typing it — the slugs are lowercase and hyphenated (for example ci-cd, not ci_cd).
• Version mismatch. If a release tag referenced in the catalog has been deleted, the install will 404. Run /plugin marketplace update to pull the latest catalog and try again.
• Skills not triggering. After install, start a fresh conversation. Skills loaded mid-session are not always picked up until the next session begins.

Where to go next

• Browse the full skill catalog to see what each bundle ships.
• See the best CI/CD skills guide for curated recommendations from the ci-cd bundle.
• Read the Claude Code vs Codex comparison if you are evaluating both platforms.
• Official: docs.claude.com for the plugin system reference.