원클릭으로
google-workspace-ops
将 Google 云端硬盘、文档、表格和幻灯片作为一个工作流界面来操作,用于处理计划、追踪器、演示文稿和共享文档。当用户需要查找、总结、编辑、迁移或清理 Google Workspace 资产,而无需使用原始工具调用时使用。
메뉴
将 Google 云端硬盘、文档、表格和幻灯片作为一个工作流界面来操作,用于处理计划、追踪器、演示文稿和共享文档。当用户需要查找、总结、编辑、迁移或清理 Google Workspace 资产,而无需使用原始工具调用时使用。
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.
Orchestrate building a brand-new feature end to end — research, plan, TDD implementation, review, and gated commit — by delegating each phase to the matching ECC agent. Use when adding a capability that does not exist yet.
Orchestrate bootstrapping a working MVP from a design or spec document — ingest the doc, plan thin vertical slices, scaffold the first end-to-end slice, then TDD-implement, review, and gated commit. Use to turn an SDD/PRD into a running starting point.
Orchestrate altering an existing, working feature to new desired behavior — update its tests to the new spec, change the implementation to match, review, and gated commit. Use when behavior is not broken but should be different.
Orchestrate fixing a bug — reproduce it as a failing regression test, fix to green, review, and gated commit — by delegating each phase to the matching ECC agent. Use when existing behavior is broken or wrong.
Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.
| name | google-workspace-ops |
| description | 将 Google 云端硬盘、文档、表格和幻灯片作为一个工作流界面来操作,用于处理计划、追踪器、演示文稿和共享文档。当用户需要查找、总结、编辑、迁移或清理 Google Workspace 资产,而无需使用原始工具调用时使用。 |
| origin | ECC |
此技能用于将共享文档、电子表格和演示文稿作为工作系统进行操作,而不仅仅是孤立地编辑单个文件。
使用 Google Drive 作为入口,然后切换到合适的专业工具:
不要仅凭文件名猜测结构。先检查。
从 Drive 搜索界面开始,定位:
如果多个文档看起来相似,请通过标题、所有者、修改时间或文件夹进行确认。
在进行更改之前:
选择能够安全完成工作的最小工具。
如果请求的工作涉及视觉或布局调整,请通过检查和验证进行迭代,而不是进行一次性的盲目更新。
当文件是更大工作流程的一部分时,还需指出:
使用:
资产
- 文件名
- 类型
- 为何选择此文件
当前状态
- 结构摘要
- 关键问题或阻碍
操作
- 已执行或建议的编辑
后续事项
- 归档 / 合并 / 重复清理 / 下一个待更新文件