proton-drive-selective-backup
Skill0 starsChanged 39 days agoMITView on GitHub
Use when backing up selected macOS Documents or Downloads to Proton Drive while excluding installers and dependencies, reviewing Git-based exclusions, or checking whether a filtered upload is actually recoverable.
In this repository66 other files it gives its agents.
- AGENTS.mdAGENTS.md
- postgres-locking-joinsSkill
- ai-bug-patternsSkill
- compressed-ndjson-boundariesSkill
- http-resume-integritySkill
- linux-io-latency-triageSkill
- macos-disk-space-recoverySkill
- minimal-sufficient-evidenceSkill
- modularize-large-filesSkill
- patch-reproducer-validitySkill
- prompt-cache-boundariesSkill
- transactional-outbox-deliverySkill
- conventional-commitsSkill
- git-advanced-mergingSkill
- git-bisect-forensicsSkill
- git-data-recoverySkill
- git-hooksSkill
- git-rerereSkill
- git-reset-mechanicsSkill
- git-revisions-syntaxSkill
- git-rewriting-historySkill
- git-submodulesSkill
- git-worktreesSkill
- github-ssh-keysSkill
- npm-publish-ci-pitfallsSkill
- sapling-stacked-pr-workflowSkill
- go-concurrency-patternsSkill
- go-data-idiomsSkill
- go-error-handlingSkill
- go-interfaces-embeddingSkill
- go-pprof-profilingSkill
- marketing-funnel-diagnosisSkill
- marketing-geo-experimentsSkill
- marketing-incrementalitySkill
- marketing-positioning-testsSkill
- python-descriptors-mroSkill
- python-logging-cookbookSkill
- python-scaling-regression-testsSkill
- python-unicode-gotchasSkill
- rust-compile-time-invariantsSkill
- rust-deterministic-concurrency-testsSkill
- rust-error-identity-boundariesSkill
- rust-regex-search-contractsSkill
- rust-runtime-bug-classesSkill
- rust-tokio-actor-deliverySkill
- rust-tokio-cancellation-safetySkill
- sales-discovery-qualificationSkill
- sales-mutual-action-plansSkill
- sales-pipeline-forecast-calibrationSkill
- sales-value-negotiationSkill
- ai-triage-evaluationSkill
- container-image-patchingSkill
- dependency-artifact-integritySkill
- dnssec-sentinel-diagnosticsSkill
- iam-policy-change-replaySkill
- rbvm-applicabilitySkill
- rbvm-asset-evidenceSkill
- rbvm-guarded-remediationSkill
- rbvm-priority-decisionsSkill
- rbvm-risk-exceptionsSkill
- The first 60 shown.
The file
Files
Proton Drive selective backup
A cleanup candidate is not a backup exclusion. A Git remote is not proof that local work is recoverable. Separate inventory, selection, transfer and restore evidence; never delete originals to make a backup smaller.
Selection contract
| Input | Default decision |
Regular .dmg files; node_modules directories | Exclude with an explicit reason; review locally patched dependencies |
| PDFs, photos, Office files, archives, dotfiles | Keep as candidates, not automatically authorized uploads |
build, dist, vendor, caches | Exclude only exact reviewed paths; names alone do not establish reproducibility |
| Git projects | Keep working files; require separate repository-recovery review |
| Symlinks, special files, unreadable/changing entries | Report blockers, never silently follow or call complete |
The planner requires explicit roots, emits JSON, hashes files, and never invokes Git, Mole or Proton. Its .git omission blocks completeness. Check local-only/unpushed branches, dirty/untracked work, ignored assets, LFS objects and submodules before approving project exclusions. .gitignore is not a backup policy.
Recipe
- Obtain permission for the exact local roots. After checking installed-version help, optional
mo analyze --json "$HOME/Documents"provides sizing insights; partial sizes are lower bounds. Never run Mole cleanup, purge, installer or optimize in this workflow. From this skill directory, run:
python3 scripts/plan_backup.py --root "Documents=$HOME/Documents" --root "Downloads=$HOME/Downloads"Resolve exclusions, Git warnings, collisions, limits and errors. Keep the manifest private: filenames and hashes reveal information. See planner contract.
- Show selected data categories, destination account/folder, estimated bytes and omissions. Obtain upload approval, explicitly covering sensitive documents or secrets; encryption does not substitute for consent. Installation, persistent authentication and recurring runs require their own authorization. Browser login is
proton-drive auth login; putting the binary on PATH is separate from its saved session. - Prepare an approved, private staging copy outside every source root; use regular files, not symlinks or hard links to changing originals. Rehash staging against the approved manifest and stop on drift. See transfer and restore gates. The planner does not implement staging or transfer.
- Confirm installed CLI options, upload only staging, reconcile every planned item, then restore into a fresh directory and compare paths, sizes and SHA-256. Report sampled versus complete verification accurately. Never propagate local deletion or run remote replacement by default.
Pitfalls
- Proton
skipcan omit changed files; current-sourcereplacetrashes remote content. JSON mode does not make a command a dry run. - Case-only or Unicode-equivalent names may collide on restoration. Resolve without overwriting originals.
- A clean scan is not an atomic snapshot; later changes invalidate approval and hashes. File bytes alone do not preserve macOS ACLs, resource forks or extended attributes.
- Upload success, cached remote digests and configured Git remotes are not restore evidence. Sources and version limits.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

