Install
$ agentstack add skill-affaan-m-ecc-google-workspace-ops ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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"
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: affaan-m
- Source: affaan-m/ECC
- License: MIT
- Homepage: https://ecc.tools
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.