with one click
google-workspace-ops
Google Workspace API操作、Sheets自動化、Gmail統合、およびドキュメント管理。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Menu
Google Workspace API操作、Sheets自動化、Gmail統合、およびドキュメント管理。
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Build a fully automated AI-powered data collection agent for any public source — job boards, prices, news, GitHub, sports, anything. Runs on a schedule, enriches data with a free LLM (Gemini Flash), stores results in Notion/Sheets/Supabase, and learns from user feedback. Runs 100% free on GitHub Actions. Use when the user wants to monitor, collect, or track any public data automatically.
Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or when feedback like "move this, change that" is easier pointed at than typed.
Open plans and HTML artifacts in a local browser canvas where the human annotates elements, chats, and approves or requests changes without leaving the page. Use when presenting a plan for review, or when feedback like "move this, change that" is easier pointed at than typed.
Instinct-based learning system that observes sessions via hooks, creates atomic instincts with confidence scoring, and evolves them into skills/commands/agents. v2.1 adds project-scoped instincts to prevent cross-project contamination.
基于本能的学习系统,通过钩子观察会话,创建带置信度评分的原子本能,并将其进化为技能/命令/代理。v2.1版本增加了项目范围的本能,以防止跨项目污染。
任意の自動コンパクションではなく、タスクフェーズを通じてコンテキストを保持するための論理的な間隔での手動コンパクションを提案します。
| name | google-workspace-ops |
| description | Google Workspace API操作、Sheets自動化、Gmail統合、およびドキュメント管理。 |
| origin | ECC |
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