StrawHub CLI
Command-line client for StrawHub, the public registry for StrawPot agents.
Discover, install, publish, and manage reusable skills, roles, agents, memories, and integrations — with recursive dependency resolution.
Installation
pip install strawhub
Quick Start
# Search for skills, roles, agents, and memories
strawhub search "code review"
# Install a skill (dependencies resolved automatically)
strawhub install skill code-review
# Install a role
strawhub install role implementer
# Save dependencies to strawpot.toml
strawhub install skill code-review --save
# Install all dependencies from strawpot.toml
strawhub install
# Authenticate for publishing
strawhub login
Project File (strawpot.toml)
Declare your project's skill and role dependencies in a strawpot.toml file at the project root:
[skills]
git-workflow = "*"
code-review = "==2.1.0"
[roles]
implementer = "*"
Run strawhub install to install everything. Teammates can clone the repo and run the same command to get an identical setup.
Version constraints: "*" (latest), "==X.Y.Z" (exact).
See the project file documentation for full details.
Commands
Package Management
| Command | Description |
|---|---|
install |
Install all dependencies from strawpot.toml |
install skill|role|agent|memory <slug> |
Install a specific package |
install skill|role|agent|memory <slug> --save |
Install and save to strawpot.toml (*) |
install skill|role|agent|memory <slug> --save-exact |
Install and save to strawpot.toml (==X.Y.Z) |
install skill|role|agent|memory <slug> --version X.Y.Z |
Install a specific version |
uninstall skill|role|agent|memory <slug> |
Uninstall a package |
uninstall skill|role|agent|memory <slug> --save |
Uninstall and remove from strawpot.toml |
update skill|role|agent|memory <slug> |
Update to the latest version |
update --all |
Update all installed packages |
update --all --save |
Update all and save new versions to strawpot.toml |
init |
Create strawpot.toml from currently installed packages |
install-tools |
Install system tools declared by installed packages |
install integration <slug> |
Install an integration (always global) |
uninstall integration <slug> |
Uninstall an integration |
update integration <slug> |
Update an integration |
Discovery
| Command | Description |
|---|---|
search <query> |
Search for skills, roles, agents, and memories |
info skill|role|agent|memory <slug> |
Show detail for a skill, role, agent, or memory |
list |
List all available skills, roles, agents, and memories |
star skill|role|agent|memory <slug> |
Star a skill, role, agent, or memory |
unstar skill|role|agent|memory <slug> |
Unstar a skill, role, agent, or memory |
Publishing
| Command | Description |
|---|---|
publish skill|role|agent|memory <path> |
Publish to the registry |
Runtime
| Command | Description |
|---|---|
resolve skill|role <slug> |
Resolve and print package paths (JSON) |
Authentication
| Command | Description |
|---|---|
login |
Authenticate with StrawHub |
logout |
Remove stored credentials |
whoami |
Show current user info |
Most commands support --json for machine-readable output. See the full CLI reference for detailed documentation of every command and option.
Install Options
The install command supports several flags for controlling behavior:
| Option | Description |
|---|---|
--global |
Install to global directory (~/.strawpot) |
--version X.Y.Z |
Install a specific version |
--force |
Force replace existing installation (requires --version) |
--update |
Update to latest if already installed |
--recursive |
Also update dependencies (requires --update) |
--save |
Save to strawpot.toml with * |
--save-exact |
Save to strawpot.toml with ==X.Y.Z |
--skip-tools |
Skip system tool installation |
--yes, -y |
Auto-confirm tool install prompts |
Configuration
| Variable | Description | Default |
|---|---|---|
STRAWHUB_API_URL |
Override the API endpoint | https://strawhub.dev |
STRAWHUB_TOKEN |
Override the auth token | (from strawhub login) |
STRAWPOT_HOME |
Override the global install directory | ~/.strawpot |
Settings can also be persisted in ~/.config/strawhub/config.json.
Links
- Registry: https://strawhub.dev
- Source: https://github.com/strawpot/strawhub
Metadata
Release files for strawhub 0.1.54
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| strawhub-0.1.54.tar.gz | 54.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| strawhub-0.1.54-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 102.2 kB
Release files / strawhub-0.1.54.tar.gz
| Download URL | strawhub-0.1.54.tar.gz |
|---|---|
| Size | 54.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1f3f0c936ce76a989b9e0b455bf23b2b85ed83a3daaf74199b852e6d618203d2
|
|
BLAKE2b-256 checksum How to use checksums |
36ce993c35314ef7c9fc5ac279790b50b52ca12891dd2f89a72f04a6ae1b309c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 29, 2026.
Transparency logRelease files / strawhub-0.1.54-py3-none-any.whl
| Download URL | strawhub-0.1.54-py3-none-any.whl |
|---|---|
| Size | 47.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5240855ce759020efb3eef832fdaadd52b7ec9f7ba808fc5c33b927d96c570e3
|
|
BLAKE2b-256 checksum How to use checksums |
d4e61cbd00712a103e7d91898a6548c0a7c7400fe17e0b20f6a45b4e48de6798
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Mar 29, 2026.
Transparency log