Turn editor autosaves into a versioned vault you can actually recover from
Editors lose work from crashes, corruption, or confusion about which file is the "real" project vs an autosave. This recipe copies autosaves into a consistent, versioned vault with a rolling index and retention policy — so recovery is straightforward, not a gamble.
Create a skill called "Autosave Backup Vault". Inputs: - source_paths (autosave/backup folders for my editors) - vault_path - retention policy Behavior: - Detect new autosaves/backups and copy them into a versioned vault. - Keep an index of the newest restore points. - Never delete originals; only prune within the vault per retention.
This skill watches your editor's autosave/backup folders, copies new saves into a dated
vault structure, and maintains a rolling index of the latest restore points. It never
deletes originals — pruning only happens inside the vault per your retention policy.
Find out your backups are empty before you need them, not during the incident
Verifies your backups are actually restorable — checks completeness, freshness, and integrity. Runs automated restore tests to catch the silent failures that make backup confidence an illusion.
End "which file is latest?" forever
Creates a consistent project folder template, enforces versioned file naming, and keeps a lightweight transmittal log so you can always prove what was issued, when, and to whom.
Lock down your accounts and prepare for recovery
Creates a practical account security checklist for creators and a recovery plan if an account is compromised. Designed for creators who receive suspicious offers, face phishing, or worry about losing access to their income channels.
Scripture that speaks to where you are today
Get a daily Bible verse selected specifically for your current season of life. Your Claw uses what it knows about your work, family, and challenges to surface passages that actually resonate — not random verse-of-the-day generators.