
This treats Google Workspace like a working system instead of isolated files. It starts with Drive search to find the right doc, sheet, or deck, inspects structure before touching anything, then makes precise edits using the appropriate app surface. The workflow pushes you to identify duplicates, stale versions, and cleanup opportunities instead of just answering the immediate request. Good for consolidating scattered trackers, reformatting imported decks, or finding the canonical planning doc when three similar files exist. The structured output format keeps you honest about what changed and what still needs attention. Most useful when your Workspace is messy and you need someone to navigate it like they actually work there.
$ npx -y skills add affaan-m/everything-claude-code --skill google-workspace-ops --agent claude-codeInstalls into .claude/skills of the current project.
This skill is for operating shared docs, spreadsheets, and decks as working systems, not just editing one file in isolation.
Use Google Drive as the entry point, then switch to the right specialist:
Do not guess structure from filenames alone. Inspect first.
Start with the Drive search surface to locate:
If several documents look similar, confirm by title, owner, modified time, or folder.
Before making changes:
Pick the smallest tool that can safely perform the work.
If the requested work is visual or layout-sensitive, iterate with inspection and verification instead of one giant blind update.
When the file is part of a larger workflow, also surface:
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
Sponsors