Quark Drive automation (夸克网盘)

Hard constraints (must follow)

• - Remote allowlist: Only operate under remote path prefix(es) configured in references/config.json (or fallback references/config.example.json). Default allowlist should be /OpenClaw/**.
• Local allowlist: Only read/upload from local path prefix(es) configured. Do not read arbitrary local paths.
• Destructive operations need confirmation by default: delete / move / rename / copy / purge.
• If Quark triggers captcha / risk control, stop and ask the user to take over in a real browser.

Privacy & safety (publishable skill defaults)

• - Treat these files as sensitive (never commit, never paste their contents):

- references/session_api.json, references/cookies.json, references/login_token.json, references/qr_code.png - (If enabled) references/index.json (may contain private filenames/paths)

• - Do not print cookies, auth headers, or full raw responses unless user explicitly requests debug.
• When sharing the skill, keep examples generic (no usernames, absolute paths, chat_id, or personal tokens).

Runtime / dependencies

• - Runtime: system Python (this repo does not bundle a venv).
• Dependencies are expected to be installed by the host (often via OS packages). requirements.txt exists for portability/reference.

Config

• - Preferred: INLINECODE9
• Fallback: INLINECODE10

Key fields (example names; see config.example.json):

• - remoteAllowlist: e.g. INLINECODE13
• INLINECODE14: e.g. INLINECODE15
• INLINECODE16

Login workflow (QR)

Terminal (local)

1) Run login-prepare to generate QR 2) User scans in Quark App 3) Run login-wait to persist session

Any OpenClaw channel (Telegram / WhatsApp / 飞书 ...)

Use orchestration pattern: 1) Run: channel-run <op> ... 2) If exit code == 10 and JSON contains need_login: true: - Send qr_png back to the current chat/channel - Immediately start login-wait (poll every ~5s) - When login succeeds, automatically reply in the same chat/channel (e.g. “登录成功”) and then re-run the original INLINECODE23

Machine-readable interaction exit codes (for orchestration):

• - 10: INLINECODE24
• 11: need_pick=true (multiple candidates; re-run with --pick)
• 12: need_confirm=true (destructive ops; re-run with --confirm)

Commands (scripts/quark_drive.py)

Invoke as:

• - INLINECODE29

Auth

• - INLINECODE30
• INLINECODE31
• INLINECODE32
• INLINECODE33
• INLINECODE34 (preferred)
• INLINECODE35 (alias)

Browse

• - INLINECODE36
• INLINECODE37
• INLINECODE38 (privacy default: scoped to /OpenClaw/**)

Upload

• - INLINECODE40

Share (create link)

Conversation contract (important)

When the user asks to “生成分享链接/创建分享/分享某个文件(夹)”: 1) Search candidates first (do not ask user to provide full remote path). - Default: use server search. - If server search is insufficient and the user wants stronger fuzzy search, use a client-side fuzzy index and rank results by fuzzy score. - Privacy default: build the index in-memory (ephemeral) and do not write it to disk. - Only keep candidates whose resolved path is inside remote allowlist. 2) If multiple candidates: list them with index + path + type/size, ask user to pick. 3) Before creating the share, ask: - Expiry: 1 / 7 / 30 / 永久 - Passcode: 有 / 无 - If 有: ask for the code; if user does not provide, generate one (4–6 alnum). 4) If user does not answer: default to no passcode + permanent.

CLI

• - INLINECODE41
• INLINECODE42

- If multiple candidates and --pick is omitted, returns JSON with need_pick=true and a candidate list.

Local index helpers:

• - index-build --root <remote_path> --max-items <n> [--write] (may issue many API calls; without --write it does not persist)
• INLINECODE47 (builds ephemeral index; does not persist)

Share (save others' share into my drive / 转存)

• - INLINECODE48

Notes:

• - Quark typically forbids saving your own share (will error). Use an external share to test.

Destructive

• - INLINECODE49
• INLINECODE50
• INLINECODE51 (soft-delete into /OpenClaw/.trash)
• INLINECODE53

Troubleshooting

• - auth-status fails (401/403): session expired → run login flow again.
• INLINECODE55 fails with “用户禁止转存自己的分享”: you tried saving your own link → test with someone else’s share.
• If endpoints change and commands start 404/410xx: capture a browser network request (copy as cURL) and update adapter.