Agent skill
putio
Manage a put.io account via the kaput CLI (transfers, files, search) — hoist the mainsail, add magnets/URLs, and check transfer status; best paired with the chill-institute skill.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/putio-moltbot-skills
SKILL.md
put.io (kaput CLI)
This skill uses the unofficial kaput CLI to operate put.io from the command line.
If you also have the chill-institute skill installed, you can:
- use chill.institute to start a transfer (“send to put.io”), then
- use this skill to verify and monitor that the cargo is actually arriving.
Install
- Requires Rust + Cargo.
- Install:
bash
cargo install kaput-cli - Ensure
kaputis on your PATH (typically~/.cargo/bin).
Authenticate (device-code flow)
- Run:
bash
kaput login - It prints a link + short code (e.g.
https://put.io/link+ABC123). - User enters the code in the browser.
- The CLI completes and stores a token locally.
Check auth:
bash skills/putio/scripts/check_auth.sh
Common actions (scripts)
All scripts auto-locate kaput (supports KAPUT_BIN=/path/to/kaput).
-
List transfers:
bashbash skills/putio/scripts/list_transfers.sh -
Add a transfer (magnet / torrent URL / direct URL):
bashbash skills/putio/scripts/add_transfer.sh "magnet:?xt=urn:btih:..." -
Search files:
bashbash skills/putio/scripts/search_files.sh "query" -
Status (transfers; optionally account):
bashbash skills/putio/scripts/status.sh SHOW_ACCOUNT=1 bash skills/putio/scripts/status.sh
Raw CLI
For advanced actions:
kaput --help
kaput transfers --help
kaput files --help
Security notes
- Do not paste passwords into chat. Use
kaput logindevice-code flow. - kaput stores credentials locally (token file). Treat it as sensitive and avoid sharing it.
- Avoid running
kaput debugin shared logs/screenshots (may reveal local config details).
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?