360 Secure SkillHub
360 安全技能中心

put.io (kaput CLI)

该技能通过非官方 kaput CLI 操作 put.io 账户:先用 cargo 安装 kaput-cli、经设备码流程登录,再用自带脚本列出转存任务、添加磁力/种子/直链、搜索文件、查看状态与授权检查;可与 chill-institute 技能配合,先发起转存再验证是否到达。

baanish
baanish
热度 78.43
最近更新 2026-05-11 15:50:48
分类:自动化依赖:代码执行 / 第三方 API应用场景:自动化脚本 / 工作流 / 任务管理

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add putio
Metadata
name
putio
description
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.

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:
    cargo install kaput-cli
    
  • Ensure kaput is on your PATH (typically ~/.cargo/bin).

Authenticate (device-code flow)

  1. Run:
    kaput login
    
  2. It prints a link + short code (e.g. https://put.io/link + ABC123).
  3. User enters the code in the browser.
  4. 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:

    bash skills/putio/scripts/list_transfers.sh
    
  • Add a transfer (magnet / torrent URL / direct URL):

    bash skills/putio/scripts/add_transfer.sh "magnet:?xt=urn:btih:..."
    
  • Search files:

    bash skills/putio/scripts/search_files.sh "query"
    
  • Status (transfers; optionally account):

    bash 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 login device-code flow.
  • kaput stores credentials locally (token file). Treat it as sensitive and avoid sharing it.
  • Avoid running kaput debug in shared logs/screenshots (may reveal local config details).