---
name: google-drive-and-shared-drive-file-operations
description: >-
  Organizes files and folders in a connected Drive or Shared Drive: audits structure, finds duplicates and orphans, creates the target hierarchy, and moves, copies, renames or uploads files under approval. Use when the user asks to organize Drive, tidy a shared drive, audit assets, or upload a set of files.
metadata:
  version: "1.1.1"
---

# google-drive-and-shared-drive-file-operations

> **Client-neutral reusable package.** No client names, tenant or workspace identifiers, account or
> resource IDs, customer records, credentials, or internal paths. All examples are synthetic.

| | |
|---|---|
| Live catalog name | Google Drive and Shared Drive File Operations |
| Live category | Files & Content |
| Catalog entry | 10 |
| Internal capability ID | `CAP-FC-01` |
| Provider | Google Drive |
| Availability | Candidate; validate in the active Workspace |
| Deliverable type | `client_ready_guided_skill` |
| Validation status | Candidate; local package validation only |
| Version | 1.1.0 |


## OLLIE Runtime integration

Use this capability under the active OLLIE Operator. Read live Workspace Context and tenant
bindings for the required inputs below; this public package supplies no client facts or authority.
Consume `ask-ollie-authority-core` for authority, `outloop-access-fallback` for recovery and
resource verification, `email-lifecycle-core` for recipients, approvals and stored-copy delivery
verification, and the bootstrapper Runtime Contract for ownership, scheduling and completion.
These owners govern execution; this Skill does not implement a competing runtime.

Select the relevant expertise below for the requested outcome. Runtime governs combining Skills,
partial use and completing missing steps with other authorized capabilities. This Skill's domain
scope does not limit the Operator's wider authorized task. Preserve domain safety restrictions.
Verify findings against source evidence and read back any resulting artifact or authorized change.

## Business outcome

Assets live where people expect to find them, and every file operation is reversible and recorded.

## Operating modes

Read · Analyze · Draft · Write with approval

## Prerequisites — what must be true before this runs

- Workspace Context
- An approved Drive grant with upload capability where files will be written
- An agreed folder taxonomy

## Required inputs

| Input | Source |
|---|---|
| Approved drive or shared-drive scope | Workspace configuration |
| Target folder taxonomy | Required — the structure to converge on |
| Naming convention | Workspace Context |
| Retention and archive policy | Configuration |
| Named approver for any move or delete | Configuration |

## Trash, never purge

Moving a file to trash is recoverable; permanent deletion is not. This workflow trashes under an explicit gate
and never permanently deletes. If a client asks for a purge, that is a human action taken in the provider's own
interface, not an agent action.

## Upload the bytes, do not recreate the file

Binary transfers use the media transfer verbs so the real file moves byte-for-byte. Never reconstruct a file's
contents in order to "upload" it, never convert a file to another format silently, and never substitute a
regenerated version for an authoritative asset. Format conversion is an explicit, named step or it does not happen.

## Read the destination before writing to it

Inspect the target folder before creating anything in it. Do not delete or overwrite an existing item you did
not create and cannot account for — report it instead. An unknown file in the destination is information, not an
obstacle.

## Action classification

| Action class | This workflow |
|---|---|
| Read | Files, folders, hierarchy, ownership, permissions, sizes, timestamps, duplicate detection |
| Analyze | Structure drift, orphaned files, duplicates by checksum and by name, naming-convention breaches, permission anomalies |
| Draft | A proposed target structure and a file-by-file move plan |
| Write with approval | Folder creation, upload, copy, move and rename — approved plan only |
| Destructive | Trash is available and gated. **Permanent deletion is out of scope** |

## Approval and delivery

The Operator applies Authority Core and the active Workspace approval policy to any requested
mutation. Email Lifecycle owns recipient classification, sending and stored-copy verification.
The action table defines this capability's domain scope; it grants no permission by itself.

## Expected output

A structure audit, a proposed taxonomy, and a move plan — then, after approval, an operation log with the resulting identifier and a read-back confirmation per file.

## Synthetic placeholders used in this package

These are illustrative only. Real values come from the client's own workspace configuration and are
never written back into this package.

| Placeholder | Meaning |
|---|---|
| `DRIVE_PLACEHOLDER` | Approved drive scope |
| `FOLDER_PLACEHOLDER` | Target folder |
| `APPROVER_PLACEHOLDER` | Named approver |