Google Workspace Ops

Operate across Google Drive, Docs, Sheets, and Slides as unified workflow. Find, summarize, edit, migrate, or clean shared documents. Trigger phrases: find d...

Security Scan

The skill's stated purpose (operating on Drive/Docs/Sheets/Slides) aligns with the single credential it requests, and it is an instruction-only skill with no install steps, but provenance is unknown and there are a few minor configuration and autonomy considerations to review before use.

Purpose & Capability

Name/description (Google Workspace operations) align with the required environment variable (GOOGLE_APPLICATION_CREDENTIALS). No unrelated env vars, binaries, or config paths are requested that would be out of scope.

Instruction Scope

SKILL.md is high-level guidance for finding/inspecting/editing Workspace assets and does not instruct reading unrelated local files or transmitting data to unexpected endpoints. It is vague about exact API calls or how credentials are used, which is acceptable for an instruction-only skill but leaves implementation details to the agent.

Install Mechanism

No install spec and no code files — lowest-risk delivery model. Nothing is downloaded or written to disk by the skill package itself.

Credentials

Only GOOGLE_APPLICATION_CREDENTIALS is required, which is proportionate to Google Workspace access. However the skill metadata does not designate a primaryEnv and the service-account JSON referenced by that env var can grant broad access depending on how it's configured — least-privilege credentials are recommended.

Persistence & Privilege

always is false (good). The skill allows normal autonomous invocation (disable-model-invocation is false by default). That is standard but means an agent with access to GOOGLE_APPLICATION_CREDENTIALS could perform operations without the user re-confirming each action; consider this when granting credentials.

Assessment

This instruction-only skill is coherent for Google Workspace maintenance, but verify before installing: 1) Only provide a dedicated service account JSON via GOOGLE_APPLICATION_CREDENTIALS with the minimal permissions needed (Drive, Docs, Sheets, Slides APIs) — do not use owner or broad project credentials. 2) Prefer a scoped service account and/or domain-limited access; audit and rotate the key regularly. 3) Because the agent can be invoked autonomously by default, decide whether you want to allow automated edits: disable autonomous invocation or require explicit confirmation if available. 4) Because the skill's source/homepage are unknown, treat it as unreviewed: test in a low-risk account/folder first and monitor Drive audit logs for unexpected activity. 5) If you need higher assurance, ask the publisher for provenance, the exact auth model they expect, or a primaryEnv declaration pointing to GOOGLE_APPLICATION_CREDENTIALS.

Operate shared docs, spreadsheets, and decks as working systems.

When to Use

• Finding and updating a doc in place
• Consolidating plans, trackers, or notes across files
• Cleaning or restructuring a shared spreadsheet
• Importing, repairing, or reformatting slides
• Summarizing Docs, Sheets, or Slides for decisions

Workflow

1. Find the Asset

Start with Google Drive search to locate:

• The exact file
• Sibling or duplicate assets
• Recently modified versions

Confirm by title, owner, modified time, or folder.

2. Inspect Before Editing

Summarize current structure:

• Tabs, headings, slide count
• Whether task is cleanup or structural surgery
• Pick the smallest tool that works safely

3. Edit with Precision

• Docs — Use index-aware edits, not vague rewrites
• Sheets — Operate on explicit tabs and ranges
• Slides — Distinguish content edits from layout/template changes

Iterate with inspection → verify instead of one blind update.

4. Keep Systems Clean

Surface:

• Duplicate trackers or decks
• Stale vs canonical docs
• Archive/merge candidates

Output Format

ASSET: [name, type, why this one]
CURRENT STATE: [structure, key problems]
ACTION: [edits made or recommended]
FOLLOW-UPS: [archive, merge, clean, next steps]

Good Use Cases

• "Find the active planning doc and condense it"
• "Clean up the customer spreadsheet and show churn-risk rows"
• "Import this deck into Slides and make it presentable"
• "Find the current tracker, not the stale duplicate"