etanhey/drive-usage
skills/golem-powers/drive-usage/SKILL.md
Brain Drive filing discipline — where every artifact goes + how to name it. Use WHENEVER touching Google Drive / Brain Drive: uploading, creating folders, saving research prompts/results, audits, plans, transcripts, dashboards, or when about to leave a durable artifact in docs.local/. Teaches the numbered folder model (01_STANDARDS / 02_GROUNDING / 03_RESEARCH / 04_INGEST / 06_ARCHIVE), date-prefixed naming, and the rule: FILE durable artifacts in the right Drive folder — docs.local/ is cache-only. NOT for querying Drive via Gemini (use /braindrive) or web research (use /gemini-research); for >100KB heavy archival defer to /google-drive-archive.
$ install --global
skillsauthnpx skillsauth add etanhey/golems drive-usageInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 7, 2026, 3:06 AM14.6s1 file scanned
SKILL.md
- name:
- drive-usage
- description:
- Brain Drive filing discipline — where every artifact goes + how to name it. Use WHENEVER touching Google Drive / Brain Drive: uploading, creating folders, saving research prompts/results, audits, plans, transcripts, dashboards, or when about to leave a durable artifact in docs.local/. Teaches the numbered folder model (01_STANDARDS / 02_GROUNDING / 03_RESEARCH / 04_INGEST / 06_ARCHIVE), date-prefixed naming, and the rule: FILE durable artifacts in the right Drive folder — docs.local/ is cache-only. NOT for querying Drive via Gemini (use /braindrive) or web research (use /gemini-research); for >100KB heavy archival defer to /google-drive-archive.
/drive-usage — Brain Drive filing discipline (where things go)
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, it goes to Brain Drive in the RIGHT folder —docs.local/is a cache, not a home.
This is the routing/where-does-this-go layer. Related: /google-drive-archive = the heavy (>100KB/media) archival workflow; /braindrive = query Drive via Gemini; /gemini-research = web research with Drive sources. This skill decides which folder + what name, then hands off to those for the actual move when heavy.
Brain Drive folder model (real — root 1XJOCNtK-gYE_UVVfBGZjW3RLZIQ4NcGJ)
| Folder | id | What goes here |
|--------|----|----|
| 01_STANDARDS | 1IM9Q1EjQ5JRos804Ix6ZCr_Mq9VnEhMv | Canonical specs, conventions, locked schemas, standards docs (durable reference). |
| 02_GROUNDING | 1jYJPjJ0Hhu2eZjFdBeLxI3Oipaq7ab6z | Grounding corpora / reference data agents ground answers on. |
| 03_RESEARCH | 1nSQkJaIaD6lzcxVZ15-AvB7hl8Ip2W_r | Research prompts + results. In-flight → 03_RESEARCH/Active/<topic>/ (id 1zqKMg4zd58W24bTVZGe1EnTueB7OIgS7). |
| 04_INGEST | 1pgV_aX4N1rtUMBaxFY1DQalEdl-EBVas | Raw inbound to be processed/digested (not yet curated). |
| 06_ARCHIVE | 1ld8fKs9-4URpp-R1D7J_41RBuxHVZjBK | Forever storage of finished heavy artifacts (transcripts, audio/video, big audits/plans). Target of /google-drive-archive. |
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.)
Decision tree (where does THIS artifact go?)
- A research prompt or its results? →
03_RESEARCH/Active/<topic>/(e.g.skills-eval-phoenix/). Drive-ground prompts by uploading the real artifacts beside them. - A finished heavy artifact (>100KB / media / raw transcript / big audit)? → invoke
/google-drive-archive→ lands in06_ARCHIVE/<area>/<topic>/<date>/, leaves a_DRIVE-LEDGER.mdpointer indocs.local/. - A canonical standard / spec / locked schema? →
01_STANDARDS/. - Grounding corpus / reference data? →
02_GROUNDING/. - Raw, not-yet-digested inbound? →
04_INGEST/. - 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
YYYY-MM-DD-<topic>[-<surface/agent>].<ext> — date-prefixed, kebab-case, topic-first. Folders: <topic>-<domain>/ (e.g. weave-eval-phoenix/). Keep the local mirror name identical to the Drive name so the ledger maps 1:1.
The discipline (the one rule)
Before you finish a task that produced a durable artifact: did you FILE it in the right Brain Drive folder, or leave it scattered in docs.local/? If durable and still only local → file it now (this skill or /google-drive-archive) and drop a one-line _DRIVE-LEDGER.md pointer. "It's in docs.local" is not "it's saved."
Quick reference (MCP)
- Upload:
mcp__google-drive__uploadFile(localPath, parentFolderId=<from table>). - New topic folder:
mcp__google-drive__createFolder(name, parent=<numbered folder id>). - Find:
mcp__google-drive__search(query, rawQuery=true)with'<id>' in parents. - Heavy/forever: hand off to
/google-drive-archive.
After creating/editing this skill it must be REGISTERED (golem-install / symlink into
~/.claude/skills) before any agent can invoke it — committed ≠ installed.
Related Skills
etanhey/phoenix-human-view
tools
VerifiedTrustedCommunity
The human-eval UX contract for Phoenix views: turn-by-turn scrollable replay (not a scorecard), hide-but-copyable IDs, collapsed thinking, identity chips, tool filters, tiny frozen starter datasets, mark-wrong-in-thread, mobile-first. Use when: building or reviewing ANY Phoenix/eval view, annotation UI, session replay, or human-grading surface. Triggers: phoenix view, eval UI, annotation view, session replay, human eval UX, grading interface. NOT for: Phoenix data pipelines/ingest (capture scripts have their own specs).
3SKILL.mdUpdated Jun 7, 2026
etanhey/mac-systems
tools
VerifiedTrustedCommunity
macOS systems specialist — AppKit NSPanel architecture, launchd services, socket activation, MCP bridge resilience, syspolicyd, and high-frequency SwiftUI dashboards. Use when building menu-bar apps, LaunchAgents, debugging syspolicyd/Gatekeeper/TCC, resilient UDS/MCP bridges, or SwiftUI dashboards at 10Hz+.
3SKILL.mdUpdated Jun 7, 2026
etanhey/judge-fleet
development
VerifiedTrustedCommunity
Bulk LLM-judging protocol for fleet-dispatched verdict runs (KG cluster, eval harness). Use when: dispatching or running judge workers (J1/J2/RT), planning bulk-apply from verdict JSONL, or triaging evidence_degraded outputs. Triggers: judge fleet, bulk judge, R3 verdicts, kg-judge, RT gate, evidence_degraded. NOT for: single-item code review, Phoenix view UX (use phoenix-human-view), or non-judge eval pipelines.
3SKILL.mdUpdated Jun 7, 2026
etanhey/fleet-wrap
development
VerifiedTrustedCommunity
Quiet-down protocol for sprint close: when the fleet wraps, delete ALL polling crons and monitors, send ONE final dashboard + ONE message, then go SILENT. Use when: fleet wraps, all workers done, overnight queue exhausted, sprint close, Etan asleep/away with nothing approved left. Triggers: fleet wrap, wrap the fleet, stand down, going quiet, sprint close. NOT for: mid-sprint monitoring (keep your loops), spawning a successor (use /session-handoff first).
3SKILL.mdUpdated Jun 7, 2026