---
name: drive-asset-hygiene-auditor
description: "Audit a client's Google Drive (or similar shared drive) folder structure for organization problems — mixed drafts/finals, untraceable briefs, inconsistent naming, orphans, duplicates — and propose a clean folder structure and naming convention. Read-only on names and metadata; never opens file contents, never moves or renames anything. Use before onboarding a team member or agent onto a client Drive, or as a quarterly hygiene check."
metadata:
  version: "1.1.0"
  scope: "standalone-template"
---

> Standalone draft/audit template. Not validated for OLLIE execution.


# Drive & Asset Hygiene Auditor

## Who it's for

Agencies managing client assets across Google Drive or a similar shared-drive setup — especially once you're juggling more than a few clients and folders start drifting out of any consistent structure.

## What problem it solves

Every agency's Drive ends up the same way after a year: mixed drafts and finals in one folder, briefs nobody can trace back to a decision, three different naming conventions from three different team members. This skill gives an agent the job of reading the current structure and telling you exactly what's disorganized and why, plus a clean structure to move toward — without touching a single file.

## When to use it

- Before onboarding a new team member or agent workflow onto a client's Drive (so they inherit a sane structure, not a mess)
- Quarterly, as a standing hygiene check on any client with an active, growing asset library
- Whenever "where's the final version of X" becomes a recurring question on a client

## Required inputs

- Read-only access to the client's Drive folder tree (folder and file names, dates modified, and basic file metadata — not the file contents themselves)
- Optional: a note on the agency's intended naming convention or folder structure, if one already exists informally, so the agent can check for drift against it rather than inventing a new standard

## Agent instructions

You are auditing a client's Drive folder structure for organization
problems. You have READ-ONLY access to folder and file names and metadata.
You may not move, rename, delete, copy, or edit a single file or folder —
this task produces a report and a proposed structure only.

1. Map the current folder tree: top-level folders, their subfolders, and
   roughly how many files live in each.
2. Identify the common failure patterns:
   - Drafts and final/approved versions mixed in the same folder with no
     clear distinction
   - Briefs, creative packages, or deliverables with no traceable link back
     to who approved them or when
   - Inconsistent naming across similar files (e.g., three different date
     formats, or "final," "final_v2," "final_ACTUAL" all in the same folder)
   - Orphaned files sitting outside any clear folder category
   - Duplicate or near-duplicate files that suggest a broken working
     process rather than a deliberate archive
3. For each problem found, name the specific folder/file pattern (not just
   "this is messy") so a human can go verify it directly.
4. Propose a clean folder structure: a small number of top-level categories
   (for example: raw assets, active briefs, delivered/client-facing,
   reports, archive), plus a simple, consistent naming convention.
5. Do not move, rename, or delete anything. Produce the findings and the
   proposed structure, and stop.

## Expected output format

A findings report: a short list of specific disorganization patterns found, each with a concrete example (folder/file name, not file contents).

Followed by a proposed folder structure and naming convention, presented as a simple template the agency can apply manually.

## Human approval checkpoint

No file or folder changes until a human reviews the proposed structure and decides how (and whether) to reorganize. If the agency later wants an agent to actually execute the reorganization, that is a separate, explicitly-approved action — never bundled into this audit.

## Safety rules

- Read-only against file/folder names and metadata — never opens or reads file contents unless explicitly asked to for a specific, named reason
- Every finding names a specific example a human can verify directly, never a vague "this seems disorganized"
- The proposed structure is a template, not an instruction to execute

## What the agent must not do

- Move, rename, copy, or delete any file or folder
- Change any sharing permissions or link settings
- Open or read the contents of client files beyond what's needed to confirm a file's category (e.g., "this is a draft vs. final")
- Touch more than one client's folder tree in a single run

---

Part of the Outloop Agency Skill Pack ([outloop.co](https://outloop.co)). To turn this from a draft-only workflow into a safe runtime workflow across client workspaces, use Outloop to approve the right access, block wrong-client use, and keep secrets out of the agent context.