Xdrop

Use the bundled scripts inside this skill directory.

Available scripts

• - scripts/upload.mjs — Upload local files or directories to an Xdrop server and print the share link
• INLINECODE1 — Download an Xdrop share link, decrypt it locally, and save the files

Environment requirements:

• - Bun
• Local filesystem access
• Network access to the target Xdrop server

Upload

CODEBLOCK0

Prefer these flags when relevant:

• - --quiet: suppress progress output and keep stdout clean
• INLINECODE3: return transferId, shareUrl, and INLINECODE6
• INLINECODE7: choose a supported expiry
• INLINECODE8: override the default INLINECODE9
• INLINECODE10: set the transfer display name
• INLINECODE11: limit parallel uploads per file

Useful examples:

CODEBLOCK1

If the user wants verification, upload a small temporary file and then confirm the public transfer API or browser can open the returned link.

Download

Require the full share link, including #k=.... Without the fragment key, the transfer cannot be decrypted.

CODEBLOCK2

Prefer these flags when relevant:

• - --output <dir>: choose the destination directory
• INLINECODE14: suppress progress output and keep stdout clean
• INLINECODE15: return transferId, outputRoot, and saved file paths
• INLINECODE18: override the default INLINECODE19

Useful examples:

CODEBLOCK3

By default the downloader writes to ./xdrop-<transferId> and preserves the manifest's relative paths.

Gotchas

• - A download link without the #k=... fragment is not decryptable. Ask for the full original share URL.
• Use --quiet whenever another command or caller needs to capture stdout. Progress logs otherwise go to stderr, but the final result still matters.

Guardrails

• - Prefer --quiet when another command or script needs to capture stdout.
• Keep the full share link fragment intact for downloads.
• Do not bypass the scripts' built-in path sanitization or transfer cleanup behavior with manual ad hoc commands unless the user explicitly asks.