OneDrive Integration
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a mostly transparent OneDrive copy helper, but it ships with a real hard-coded OneDrive destination, so files could be copied to the wrong synced folder unless the config is replaced.
Before installing or using this skill, open config.env and replace the bundled OneDrive path with your own confirmed OneDrive folder. Only run it on files you intentionally want synced to OneDrive, and consider removing copied files after sharing.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the user does not inspect or replace this file, selected documents may be copied to the preconfigured OneDrive path rather than the user's intended OneDrive folder.
The distributed artifact includes a real machine-specific OneDrive destination. Because the copy script reads the skill-local config by default, this can become the active copy target without first onboarding the installing user.
ONEDRIVE_ROOT="/mnt/c/Users/kongz/OneDrive" ONEDRIVE_SUBDIR="openclaw"
Remove config.env from the distributed skill, ship only a config.env.example, and require explicit user confirmation of ONEDRIVE_ROOT before copying any files.
A mistakenly selected sensitive file, or a filename revealing private folder names, could persist in OneDrive and sync to cloud-connected devices.
The core behavior intentionally places selected local files into a OneDrive-synced folder, and the destination filenames preserve source-path information.
Copy requested file(s) into: `${ONEDRIVE_ROOT}/${ONEDRIVE_SUBDIR}/` ... During copy, rename files to include their source pathConfirm both the source files and the OneDrive destination before use, avoid copying secrets, and delete copied files from OneDrive when they are no longer needed.