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.

Security Scan

The skill is an instruction-only helper for using the chill.institute web UI to send items to put.io; its requirements and instructions are coherent and proportional to that purpose.

Purpose & Capability

The name/description match the SKILL.md: it directs interactive browser use of chill.institute and handing transfers to put.io. It requests no environment variables, binaries, or installs, which is appropriate for a purely browser-driven workflow. The dependency on the putio skill for verification is logical and expected.

Instruction Scope

Instructions stay focused on opening the site, having the user complete put.io OAuth in the browser, selecting results, and clicking 'send to put.io'. They also ask the agent to verify transfers by running a putio skill script (bash skills/putio/scripts/list_transfers.sh). This is reasonable, but the script path implies executing a local script from the putio skill — the user should confirm that script's contents before allowing execution.

Install Mechanism

There is no install spec and no code files beyond SKILL.md, so nothing will be written to disk by an installer. This is the lowest-risk form.

Credentials

No environment variables or credentials are requested by the skill. Authentication is expected to occur via the browser-based put.io OAuth flow, which is appropriate and keeps secrets out of chat/skill configuration.

Persistence & Privilege

always:false and default invocation settings are used. The skill does not request persistent system configuration changes or access to other skills' config. It only advises using the browser tool with an isolated profile, which is appropriate for this use.

Assessment

This is an instruction-only skill that automates browser interactions with chill.institute and relies on put.io for transfer verification. Before using it: (1) confirm you are comfortable performing put.io OAuth in the browser (the skill correctly says not to ask for passwords in chat); (2) inspect the putio skill's scripts (e.g., skills/putio/scripts/list_transfers.sh) so you know what will be executed locally; (3) run the browser automation with an isolated profile as suggested to avoid exposing unrelated cookies/sessions; and (4) only use this workflow for content you have rights to access. If you haven't installed the putio skill, verification steps that run local scripts may fail or run unexpected code — install/inspect that skill first.

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 putio skill should be available to verify the transfer in put.io.

End-to-end workflow

1. Open the site:
   • Start at: https://chill.institute/sign-in
2. If prompted, click authenticate at put.io and ask the USER to complete login.
3. Search for the title (include season/quality keywords if relevant).
4. Use quick filters (e.g. check 1080p, x265) if available.
5. Pick the best result (prefer healthy seeders, reasonable size, and expected naming).
6. Click send to put.io.
7. Confirm it changed to see in put.io.
8. Verify on put.io:

   bash skills/putio/scripts/list_transfers.sh
   

Browser automation notes

• Prefer browser tool with the isolated profile (profile="clawd").
• If clicks time out, re-snapshot (refs="aria") and retry on the new ref.

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.