Skills chill-institute
Use chill.institute (web UI) to search for content and click “send to put.io” (best paired with the putio skill) — set sail, pick the best 1080p/x265 loot, and ship it.
install
source · Clone the upstream repo
git clone https://github.com/openclaw/skills
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/baanish/chill-institute" ~/.claude/skills/openclaw-skills-chill-institute && rm -rf "$T"
OpenClaw · Install into ~/.openclaw/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/openclaw/skills "$T" && mkdir -p ~/.openclaw/skills && cp -r "$T/skills/baanish/chill-institute" ~/.openclaw/skills/openclaw-skills-chill-institute && rm -rf "$T"
manifest:
skills/baanish/chill-institute/SKILL.mdsource content
chill.institute
Use chill.institute via an interactive browser session to find an item and send it to put.io.
If you have both skills installed (chill-institute + putio), the workflow is much smoother: chill.institute launches the transfer, and putio verifies/monitors it from the CLI.
Prereqs
- User must be logged in to chill.institute (put.io OAuth in the browser).
- The
skill should be available to verify the transfer in put.io.putio
End-to-end workflow
- Open the site:
- Start at:
https://chill.institute/sign-in
- Start at:
- If prompted, click authenticate at put.io and ask the USER to complete login.
- Search for the title (include season/quality keywords if relevant).
- Use quick filters (e.g. check 1080p, x265) if available.
- Pick the best result (prefer healthy seeders, reasonable size, and expected naming).
- Click send to put.io.
- Confirm it changed to see in put.io.
- Verify on put.io:
bash skills/putio/scripts/list_transfers.sh
Browser automation notes
- Prefer
tool with the isolated profile (browser
).profile="clawd" - If clicks time out, re-snapshot (
) and retry on the new ref.refs="aria"
Safety / policy
- Don’t ask users for their put.io password in chat.
- Don’t scrape or store cookies/session tokens in files.
- Only use this workflow for content the user has rights/permission to access.