Other

/drive-filing

Brain Drive upload, archive this, post-digest archival, docs.local cleanup/rollup. NOT for Gemini Deep Research/queries.

$ golems-cli skills install drive-filing
14 evals

Updated today

One skill for everything that moves durable artifacts out of docs.local/ (formerly drive-usage, google-drive-archive, and the archive skill). Drive queries use connected Drive search tools; this skill owns filing.

Etan's pain: agents (except researchers) don't use Drive right and leave artifacts scattered in docs.local/. This skill makes filing automatic. Rule of thumb: if an artifact should outlive this session, file it by § Machine hygiene: code and harnesses in a repo, personal or client documents in iCloud, other durable artifacts in the RIGHT Brain Drive folder — docs.local/ is a cache, not a home.

NeedGo to
Which folder, what name§ Brain Drive folder model, § Decision tree, § Naming convention (below)
Put a heavy (>100KB / media / transcript) artifact into Drive, with ledger + brain_digest§ Archive a heavy artifact → references/archive-procedure.md
Keep docs.local/ legible over time (daily → monthly → Drive)§ docs.local lifecycle
Manifest schema, disk measurement commands, path reconciliationreferences/archiving-convention.md

Not this skill: connected Drive search tools query existing files; /gemini-research does web research with Drive sources.

Brain Drive folder model

Folder IDs are private deployment values. Resolve them from the environment or private operator configuration; never copy live Drive IDs into this skill.

FolderidWhat goes here
01_STANDARDS${BRAIN_DRIVE_STANDARDS_FOLDER_ID}Canonical specs, conventions, locked schemas, standards docs (durable reference).
02_GROUNDING${BRAIN_DRIVE_GROUNDING_FOLDER_ID}Grounding corpora / reference data agents ground answers on.
03_RESEARCH${BRAIN_DRIVE_RESEARCH_FOLDER_ID}Research prompts + results. In-flight → 03_RESEARCH/Active/<topic>/ via ${BRAIN_DRIVE_RESEARCH_ACTIVE_FOLDER_ID}.
04_INGEST${BRAIN_DRIVE_INGEST_FOLDER_ID}Raw inbound to be processed/digested (not yet curated).
06_ARCHIVE${BRAIN_DRIVE_ARCHIVE_FOLDER_ID}Forever storage of finished heavy artifacts (transcripts, audio/video, big audits/plans). Target of § Archive a heavy artifact.

Folder semantics (what each numbered folder means) are confirmed with brainlayer-LEAD (s:57, owns Drive/backup). Legacy non-numbered folders (Research ×2 duplicates, Sessions, Collabs, _inbox-*, BrainBar Design Audit) are pre-taxonomy scatter — do not add to them; file into the numbered model. (Consolidation of the legacy dupes is an s:57 cleanup task.)

Legacy Brain Drive/Research/<project>/ folders are being moved under 03_RESEARCH/Active; if a prompt isn't found in Active, check the legacy path read-only and report it, never write there.

Decision tree (where does THIS artifact go?)

  1. A research prompt or its results? → 03_RESEARCH/Active/<topic>/ (e.g. skills-eval/). Drive-ground prompts by uploading the real artifacts beside them.
  2. A finished heavy artifact (>100KB / media / raw transcript / big audit)? → § Archive a heavy artifact → lands in 06_ARCHIVE/<area>/<topic>/<YYYY-MM-DD>/, leaves a _DRIVE-LEDGER.md pointer in docs.local/.
  3. A canonical standard / spec / locked schema? → 01_STANDARDS/.
  4. Grounding corpus / reference data? → 02_GROUNDING/.
  5. Raw, not-yet-digested inbound? → 04_INGEST/.
  6. Lightweight, session-scoped scratch? → fine to leave in docs.local/ — but if anyone else (or future-you) needs it, FILE it per 1–5.

Naming convention

New standalone artifacts: YYYY-MM-DD-<project>-<topic>-<kind>[-by-<producer>].<ext>, lowercase kebab-case. Example: 2026-11-04-voicebar-focus-audit-by-author.md. Topic must describe the work; Theo.md, Model.md and 2026-11-04-golems-theo-report.md fail. Put a person/model attribution in by-<producer> (exactly one lowercase token), never in the project, topic or kind slots. Kinds: report, prompt, result, transcript, recording, audit, plan, review, frame, image, notes, receipt, manifest, data, archive, index, dashboard, summary, eval, log.

Before uploading a new standalone artifact, set GOLEMS_ROOT to the absolute golems checkout (normally $HOME/Gits/golems) and run node "$GOLEMS_ROOT/scripts/drive/lint-name.mjs" <basename> from any repo; nonzero blocks filing until renamed. Existing files and preserved archive members (including MANIFEST.json and frame names) are grandfathered: --existing reports issues without blocking or renaming. Research-lifecycle's sequential context/R-number names keep their own contract. Folders retain <topic>-<domain>/; keep local mirror and Drive names identical for 1:1 ledger mapping.