feat(our-gdrive-organizer): add new skill at slot 82, rename old 82 → 92

New Python CLI + dual SKILL.md (Code + Desktop) for organizing Google
Drive folders under OurDigital conventions:

- Refresh root README index (preserves manual Topics/Notes between
  AUTO-STRUCTURE markers)
- Ensure per-subfolder README.md meta files
- Propose filename + folder renames (D.intelligence → OurDigital with
  SEO-context caveat documented in patterns/gotchas.md)
- Propose moves for cluttered files (screenshots, temp downloads)
- Sensitive-folder skip list (04_Case Studies, 99_Project Archive,
  *Archive*, 진단*)
- shared/patterns/ gotcha library: canonical-files, canonical-folders,
  categorization-rules, 12 known gotchas — grows over time as the
  system encounters new edge cases

Slash command: /organize. CLI: ~/.local/bin/our-gdrive-organize.

82-tui-design-template renumbered to 92 (no content change) to free
slot 82. AGENTS.md and CLAUDE.md updated for both moves.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-05-10 23:02:45 +09:00
parent e1bd799672
commit c750fa7f5e
16 changed files with 1731 additions and 5 deletions

View File

@@ -0,0 +1,103 @@
---
name: our-gdrive-organizer
description: |
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.
version: "1.0"
author: OurDigital
environment: 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:
```bash
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:
```bash
our-gdrive-organize "/path/to/folder" --apply
```
Or just one scope at a time:
```bash
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.