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.gitFull 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:Source Detection Logic
The CLI parses sources in this order:- Local paths - Absolute or relative paths (
.,..,./,/,C:\) - GitHub URLs with paths -
github.com/owner/repo/tree/branch/path - GitHub URLs with branch -
github.com/owner/repo/tree/branch - GitHub repository URLs -
github.com/owner/repo - GitLab URLs with paths -
gitlab.com/org/repo/-/tree/branch/path - GitLab URLs with branch -
gitlab.com/org/repo/-/tree/branch - GitLab repository URLs -
gitlab.com/org/repo - GitHub shorthand with skill filter -
owner/repo@skill-name - GitHub shorthand with path -
owner/repo/path/to/skill - GitHub shorthand -
owner/repo - Well-known endpoints - HTTP(S) URLs with
/.well-known/skills/index.json - 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:Source Aliases
Some commonly used repositories have aliases:| Alias | Expands to |
|---|---|
coinbase/agentWallet | coinbase/agentic-wallet-skills |
Listing Available Skills
Before installing, preview available skills from a source:Private Repositories
For private repositories, ensure you have git credentials configured:SSH Authentication
HTTPS with Credentials
Configure git credentials helper:Examples by Use Case
Installing from a monorepo
Installing from a monorepo
Testing local skills before publishing
Testing local skills before publishing
Installing from self-hosted git
Installing from self-hosted git
Installing from a fork
Installing from a fork
Troubleshooting
No skills found
No skills found
Ensure the repository contains valid
SKILL.md files with name and description in the frontmatter. Check that skills are in recognized directories.Git authentication failed
Git authentication failed
For private repositories:
- Verify your SSH keys are configured:
ssh -T [email protected] - Or use HTTPS with credentials helper configured
- Check that you have read access to the repository
Ambiguous source format
Ambiguous source format
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