research-backuplisted

Back up untracked research report directories (outputs/, results/, report(s)/) from local projects into the locally synced Dropbox folder, organized by category/project. Discovers candidate directories that git does not track, keeps a registry under ~/.config/research-backup/, and mirrors additively with rsync (deletions are never propagated). Use when the user asks to back up research outputs or reports to Dropbox, register new report directories for backup, check what would change before backing up, or says backup outputs, research backup, outputs 백업, 결과 백업, 리포트 백업, 연구 백업, Dropbox 백업 모음. For single-file upload/download/share through the Dropbox API use the dropbox skill instead.
Axect/skills · ★ 3 · AI & Automation · score 76

Install: claude install-skill Axect/skills

# Research Backup Backs up the report/output directories that research projects keep outside git (`outputs/`, `results/`, `report/`, `reports/`) into the locally synced Dropbox folder. The Dropbox daemon handles the actual upload; this skill only writes files under `BACKUP_ROOT` with rsync, so backups are incremental and need no API credentials. ## Which Dropbox skill? - `research-backup` (this skill): bulk, recurring backup of whole report directories into the local `~/Dropbox` sync folder. Requires the Dropbox client to be syncing this machine. - `dropbox`: one-off upload/download/share of individual files through the Dropbox HTTP API. Works without a local sync client. ## How projects are separated Sources are mirrored relative to `SCAN_ROOT` (default `$HOME/Documents/Project`), so the Dropbox side keeps the full `<category>/<project>/<dir>` layout: ~/Documents/Project/Research/MyProject/results -> ~/Dropbox/ResearchBackup/Research/MyProject/results Same-named projects in different categories (e.g. two `pytorch_template` checkouts) never collide because the category directory is part of the destination path. ## Prerequisites (check before any operation) 1. `rsync` on PATH. 2. A locally synced Dropbox folder. Verify the parent of `BACKUP_ROOT` exists (default check: `test -d ~/Dropbox`). If it does not exist, tell the user the Dropbox client is not syncing this machine and stop; do not fall back to the API. 3. The Dropbox daemon must be running for local writ