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 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"
1---2name: google-workspace-ops3description: Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents.4---56# Google Workspace Ops78This skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.910## When to Use1112- User needs to find a doc, sheet, or deck and update it in place13- Consolidating plans, trackers, notes, or customer lists stored in Google Drive14- Cleaning or restructuring a shared spreadsheet15- Importing, repairing, or reformatting a Google Slides deck16- Producing summaries from Docs, Sheets, or Slides for decision-making1718## Preferred Tool Surface1920Use Google Drive as the entry point, then switch to the right specialist:2122- Google Docs for text-heavy docs23- Google Sheets for tabular work, formulas, and charts24- Google Slides for decks, imports, template migration, and cleanup2526Do not guess structure from filenames alone. Inspect first.2728## Workflow2930### 1. Find the asset3132Start with the Drive search surface to locate:3334- the exact file35- sibling assets36- likely duplicates37- recently modified versions3839If several documents look similar, confirm by title, owner, modified time, or folder.4041### 2. Inspect before editing4243Before making changes:4445- summarize current structure46- identify tabs, headings, or slide count47- detect whether the task is local cleanup or structural surgery4849Pick the smallest tool that can safely perform the work.5051### 3. Edit with precision5253- For Docs: use index-aware edits, not vague rewrites54- For Sheets: operate on explicit tabs and ranges55- For Slides: distinguish content edits from visual cleanup or template migration5657If the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.5859### 4. Keep the working system clean6061When the file is part of a larger workflow, also surface:6263- duplicate trackers64- outdated decks65- stale docs vs canonical docs66- whether the asset should be archived, merged, or renamed6768## Output Format6970Use:7172```text73ASSET74- file name75- type76- why this is the right file7778CURRENT STATE79- structure summary80- key problems or blockers8182ACTION83- edits made or recommended8485FOLLOW-UPS86- archive / merge / duplicate cleanup / next file to update87```8889## Good Use Cases9091- "Find the active planning doc and condense it"92- "Clean up this customer spreadsheet and show me the churn-risk rows"93- "Import this deck into Slides and make it presentable"94- "Find the current tracker, not the stale duplicate"
Affaan Mustafa