This skill automates every coordination step that must happen when a new CoWork skill, plugin, or tool is created or updated at MPM. It handles two distinct lifecycle modes: capturing a concept that doesn't exist yet (Mode 1), and documenting a fully-built or recently-updated project (Mode 2). It connects directly to the MPM CoWork coordination system in Google Drive (folder structure, Google Docs Wiki V2, and Google Sheets project registry) and to the MPM Gitea instance for repo creation and README pushes. All Drive operations use the Google Workspace MCP exclusively — the local FUSE mount path is never used due to OSError Errno 35 deadlock issues.
| `cowork-repository-update` | Manages the full CoWork project coordination lifecycle. Triggers on: "new skill idea", "I want to build a plugin for X", "let's capture this concept", "add a new project to the registry", "create the entry for this", "document this plugin", "update the wiki", "add to the coordination folder", "set up the project folder", "package the plugin", "we just finished building", "update the registry for". Runs Mode 1 (concept interview) or Mode 2 (document existing build) depending on context. |
6.**Package .skill file** — skill-only: stage into single top-level folder with SKILL.md at root; with server: zip server/ + .mcp.json + plugin.json + SKILL.md; upload to Drive folder
7.**Create or update Wiki Doc** — V2 5-section format; use `create_doc` → `update_drive_file add_parents` → `batch_update_doc`; if updating, prepend changelog row only
8.**Verify all 3 artifacts** in Drive folder before registry write
9.**Update registry** — correct-order insertion; update Version, Drive Folder, Wiki Doc, Last Updated, Notes
10.**Confirm to user** — all artifact links + any manual follow-up flags
**Critical rules:**
- Never write files to the FUSE-mounted Google Drive path — Drive API tools only
- Thin README is worse than no README — pull every tool, every trigger phrase
- For backfill CW-IDs, read all column A values and shift rows at insertion point downward
- Confirm version number before writing any artifacts
| 2026-05-05 | v1.1 | Renamed to CoWork Repository Update. Fixed skill-only .skill packaging: zip must have one top-level folder with SKILL.md at root (not nested under skills/). |
| .skill upload rejected ("Zip must contain exactly one top-level folder") | Stage into `/tmp/[skill-name]-pkg/[skill-name]/`, put SKILL.md directly there, zip the folder |
| README in Git shows a base64 blob instead of markdown | Content was double-encoded. Pass plain markdown text to `create_or_update_file` — the Gitea MCP base64-encodes internally. Re-push the plain text to fix. |
| Drive upload fails with "file not found" on `fileUrl` | The path points at the sandbox `/tmp` or a stale session path. Copy the file to the current session's outputs directory and use that host path. |
| Duplicate CW-XXX folder or registry row after a failed run | Don't restart from scratch — search for existing artifacts first, reuse them, and continue from the first missing one (see "Resuming a partial run" in SKILL.md). |
| Registry cells wiped (Chat Space, Odoo Module) after an update | A full-row write overwrote hand-maintained columns. Restore from sheet version history; use targeted range writes for changed cells only. |
