Google Workspace Ops

affaan-m/ECC/skills/google-workspace-ops

by affaan-mef648e01899ba3e8dc6371642deaaf64b4477775No license275K starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated 4 days ago

Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.

AI-generated overview

Operates across Google Drive, Docs, Sheets, and Slides to find, inspect, edit, and clean up shared workspace assets.

What it does
This skill guides an agent through working with Google Workspace assets as one workflow surface: locating files in Drive, inspecting their structure, editing Docs, Sheets, and Slides with precision, and cleaning up duplicates or stale files. It produces structured output covering the chosen asset, its current state, actions taken or recommended, and follow-up cleanup. It is instructions only and ships no scripts.
When to use it
Use it when a user needs to find and update a Google Doc, Sheet, or Slides deck in place, consolidate plans, trackers, notes, or customer lists in Drive, restructure a shared spreadsheet, import or repair a deck, or summarize Workspace files for decision-making.
Requirements
Access to Google Drive, Docs, Sheets, and Slides through the agent's available tools; no scripts are included.

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:

text
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

Good 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"

Source and attribution

Source:affaan-m/ECCinskills/google-workspace-opsat commitef648e0

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal