bms-skills-cli
A minimal, user-friendly Python CLI to manage agent skills from GitHub releases or branches. It installs skills to both ~/.agents/skills and ~/.claude/skills for seamless integration across platforms.
Features
- Interactive Installation: Select specific skills to add from any GitHub repository.
- Multi-Repo Support: Manage skills from multiple repositories independently.
- Lock File State: Tracks installed sources (release tags or branches), pinned commit SHAs, and skills in
~/.agents/skills.lock.jsonfor reproducibility. - Automated Updates: Easily upgrade all or specific repositories to their latest GitHub release or tracked branch head.
- Smart Caching: Downloads are cached in a temporary directory (
TEMPor/tmp) to avoid redundant network usage. Can be overridden withBMS_SKILL_CACHE_DIR. - GitHub CLI Integration: Uses the
ghtool for fast downloads if available, with a reliablerequestsfallback.
Installation
Install using pip or uv:
pip install bms-skills-cli
# or
uv tool install bms-skills-cli
Usage
1. Add Skills
Interactively select skills to add from a GitHub repository's latest release:
bms-skills add google/gemini-cli-skills
If a repository has no releases, the CLI automatically falls back to the main branch. You can also install directly from a branch:
bms-skills add anthropics/skills --branch main --skill pdf
2. Remove Skills
Interactively select installed skills to remove from your system:
bms-skills remove
3. Update Skills
Update all installed skills to their latest tracked versions:
bms-skills update
Or update a specific repository:
bms-skills update --repo google/gemini-cli-skills
4. Sync Skills
Install all skills as defined in the lock file using the pinned commit SHAs (useful for setting up a new machine):
bms-skills sync
Skill Definition
A folder is recognized as a valid skill if it resides within a skills/ directory at the repository root and contains a SKILL.md file.
Development
This project uses uv for dependency management.
# Install dependencies
uv sync
# Run locally
uv run bms-skills --help
# Run tests
uv run pytest
# Type check
uv run pyright bms_skills
License
MIT
Metadata
Release files for bms-skills-cli 0.3.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| bms_skills_cli-0.3.1.tar.gz | 26.1 kB | With provenance | Details for bms_skills_cli-0.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bms_skills_cli-0.3.1-py3-none-any.whl | Python 3 | none | any | Details for bms_skills_cli-0.3.1-py3-none-any.whl |
Total release size: 34.7 kB
Release files / bms_skills_cli-0.3.1.tar.gz
| Download URL | bms_skills_cli-0.3.1.tar.gz |
|---|---|
| Size | 26.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
527b32f1c20c89abc8b877f32f2d630eb5ea612ddd1e820a9ee9af644eeddc5d
|
|
BLAKE2b-256 checksum How to use checksums |
7cbbc66e0f0f4077150810f3636e7375219abb111068e380a376cd63b16d401f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 29, 2026.
Transparency logRelease files / bms_skills_cli-0.3.1-py3-none-any.whl
| Download URL | bms_skills_cli-0.3.1-py3-none-any.whl |
|---|---|
| Size | 8.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c28d512c989705c2d09298dfac748b0bc7654e8bee7bbf20c27ec5da039521f0
|
|
BLAKE2b-256 checksum How to use checksums |
ce5a300e72b324b5dbe4802c17144ffbc6a351bae261a3654d2b0d63e8d0ce53
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 29, 2026.
Transparency logSecurity for bms-skills-cli 0.3.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for bms_skills_cli-0.3.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 29, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.