How do I install the Managing Google Workspace skill?

Run npx skillmds@latest add gitwalter/managing-google-workspace in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Managing Google Workspace safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: executes scripts, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Managing Google Workspace?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Managing Google Workspace free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Managing Google Workspace?

gitwalter (@gitwalter) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Managing Google Workspace by gitwalter

Name: Managing Google Workspace
Rating: 4.666666666666667 (3 reviews)
Author: gitwalter

File contents

Capability Manifest: Google Workspace Mastery

This blueprint provides the procedural truth for managing the user's digital ecosystem with precision and beauty.

Process

Follow these procedures to interact with Google Workspace components:

Procedure 1: Precise Information Retrieval (Drive & Gmail)

Query Decomposition: Never run a broad search. Use specific operators:
- Gmail: from:name, has:attachment, after:YYYY/MM/DD.
- Drive: name contains 'X', mimeType = 'application/pdf'.
Metadata Audit: When retrieving information, always check the modifiedTime and lastModifyingUser to ensure you are viewing the current Truth.

Procedure 2: Axiomatic Scheduling (Calendar)

Conflict Check: Run list_events for the target day and the days surrounding it to identify context.
Buffer Implementation: When creating an event, check the end time of the previous event. If the gap is <15m, suggest a later start time.
Description Truth: Every event must have a clear description, a location (or link), and relevant context attached.

Procedure 3: High-Fidelity Communication (Gmail)

Contextual Grounding: Before drafting an email, search the thread history to maintain continuity.
Drafting Gate:
- Use clear, action-oriented subject lines.
- Use professional, context-aware greetings.
- Include a clear "Call to Action" or "Closure Statement."
Attachment Protocol: Use gmail.send_email with the attachments argument to include local files or drive documents (after downloading).
Verification: For sensitive emails, present the draft alongside a "Context Summary" (e.g., "This email addresses the points raised by X on Tuesday regarding Y").

Process (Fail-State & Recovery)

Symptom	Probable Cause	Recovery Operation
Search Zero-Result	Too restrictive query or expired token.	Broaden the search; check for typos in the query; trigger a permission/auth check if necessary.
Event Conflict	Simultaneous booking.	Propose "Alternative Intelligence": Provide 3 distinct time slots that satisfy all axioms (including buffers).
Auth Error	OAuth key missing or expired.	Ensure `gcp-oauth.keys.json` is in the workspace root and re-authenticate via browser.

Prerequisites

Action	Tool / Command
Find Email	`gmail.search_emails(query="...")`
Send Email	`gmail.send_email(to="...", subject="...", content="...", attachments=["..."])`
Book Meeting	`google-calendar.list_events(...)`
Organize File	`gdrive.list_files(q="...")`

When to Use

Use this blueprint whenever managing personal or professional operations involving the Google Workspace ecosystem. It is the authoritative source for "How we assist" vs "What Google Workspace is."

Best Practices

Follow the system axioms (A1-A5)
Ensure all changes are verifiable
Maintain clean label structures using gmail.create_label and gmail.list_email_labels.

---name: managing-google-workspacedescription: Tactical Blueprint for managing Google Workspace (Drive, Gmail, Calendar). Focuses on prescriptive search, organization, and high-fidelity communication.---# Capability Manifest: Google Workspace MasteryThis blueprint provides the **procedural truth** for managing the user's digital ecosystem with precision and beauty.## ProcessFollow these procedures to interact with Google Workspace components:### Procedure 1: Precise Information Retrieval (Drive & Gmail)1. **Query Decomposition**: Never run a broad search. Use specific operators: - *Gmail*: `from:name`, `has:attachment`, `after:YYYY/MM/DD`. - *Drive*: `name contains 'X'`, `mimeType = 'application/pdf'`.2. **Metadata Audit**: When retrieving information, always check the `modifiedTime` and `lastModifyingUser` to ensure you are viewing the current Truth.### Procedure 2: Axiomatic Scheduling (Calendar)1. **Conflict Check**: Run `list_events` for the target day *and* the days surrounding it to identify context.2. **Buffer Implementation**: When creating an event, check the end time of the previous event. If the gap is <15m, suggest a later start time.3. **Description Truth**: Every event must have a clear description, a location (or link), and relevant context attached.### Procedure 3: High-Fidelity Communication (Gmail)1. **Contextual Grounding**: Before drafting an email, search the thread history to maintain continuity.2. **Drafting Gate**: - Use clear, action-oriented subject lines. - Use professional, context-aware greetings. - Include a clear "Call to Action" or "Closure Statement."3. **Attachment Protocol**: Use `gmail.send_email` with the `attachments` argument to include local files or drive documents (after downloading).4. **Verification**: For sensitive emails, present the draft alongside a "Context Summary" (e.g., "This email addresses the points raised by X on Tuesday regarding Y").## Process (Fail-State & Recovery)| Symptom | Probable Cause | Recovery Operation || :--- | :--- | :--- || **Search Zero-Result** | Too restrictive query or expired token. | Broaden the search; check for typos in the query; trigger a permission/auth check if necessary. || **Event Conflict** | Simultaneous booking. | Propose "Alternative Intelligence": Provide 3 distinct time slots that satisfy all axioms (including buffers). || **Auth Error** | OAuth key missing or expired. | Ensure `gcp-oauth.keys.json` is in the workspace root and re-authenticate via browser. |## Prerequisites| Action | Tool / Command || :--- | :--- || Find Email | `gmail.search_emails(query="...")` || Send Email | `gmail.send_email(to="...", subject="...", content="...", attachments=["..."])` || Book Meeting | `google-calendar.list_events(...)` || Organize File | `gdrive.list_files(q="...")` |## When to UseUse this blueprint whenever managing personal or professional operations involving the Google Workspace ecosystem. It is the authoritative source for "How we assist" vs "What Google Workspace is."## Best Practices- Follow the system axioms (A1-A5)- Ensure all changes are verifiable- Maintain clean label structures using `gmail.create_label` and `gmail.list_email_labels`.

Frequently asked questions

Managing Google Workspace