Google Workspace Ops
SkillFiles & storagegoogle-workspace-ops is a skill that lets an AI agent work across Google Drive, Docs, Sheets, and Slides as one workflow surface. It guides the agent to find files through Drive search, inspect their structure, and then make precise edits with the right app-specific tooling. It is aimed at plans, trackers, decks, and shared documents that need finding, summarizing, editing, migrating, or cleaning up.
Available today. Use it from your connected AI after setup.
No other account needed.
Have an agent setup that supports loading skills and has access to Google Drive, Docs, Sheets, and Slides tooling.
Then ask your AI: use the Google Workspace Ops skill
What your AI can do with it
- Locate files, duplicates, and recently modified versions via Google Drive search
- Summarize the structure of Docs, Sheets, or Slides before any edit
- Make index-aware edits in Google Docs and range-based edits in Google Sheets
- Import, repair, reformat, and clean up Google Slides decks
- Flag duplicate trackers, stale docs, and candidates for archiving or merging
- Produce summaries from Docs, Sheets, or Slides for decision-making
Getting started
- Have an agent setup that supports loading skills and has access to Google Drive, Docs, Sheets, and Slides tooling.
- Add the google-workspace-ops skill to the agent's available skills.
- Ask the agent to find, summarize, edit, migrate, or clean up a Google Workspace file.
- Review the agent's output, which reports the asset chosen, its current state, actions taken, and suggested follow-ups.
What this skill tells your AI
The instructions your AI receives, as published by affaan-m/ecc in skills/google-workspace-ops/SKILL.md and read by ahel’s review.
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"
Signals
- GitHub stars
- 268k
- Forks
- 40k
- Last commit
- Sep 2026
ahel review
S4info
community integration, published by affaan-m, not google
Automated review, not a security audit. Ruleset v1+k2.
Questions
- When should this skill be used?
- When a user needs to find, summarize, edit, migrate, or clean up Google Workspace assets, such as updating a planning doc, cleaning a shared spreadsheet, or making an imported deck presentable, without dropping to raw tool calls.
- How does it avoid editing the wrong file?
- It starts with Drive search, confirms the correct file by title, owner, modified time, or folder when several look similar, and inspects the file's structure before making any changes.
Advanced
- Item type
- skill
- Key
google-workspace-ops-affaan-m- Source
- github.com/affaan-m/ecc