Skip to content

gdrive-share

Publish matter content from the live OneDrive workspace to the firm's shared Google Drive (H:\My Drive\\) so the team sees it through the shared login. One-way copy - never writes back to the workspace. Use when asked to share a matter with the team, publish something to Google Drive, copy a matter to My Drive, or make a matter visible to the firm Google account.

Source: .opencode/skills/gdrive-share/SKILL.md — site rebuilt 2026-09-05.

gdrive-share — Publish to the team's Google Drive

The team shares one Google login (info@blp-uk.com). Anything in H:\My Drive is immediately visible to everyone on that login. This skill publishes a matter (or a subset of it) from the live OneDrive workspace to H:\My Drive\<client>\<matter> as a one-way copy — it never writes back, never edits, never renames anything in the workspace.

When to use

  • "Share this matter with the team", "put X on the Google Drive", "make Y visible to the firm account"
  • Updating the team's copy of a matter after new OCR/filing batches

Workflow

1. Identify source and target

  • Source: the live matter folder under OKF\Contentious_* / OKF\NonContentious_* (or wherever the matter lives in the workspace).
  • Target: H:\My Drive\<client>\<matter> — mirror the naming already used in H:\My Drive (client-company folders, e.g. H:\My Drive\01367-Ennova Limited t a Ennova Law). Check existing naming there first; never invent a new pattern if one exists.

2. Check the drive

  • H:\ must be mounted (Google Drive for Desktop). If missing: tell the user to sign in to Google Drive for Desktop with the shared login, then re-run.
  • Never write to H:\ root or H:\My Drive root — only into the matter's own folder.

3. Publish

Run the helper (read-only on the source): 

powershell -ExecutionPolicy Bypass -File "<this skill's base directory>\tools\publish.ps1" `
  -Source "<workspace matter folder>" `
  -Target "H:\My Drive\<client>\<matter>" `
  [-WhatIf]
The script copies files (skip older, overwrite newer), and excludes machine-state and staging folders: .opencode, graphify-out, NotebookLM_*, __pycache__, .venv, venv, .git, 98_Inbox_ToProcess, 97_OCR_Log staging artifacts.

  • Always run once with -WhatIf first and show the user what would be copied.
  • After the copy, verify: list the target, confirm file count and total size, and report the exact target path to the user ("team can see it at H:\My Drive\<client>\<matter>").

4. Never

  • Copy into a Shared Drive (H:\Shared drives\...) unless the user explicitly asks — those are separate ownership spaces.
  • Mirror (/MIR) — this is additive publish; deletions on the Drive side are the user's call.
  • Copy secrets: if the source contains auth.json, API keys, or client bank details not already in the matter, flag it to the user before publishing.