Andrew Yim
e519a49cc4
Run the additive migration pass from SKILL-MIGRATION-GUIDE: generate a root SKILL.md for every skill that lacked one, copied from its desktop/SKILL.md (or code/SKILL.md), with name set to the directory name and description + body preserved verbatim. - scripts/migrate_skill_root.py: the reusable, non-destructive migrator (dry-run default). - 61 new root SKILL.md (desktop source for most; code/SKILL.md for 61/62/92). - Untouched: 16/17/95 (already had root); desktop/ and code/ packaging left intact. - All 64 root SKILL.md validate: frontmatter <=1024, kebab name, description present. Still MANUAL (no SKILL.md source — commands/README only), need hand-authored root SKILL.md: 81-mac-optimizer, 90-reference-curator, 91-multi-agent-guide, 94-dintel-bootstrap. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3.6 KiB
name, description, version, author, environment
| name | description | version | author | environment |
|---|---|---|---|---|
| 82-our-gdrive-organizer | Organize a Google Drive folder under OurDigital conventions: refresh the root README.md index, refresh per-subfolder README.md meta files, propose filename normalizations (D.intelligence → OurDigital, client name → OOO placeholder), and propose moves for cluttered files (screenshots, temp downloads). Triggers: - "organize the Drive folder", "organize this folder" - "refresh the index", "rescan the folder", "update README" - "clean up cluttered files", "propose renames" - "/organize", "/our-gdrive-organizer" Designed for any 2nd-level Drive folder (not specific to one project). In Claude Desktop, this is a guide — the actual filesystem operations are performed by the user via the bundled `organizer.py` CLI in a terminal, or by Claude with a filesystem MCP tool if available. | 1.0 | OurDigital | Desktop |
our-gdrive-organizer (Desktop)
Guide for organizing a Drive folder under OurDigital naming + structure conventions. In Claude Desktop without filesystem write access, walk the user through running the bundled CLI script themselves.
Activation
User says any of:
- "organize my Drive folder"
- "refresh the index README"
- "scan for changes and update the README"
- "rename files to follow OurDigital convention"
- "/organize" (slash command)
Workflow
Step 1 — Identify the target folder
Ask the user which folder they want to organize, or assume the conversation's
current 2nd-level Drive folder (e.g., 02_SEO in Action/,
01_Brand in Action/, 00_OurDigital/).
Step 2 — Have the user run the CLI
The Python script lives in the user's local ~/Project/our-claude-skills/
repo and is symlinked to ~/.local/bin/our-gdrive-organize. The user runs:
our-gdrive-organize "/Users/ourdigital/Library/CloudStorage/GoogleDrive-andrew.yim@ourdigital.org/My Drive/NN_FolderName"
This is a dry-run by default. It always writes the README index (idempotent), and it prints proposals for renames and moves without applying them.
Ask the user to paste back the report.
Step 3 — Summarize and confirm
Read the report, summarize each proposed rename and move in plain language, and ask the user which (if any) they want to apply. They can apply all:
our-gdrive-organize "/path/to/folder" --apply
Or just one scope at a time:
our-gdrive-organize "/path/to/folder" --scope rename --apply
out-gdrive-organize "/path/to/folder" --scope move --apply
Important guardrails
The script automatically skips invasive changes (renames, moves) inside:
04_Case Studies/99_Project Archive/- Any folder ending in
Archive - Any folder starting with
진단
These are client-engagement records that must keep their original filenames.
If the user wants to override that, they need to edit
SENSITIVE_SUBFOLDER_PATTERNS in ~/Project/our-claude-skills/custom-skills/our-gdrive-organizer/code/organizer.py.
Naming convention
See ../shared/conventions.md for the canonical spec. Highlights:
D.intelligence→OurDigital(rebrand)- Client-specific quote/template files →
OurDigital-{topic}-OOO {date}.{ext} - Top-level subfolders →
NN_descriptive name - Client subfolders inside Active Workspaces / Project Archive →
NN_{client name}
Troubleshooting
- "command not found: our-gdrive-organize" — the symlink may not be set up.
Ask the user to run:
ln -s ~/Project/our-claude-skills/custom-skills/our-gdrive-organizer/code/organizer.py ~/.local/bin/our-gdrive-organize - Script changes README but the user doesn't see the update — Google Drive sync delay; usually 5-30 seconds.