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

88

Quality

80

Clarity

85

Completeness

74

Summary

A skill for operating across Google Workspace assets (Docs, Sheets, Slides) as an integrated workflow surface. It guides agents to find, inspect, and edit shared documents in place rather than manipulating files in isolation, with emphasis on understanding structure before making changes and maintaining system cleanliness across duplicates and related assets.

Detected Capabilities

Google Drive search and metadata inspectionGoogle Docs content reading and text editsGoogle Sheets range operations and formula managementGoogle Slides content and layout modificationAsset discovery and duplicate detection

Trigger Keywords

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

find and consolidate docsclean up shared sheetsimport and reformat deckslocate active trackerdeduplicate drive assetssummarize workspace documents

Use Cases

Finding and updating active planning documents within organizational systems
Consolidating and cleaning shared spreadsheets for data accuracy and compliance
Importing and reformatting presentation decks across Slides
Identifying and deduplicating stale versions of tracked assets
Producing summaries from multi-document workflows for decision-making

Quality Notes

Clear workflow hierarchy (find → inspect → edit → maintain) that teaches deliberate, verification-driven operations rather than blind bulk edits
Practical output format (ASSET / CURRENT STATE / ACTION / FOLLOW-UPS) that keeps agents accountable for reasoning
Strong scope boundaries: explicitly recommends inspecting structure before changes and picking the 'smallest tool that can safely perform the work'
Good coverage of shared-system nuances: duplicates, staleness, archive vs. merge decisions that go beyond single-file edits
Emphasizes incremental iteration for visual/layout-sensitive work, reducing risk of destructive one-shot rewrites
Well-organized with clear 'When to Use' section and preferred tool surface guidance
No error handling or edge case coverage documented (e.g., permission errors, locked files, corrupt sheets)
Limited guidance on scaling to large datasets or handling deeply nested folder hierarchies

Model: claude-haiku-4-5-20251001Analyzed: Jul 14, 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.2

Content updated

2026-07-14

Latest

v1.1