
Google Workspace Ops
- 1.4k installs
- 238k repo stars
- Updated August 5, 2026
- affaan-m/ecc
This is a copy of google-workspace-ops by affaan-m - installs and ranking accrue to the original listing.
google-workspace-ops is an agent skill that operates Google Drive, Docs, Sheets, and Slides as a unified workflow surface for finding, updating, summarizing, cleaning, and migrating living documents for developers managi
About
google-workspace-ops is an ECC skill for treating Google Workspace as an integrated workflow system rather than editing isolated files. It uses Google Drive as the entry point, then routes work to Docs, Sheets, or Slides for in-place updates, consolidation, restructuring, import repair, and decision-ready summaries. Developers reach for google-workspace-ops when locating shared plans or customer lists in Drive, cleaning messy spreadsheets, reformatting slide decks, or producing summaries from living documents and trackers. The skill also covers Sheets automation and Gmail integration per its manifest. It fits teams whose operational truth lives in Google Workspace instead of a dedicated project database.
- Unified entry via Google Drive search before switching to Docs, Sheets, or Slides
- Always inspect and summarize structure before any edit or migration
- Handles find, update-in-place, consolidate, clean, import, repair, reformat, and produce summaries
- Works across plans, trackers, customer lists, decks, and shared documents as living systems
Google Workspace Ops by the numbers
- 1,361 all-time installs (skills.sh)
- +85 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill google-workspace-opsAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 1.4k |
|---|---|
| repo stars | ★ 238k |
| Last updated | August 5, 2026 |
| Repository | affaan-m/ecc ↗ |
How do you automate updates across Google Workspace docs?
Treat Google Drive, Docs, Sheets, and Slides as a unified workflow surface for finding, updating, summarizing, cleaning, and migrating living documents and trackers.
Who is it for?
Developers or tech leads whose team plans, trackers, and customer lists live in Google Drive and need API-driven batch updates or cleanup.
Skip if: Teams standardized on Notion, Confluence, or local Markdown repos without Google Workspace API access.
When should I use this skill?
User needs to find, update, consolidate, clean, reformat, or summarize Google Docs, Sheets, or Slides in Drive.
What you get
Updated Docs and Sheets, restructured slide decks, consolidated trackers, and decision-ready document summaries.
- Updated shared spreadsheets
- Consolidated document summaries
- Reformatted slide decks
By the numbers
- Covers 4 Google Workspace apps: Drive, Docs, Sheets, and Slides
Files
Google Workspace Ops
This skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.
When to Use
- User needs to find a doc, sheet, or deck and update it in place
- Consolidating plans, trackers, notes, or customer lists stored in Google Drive
- Cleaning or restructuring a shared spreadsheet
- Importing, repairing, or reformatting a Google Slides deck
- Producing summaries from Docs, Sheets, or Slides for decision-making
Preferred Tool Surface
Use Google Drive as the entry point, then switch to the right specialist:
- Google Docs for text-heavy docs
- Google Sheets for tabular work, formulas, and charts
- Google Slides for decks, imports, template migration, and cleanup
Do not guess structure from filenames alone. Inspect first.
Workflow
1. Find the asset
Start with the Drive search surface to locate:
- the exact file
- sibling assets
- likely duplicates
- recently modified versions
If several documents look similar, confirm by title, owner, modified time, or folder.
2. Inspect before editing
Before making changes:
- summarize current structure
- identify tabs, headings, or slide count
- detect whether the task is local cleanup or structural surgery
Pick the smallest tool that can safely perform the work.
3. Edit with precision
- For Docs: use index-aware edits, not vague rewrites
- For Sheets: operate on explicit tabs and ranges
- For Slides: distinguish content edits from visual cleanup or template migration
If the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.
4. Keep the working system clean
When the file is part of a larger workflow, also surface:
- duplicate trackers
- outdated decks
- stale docs vs canonical docs
- whether the asset should be archived, merged, or renamed
Output Format
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 updateGood Use Cases
- "Find the active planning doc and condense it"
- "Clean up this customer spreadsheet and show me the churn-risk rows"
- "Import this deck into Slides and make it presentable"
- "Find the current tracker, not the stale duplicate"
Related skills
How it compares
Pick google-workspace-ops over generic document skills when operational data already lives in Google Drive and needs API-driven batch maintenance.
FAQ
Which Google apps does google-workspace-ops cover?
google-workspace-ops operates Google Drive as the entry point and works across Docs, Sheets, and Slides for finding, updating, summarizing, cleaning, and migrating shared documents and trackers.
When should developers use google-workspace-ops?
google-workspace-ops fits when shared plans, customer lists, or trackers live in Google Drive and need in-place updates, spreadsheet restructuring, deck repair, or summary generation rather than isolated one-file edits.