SkillHub

Skills affaan-m ecc

google-workspace-ops

Use it when:
You need to find a plan, tracker or deck in Google Drive and update, clean up, summarize or import it.
It does:
Searches Drive for the exact file and its duplicates, summarizes its structure, then edits by index in Docs, by tab and range in Sheets, or by slide.
You get:
The edited file and a short report: which asset and why, its state, the action taken and follow-ups like archiving or merging.
Needs:
Google Drive, Docs, Sheets and Slides tools connected to the agent; the skill brings no tools of its own.

It relies on Google Drive, Docs, Sheets and Slides tools the agent already has connected; it brings none of its own.

TL;DR

A working method for Google Workspace files that are part of a larger system, such as trackers, plans, customer lists and decks. Drive is the entry point: the agent locates the exact file, sibling assets, likely duplicates and recent versions, and confirms by title, owner, modified time or folder when several look alike, instead of guessing from filenames. Before changing anything it summarizes the structure, such as tabs, headings or slide count, and decides whether the job is light cleanup or structural surgery, then picks the smallest tool that can do it safely. Edits stay precise: index-aware edits in Docs, explicit tabs and ranges in Sheets, and in Slides a split between content edits and visual cleanup or template migration, rechecked by inspection for layout work. It also points out duplicate trackers, outdated decks and stale copies of canonical docs, and whether each should be archived, merged or renamed. Example requests: condense the active planning doc, show the churn-risk rows in a customer sheet, import a deck into Slides and make it presentable.

Summarizes the skill at d2ef268.

npx skills add https://github.com/affaan-m/ecc --skill google-workspace-ops

skills.sh pageSource on GitHubAll skills from affaan-m/ecc

Total Downloads
5,300 on skills.sh, Nov 9, 2026
Repo stars
299,776 affaan-m/ecc
First seen
May 19, 2026 on skills.sh
Weekly Downloads
440
+69% over the 8 weeks to Nov 9
Weekly values
Week toInstalls
Sep 21261
Sep 28159
Oct 5138
Oct 12228
Oct 19408
Oct 26398
Nov 2467
Nov 9440
Category
category:documents

Office files, notes and suites like Lark and Google Workspace.
Type
type:workflow

A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect
effect:remote

Its own steps change something outside your machine: post, send, deploy, provision, file issues, drive a website, or upload data to a service.
Needs
needs:account

An account, API key or paid plan with an outside service.
Publisher
by:community

Everyone else. Unverified vendor claims default to community.
Topics
documentsspreadsheetsslides
Stack
stack:google-workspace

SKILL.md

From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.

Frontmatter
name: google-workspace-ops
description: Operate across Google Drive, Docs, Sheets, and Slides as one workflow surface for plans, trackers, decks, and shared documents. Use when the user needs to find, summarize, edit, migrate, or clean up Google Workspace assets without dropping to raw tool calls.
metadata:
  origin: ECC

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"