skillmux is a high-performance CLI for managing Skills across multiple remote sources and multiple local runtime targets.
- What is skillmux
- Core Capabilities
- Installation
- Command Overview
- Configuration
- Source Resolution Rules
- Install Targets
- Examples
- Troubleshooting
- Development
- License
Modern agent runtimes often need skills from different ecosystems (official registries, internal hubs, GitHub repos), and they may store those skills in different local folders.
skillmux solves this by providing:
- One unified CLI for search / install / list / update / remove.
- Multiple source backends in one tool.
- Multiple target layouts for different agent products.
- Reproducible metadata tracking for installed skills.
- Search skills from configured source providers.
- Built-in source adapters include:
kingdeeclawhub
- Rich search output includes:
- slug
- version
- description
Install from:
- Named skill slug from configured source.
- GitHub shorthand:
gh:owner/repogithub:owner/repo
- Full GitHub repository URL.
Optional install controls:
--versionto pin a version when source supports versioning.--refto install from a specific git ref.--subdirto install from a repository subdirectory.--asto rename the local installed folder.--forceto overwrite/refresh existing content.--jsonfor machine-readable output.
For registry sources, the local folder name defaults to the skill slug. Display names from SKILL.md are saved as metadata, which avoids duplicate installs when a skill has a localized display name.
skillmux list shows installed skills with metadata such as:
- target
- local skill name
- source
- version
- description
- Update one installed skill by name.
- Update all installed skills with
--allor with no update argument. - Shows per-skill
installed/updated/unchangedstatus instead of repeated install logs. - Keeps source information to make update behavior deterministic.
- Remove a skill from managed targets.
- Optional purge mode for deeper cleanup.
Supports target-specific install layouts, including:
codexqoderqoderworkkiroworkbuddy
pip install skillmuxskillmux --versionskillmux search <keyword> [--limit <n>] [--page <n>] [--json]skillmux install <skill_or_repo>
[--version <version>]
[--ref <git-ref>]
[--subdir <path>]
[--as <name>]
[-y|--yes]
[--force]
[--json]skillmux list [--json]skillmux update [skill]
skillmux update --all [--ref <git-ref>]skillmux remove <skill> [--purge]skillmux config list
skillmux config get <key>
skillmux config set <key> <value>
skillmux config targets <target1,target2,...>
skillmux config targets set <target1,target2,...>
skillmux config targets add <target1,target2,...>
skillmux config targets remove <target1,target2,...>skillmux reads settings from config and command-line overrides.
Common configuration dimensions:
- API endpoint and timeout.
- Default source.
- Install targets.
- Token resolution strategy.
CLI-level override flags:
--config <path>: use a specific config file.--api <url>: override API endpoint.--token <token>: provide token for the current run.--source <name>: override default source.
When installing:
- If input looks like GitHub shorthand/URL, it is handled by GitHub flow.
- Otherwise it is resolved through the currently selected source backend.
- Source metadata is persisted for future updates.
This design allows predictable updates even when multiple sources may contain similarly named skills.
Each target maps to a specific local directory layout.
Why this matters:
- Different agent products discover skills in different paths.
skillmuxnormalizes install/update/remove operations across these paths.
Recommended workflow:
- Configure the target list once.
- Install skills normally.
- Use
listandupdate --allfor routine maintenance.
skillmux search pdf
skillmux install pdf-processing
skillmux list
skillmux update --all
skillmux remove pdf-processingskillmux install gh:owner/repo
skillmux install https://github.com/owner/reposkillmux install gh:owner/repo --ref v1.2.3 --subdir skills/my-skill --as my-skillskillmux search retrieval --json
skillmux list --json- Confirm source selection (
--sourceor config default). - Retry with a broader search keyword.
- Check whether the original source is still reachable.
- If source changed, remove and reinstall from desired source.
- Verify configured targets:
skillmux config get install.targets
cargo buildcargo fmt
cargo checkThe release helper keeps Cargo.toml and pyproject.toml in sync, commits the version bump, creates an annotated tag, pushes the branch and tag, then creates a GitHub release with generated notes.
Interactive:
python scripts/release.pyNon-interactive:
python scripts/release.py patch --yes
python scripts/release.py major --yesPowerShell:
.\scripts\release.cmd patch --yesUse --dry-run to preview the release. The script requires a clean git worktree, git, and an authenticated GitHub CLI (gh auth status).
The publish GitHub Actions workflow runs when a GitHub Release is published. It builds PyPI wheels and standalone CLI binaries for:
x86_64-unknown-linux-gnuaarch64-unknown-linux-gnux86_64-pc-windows-msvcaarch64-pc-windows-msvcx86_64-apple-darwinaarch64-apple-darwin
The workflow uploads the standalone CLI binaries plus SHA256SUMS.txt to the same GitHub Release, publishes wheels to PyPI, and can update Homebrew, WinGet, and Launchpad PPA when the related secrets and variables are configured. See packaging/homebrew, packaging/winget, and packaging/ppa for the required CI configuration.
Released under the terms of the repository license.
