Skip to main content
The Skills CLI supports multiple source formats for installing skills, from GitHub shorthand to local directories. Understanding these formats helps you install skills from anywhere.

Supported Formats

The CLI automatically detects the source type and handles installation appropriately.

GitHub Shorthand

The simplest way to install skills from GitHub:
The owner/repo format is automatically expanded to https://github.com/owner/repo.git

Full GitHub URLs

You can also use complete GitHub URLs:

GitLab URLs

Full support for GitLab repositories, including subgroups:
GitLab URLs use the /-/tree/ pattern which is unique to GitLab. The CLI automatically detects this.

Git URLs

Any valid git URL is supported:

Local Paths

Install skills from your local filesystem:
Local paths must start with ./, ../, /, or be absolute (e.g., C:\ on Windows). This prevents ambiguity with GitHub shorthand.

Source Detection Logic

The CLI parses sources in this order:
  1. Local paths - Absolute or relative paths (., .., ./, /, C:\)
  2. GitHub URLs with paths - github.com/owner/repo/tree/branch/path
  3. GitHub URLs with branch - github.com/owner/repo/tree/branch
  4. GitHub repository URLs - github.com/owner/repo
  5. GitLab URLs with paths - gitlab.com/org/repo/-/tree/branch/path
  6. GitLab URLs with branch - gitlab.com/org/repo/-/tree/branch
  7. GitLab repository URLs - gitlab.com/org/repo
  8. GitHub shorthand with skill filter - owner/repo@skill-name
  9. GitHub shorthand with path - owner/repo/path/to/skill
  10. GitHub shorthand - owner/repo
  11. Well-known endpoints - HTTP(S) URLs with /.well-known/skills/index.json
  12. Direct git URLs - Any other git-compatible URL

Special Formats

Installing Specific Skills

You can filter which skills to install using the @skill-name syntax or --skill flag:

Branches and Refs

Install from specific branches or tags:
For GitHub shorthand (owner/repo), the default branch is used automatically.

Subpaths

Install skills from a subdirectory within a repository:
When a subpath is provided, the CLI searches for skills starting from that directory.

Source Aliases

Some commonly used repositories have aliases: More aliases may be added in future releases.

Listing Available Skills

Before installing, preview available skills from a source:
This displays all discoverable skills without installing them.

Private Repositories

For private repositories, ensure you have git credentials configured:

SSH Authentication

HTTPS with Credentials

Configure git credentials helper:
The CLI uses git to clone repositories. Make sure you have read access to the repository with your configured git credentials.

Examples by Use Case

Troubleshooting

Ensure the repository contains valid SKILL.md files with name and description in the frontmatter. Check that skills are in recognized directories.
For private repositories:
  • Verify your SSH keys are configured: ssh -T git@github.com
  • Or use HTTPS with credentials helper configured
  • Check that you have read access to the repository
If the CLI misinterprets your input:
  • Use explicit URLs instead of shorthand
  • For local paths, always start with ./ or use absolute paths
  • Check for typos in owner/repo names

Next Steps

Creating Skills

Learn how to create your own skills

Installation Methods

Understand symlink vs copy installation