onedrive-integration_skill

Overview

This skill copies large or long files into a OneDrive folder so users can open or share full documents from chat apps like Telegram or WhatsApp. It places files under an OpenClaw subfolder in the configured OneDrive root and returns the new filename and location for easy access.

How this skill works

The script reads a machine-specific config to find ONEDRIVE_ROOT and optional ONEDRIVE_SUBDIR, then copies provided paths into ${ONEDRIVE_ROOT}/${ONEDRIVE_SUBDIR}/. Files are renamed to include their source path (made filesystem-safe) to avoid collisions, timestamps are preserved, and the script prints the destination paths. If a browser-only document is requested, the file is downloaded to a temp path first, then copied. If ONEDRIVE_ROOT is unset, the skill asks the user to confirm the correct OneDrive folder before writing config.

When to use it

• You need to share a full document or long file via Telegram or WhatsApp where pasting is impractical.
• A chat user requests a local file that is too large or inconvenient to send directly in chat.
• You want a predictable OneDrive location for archived copies of files shared from chat.
• You need to preserve timestamps and avoid filename collisions when moving multiple files to OneDrive.

Best practices

• Confirm ONEDRIVE_ROOT once during onboarding; do not guess or assume a default path.
• Use the chat-first onboarding: ask for the OneDrive root, write config.env, then run a small smoke test file copy.
• Keep the canonical script inside the skill folder; only symlink into PATH if you want a short command.
• When sending browser-only documents, download them to a temporary path before invoking the copy script.
• Name collisions are avoided by source-path based renaming; verify resulting filenames if you rely on exact names.

Example use cases

• A Telegram user asks to view a long markdown document; copy the local file to OneDrive and reply with the OneDrive path.
• A WhatsApp contact needs a large PDF; download the browser copy if needed, copy it to openclaw/ in OneDrive, and share the new link.
• Batch-archive several local log files into OneDrive for later review, preserving timestamps and source info in filenames.
• Onboard a new machine: confirm OneDrive root in chat, write config.env, and run a small test copy to verify access.