| name | drive-persistence-bridge |
| description | Persists agent artifacts to cloud drive storage. Use when saving reports, ba ckups, or user says save to drive, persist output. Triggers: save to drive, persist output, upload report, cloud backup.
|
| version | 1.1.0 |
| author | Stijnman |
| license | MIT |
| metadata | {"grok":{"tags":["save to drive","persist output","upload report","cloud backup"],"related_skills":["connected-services-bridge","privacy-redactor","persistent-memory-bridge"]}} |
| compatibility | Grok agent; optional MCP and shell access |
Drive Persistence Bridge
When to Use
- User says save to drive or task matches this capability
- User says persist output or task matches this capability
- User says upload report or task matches this capability
- User says cloud backup or task matches this capability
Workflow
- Identify artifact and target folder.
- Run privacy-redactor on content if external.
- Upload via connected service; confirm link.
- Log path in semantic-memory-manager optional index.
Integrations
connected-services-bridgeprivacy-redactorpersistent-memory-bridge
Error Handling
| Failure | Response |
|---|
| Upload fail | Retry once; offer local save fallback. |
Gotchas
- Large files: confirm with user before upload.
Example
Input: User request matching triggers above.
Output: Structured result per workflow with integrations invoked as needed.
