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"

Files1

1 files · 1.0 KB

Select a file to preview

Overall Score

82/100

Grade

B

Good

Safety

92

Quality

80

Clarity

85

Completeness

72

Summary

A skill for operating across Google Workspace (Drive, Docs, Sheets, Slides) as an integrated workflow surface. It guides agents to find, inspect, summarize, edit, and consolidate shared documents and spreadsheets while maintaining organizational hygiene and avoiding duplicates.

Detected Capabilities

Google Drive search and file discoveryGoogle Docs inspection and text editingGoogle Sheets inspection, tab operations, and range editsGoogle Slides inspection and content editingDocument structure analysis and summarizationDuplicate detection and cleanup workflow

Trigger Keywords

Phrases that MCP clients use to match this skill to user intent.

find planning documentconsolidate spreadsheetsclean up trackermerge duplicate docsimport slides deckgoogle workspace workflow

Use Cases

Find and update an active planning document in place
Consolidate customer lists or trackers across multiple sheets
Clean up and restructure shared spreadsheets
Import and reformat Google Slides decks
Identify and merge duplicate documents or trackers
Generate summaries from Docs, Sheets, or Slides for decision-making

Quality Notes

Clear workflow structure with four well-defined phases (find, inspect, edit, clean)
Good emphasis on inspection before action — reduces blind edits and mistakes
Practical output format (ASSET, CURRENT STATE, ACTION, FOLLOW-UPS) gives agent clear structure for reporting
Use case examples are concrete and distinguish this skill from generic doc editing
Helpful guidance on choosing the smallest tool for each task (Docs vs Sheets vs Slides)
Minor: No explicit guidance on handling large documents or performance constraints
Minor: No mention of permissions issues or what to do if a document is read-only
Minor: Scope around 'stale vs canonical' detection is somewhat subjective — no criteria for deciding when to archive
Minor: No guidance on error handling for failed searches or missing files

Model: claude-haiku-4-5-20251001Analyzed: Apr 20, 2026

Reviews

Add this skill to your library to leave a review.

No reviews yet

Be the first to share your experience.

Version History

v1.1

Content updated

2026-04-20

Latest

v1.0

No changelog

2026-04-12

google-workspace-ops