Menu

Individual skill

drive-persistence-bridge

0upvotes

Creates, verifies, restores, or synchronizes user-approved backups and artifacts with connected cloud storage or a repository. Use for: backing up files, preparing a restore, comparing versions, or uploading a specifically approved artifact.

.grok/skills/drive-persistence-bridge/SKILL.md

Read pinned source

Source commit bf31cc83a43ed8069d0d5070c68df4250273eb29

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
14
Repository last updated
Oct 21, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Drive Persistence Bridge

Use this skill to preserve named artifacts safely across local storage and an approved remote destination. It supports backup preparation, version comparison, restore planning, and approved uploads; it does **not** authorize autonomous synchronization or publication.

## Workflow

1. Confirm the source files, destination service and folder or repository, retention expectation, and whether the request is local-only, upload, restore, or comparison.
2. Inspect available connector capabilities and permissions. Use read-only discovery first; do not assume a destination, branch, folder, account, or tool schema.
3. Build a local, timestamped artifact with a clear name. Record its checksum, source scope, creation time, and a concise description. Exclude secrets, credentials, cache directories, and unnecessary personal data.
4. For a remote upload, repository commit or push, restoration that overwrites files, retention cleanup, or deletion, present a preview of the exact targets and changes. Obtain explicit user approval before proceeding.
5. Execute only the approved operation with least privilege. Verify the returned identifier, link, commit reference, or checksum.
6. Report what completed, where it was stored, how to restore it, and any failed steps. Keep local artifacts intact when a remote operation fails.

## Restore and Version Comparison
Back to top