daily-cowork-backup

Archive Cowork session folders and configuration files to Google Drive.

8|1|Updated Mar 21, 2026
One-click install
npx skills add https://github.com/MSApps-Mobile/claude-plugins --skill daily-cowork-backup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: daily-cowork-backup
Source: https://github.com/MSApps-Mobile/claude-plugins/tree/main/plugins/session-backup/skills/session-backup
Command: npx skills add https://github.com/MSApps-Mobile/claude-plugins --skill daily-cowork-backup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates daily backups of Cowork VM sessions, bundling skills, Claude documents, plugins, and configuration files and removing the manual work of locating volatile session mounts, zipping components with exclusions, and transferring them to Google Drive.

Core Features & Use Cases

  • Automatic session discovery: Dynamically finds the active Cowork session mount so you never hardcode session names.
  • Componentized archiving with exclusions: Produces separate zip archives for skills, Claude documents (with optional splitting when large), plugins, and configs while excluding node_modules, .git, build artifacts, and image files.
  • Mac-side upload flow: Stages archives to the host via the mounted Claude folder and executes a two-step POST→GET upload using Desktop Commander to a configured Apps Script endpoint, replacing previous backups.
  • Use Case: Run daily as a scheduled Cowork task to maintain an up-to-date Cowork-Backups folder on Google Drive for disaster recovery and migration.

Quick Start

Run the daily-cowork-backup skill to discover the active session, create zipped backups of skills, docs, plugins, and configs with the required exclusions, stage them to the host, and upload them to the Cowork-Backups folder on Google Drive.

Frequently Asked Questions about daily-cowork-backup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate daily Cowork session backups to Google Drive?

You can automate daily Cowork session backups by running this skill to dynamically discover the active session mount, zip your skills, documents, plugins, and configurations, and upload them to Google Drive via Desktop Commander.

What files are excluded when zipping Cowork configurations and plugins for backup?

When zipping Cowork configurations and plugins for backup, the skill automatically excludes node_modules, .git directories, Next.js caches, and image files to reduce archive size and avoid payload limits.

Can I use Desktop Commander to upload large Cowork archives to Google Drive?

Yes, you can use Desktop Commander to upload large Cowork archives to Google Drive. The skill splits large archives to avoid payload limits and uses a POST to GET Apps Script redirect flow with replaceExisting uploads.

Does the backup process require hardcoding the active Cowork session mount name?

No, the backup process does not require hardcoding the active Cowork session mount name. The skill features automatic session discovery to dynamically locate the active Cowork VM session mount.

What is the best way to handle Google Drive payload limits when uploading Cowork backups?

The best way to handle Google Drive payload limits when uploading Cowork backups is to split large archives into smaller segments before using the two-step POST to GET upload flow via Desktop Commander.