Google Workspace API操作、Sheets自動化、Gmail統合、およびドキュメント管理。
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
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/google-workspace-ops · pinned to the source commit
git clone https://github.com/affaan-m/ECC.git
cd ECC
git checkout d8409a4b0813771235555e32e3d8046a73988bfa
mkdir -p ".claude/skills/google-workspace-ops"
cp -r "docs/ja-JP/skills/google-workspace-ops" ".claude/skills/google-workspace-ops"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit d8409a4b0813. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.