Sync Notes
ReviewAudited by ClawScan on May 17, 2026.
Overview
The skill’s note-sync behavior is mostly coherent, but it makes sensitive files and plaintext backups while claiming they are gitignored even though no .gitignore is included in the provided package.
Install only if you are comfortable giving it access to your notes folder and an R2 bucket. Add your own .gitignore exclusions before running setup, use a narrowly scoped R2 token, verify the initial bisync baseline carefully, and keep an independent backup of important notes.
Findings (4)
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.
A mistaken sync or bad baseline could affect both your local notes and the cloud copy.
The skill intentionally uses rclone bisync, which can propagate deletions or unintended changes between the local vault and the R2 bucket.
`bisync` is powerful and can delete on both sides. Use `--dry-run` and `status` liberally on the first few runs.
Run status and dry-run checks during setup, confirm the initial baseline, and keep an independent backup before routine use.
Anyone with the generated rclone.conf could access or modify the configured R2 storage according to the token’s permissions.
The setup wizard collects Cloudflare R2 access credentials, which is expected for this integration but grants access to the configured bucket.
prompt R2_ACCESS_KEY "R2 Access Key ID" prompt R2_SECRET "R2 Secret Access Key" "" silent
Use an R2 token scoped only to the intended bucket and prefix, and rotate it if the config file may have been exposed.
Private notes may exist outside the original vault path in the skill’s backups directory.
The skill intentionally creates local plaintext backups of the notes vault; this is useful for recovery but sensitive.
- **Never commit `backups/`** — it contains a verbatim copy of your vault.
Treat the backups directory as sensitive, exclude it from sharing or indexing, and delete it securely if you uninstall the skill.
Users may rely on a missing safety control and accidentally commit or share R2 credentials, crypt settings, or plaintext note backups.
The documentation tells users sensitive generated files are covered by .gitignore, but the provided file manifest does not include a .gitignore file.
- **Never commit `config/rclone.conf` or `config/.env`** — they're in `.gitignore`, but double-check before pushing. - **Never commit `backups/`** — it contains a verbatim copy of your vault. Also gitignored.
Before setup, add a .gitignore that excludes config/rclone.conf, config/.env, backups/, logs/, and state/, or keep this skill outside any repository you publish.