From ecc
Operates across Google Drive, Docs, Sheets, and Slides as a unified workflow surface for finding, summarizing, editing, migrating, or cleaning up assets.
How this skill is triggered — by the user, by Claude, or both
Slash command
/ecc:google-workspace-opsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
This skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.
This skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.
Use Google Drive as the entry point, then switch to the right specialist:
Do not guess structure from filenames alone. Inspect first.
Start with the Drive search surface to locate:
If several documents look similar, confirm by title, owner, modified time, or folder.
Before making changes:
Pick the smallest tool that can safely perform the work.
If the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.
When the file is part of a larger workflow, also surface:
Use:
ASSET
- file name
- type
- why this is the right file
CURRENT STATE
- structure summary
- key problems or blockers
ACTION
- edits made or recommended
FOLLOW-UPS
- archive / merge / duplicate cleanup / next file to update
npx claudepluginhub affaan-m/ecc --plugin ecc374plugins reuse this skill
First indexed Jun 3, 2026
Showing the 6 earliest of 374 plugins
Operates across Google Drive, Docs, Sheets, and Slides as a unified workflow surface for finding, summarizing, editing, migrating, or cleaning up assets.
Operates Google Workspace assets (Drive, Docs, Sheets, Slides) as workflow surfaces for finding, summarizing, editing, migrating, or cleaning files.
Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, etc.) via MCP tools or CLI. Activates on email, file, calendar, or document requests.