Google Workspace Ops
Run Google Drive, Docs, Sheets, and Slides as one coordinated workflow—find assets, inspect structure, then edit trackers, plans, and decks without raw MCP guessing.
Overview
Google Workspace Ops is an agent skill most often used in Build PM (also Validate scoping and Grow lifecycle trackers) that coordinates Drive search, inspection, and edits across Docs, Sheets, and Slides.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill google-workspace-opsWhat is this skill?
- Treats Drive as entry point, then routes to Docs, Sheets, or Slides specialists by asset type.
- Find → inspect → edit workflow: search duplicates, confirm owner/modified time before mutating shared files.
- Supports consolidation, cleanup, import/repair for Slides, and spreadsheet restructuring.
- Produces summaries from Docs, Sheets, or Slides for decisions instead of silent single-file edits.
- Explicit anti-pattern: do not guess structure from filenames alone—inspect tabs and headings first.
Adoption & trust: 3.2k installs on skills.sh; 210k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your roadmap and customer data are scattered across Google files and the agent keeps editing the wrong duplicate or breaking spreadsheet structure.
Who is it for?
Solopreneurs who run planning, support lists, and decks entirely in Google Workspace with agent-assisted maintenance.
Skip if: Builders who need only local markdown or Notion with no Google API access.
When should I use this skill?
User needs to find, summarize, edit, migrate, or clean up Google Drive, Docs, Sheets, or Slides assets as one workflow.
What do I get? / Deliverables
You get confirmed asset selection, structural summaries, and in-place updates across Docs, Sheets, and Slides using a single repeatable ops workflow.
- Updated Workspace files
- Structural summary before/after edits
- Decision-oriented summaries from Docs/Sheets/Slides
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Shared docs and spreadsheets are where solo builders plan and track the product—PM shelf fits first structured use, with heavy overlap in validate and grow. PM subphase covers roadmaps, trackers, customer lists, and decision summaries that live in Workspace rather than in-repo markdown alone.
Where it fits
Locate the latest PRD doc among duplicates and summarize headings before committing to a build scope.
Restructure a multi-tab sprint tracker with formulas intact after inspecting sheet layout.
Import or reformat a pitch Slides deck after confirming it is the recently modified owner copy.
Consolidate customer issue lists from sibling spreadsheets into one cleaned master sheet.
How it compares
Use this workflow skill instead of chaining disconnected one-off Google tool calls without Drive-level discovery.
Common Questions / FAQ
Who is google-workspace-ops for?
Solo builders and small teams who treat Google Drive as their plan-of-record and want agents to find and update the right doc, sheet, or deck safely.
When should I use google-workspace-ops?
In Validate when scoping and consolidating planning docs; in Build when updating trackers and shared specs; in Grow when cleaning customer or content spreadsheets; in Launch when fixing or importing slide decks.
Is google-workspace-ops safe to install?
It implies Google API access to your files—review the Security Audits panel on this page and limit OAuth scopes before enabling on production Shared Drives.
SKILL.md
READMESKILL.md - Google Workspace Ops
# 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"