Run any Skill in Manus with one click

google-workspace

Stars3

Forks0

UpdatedJuly 7, 2026 at 18:58

Use when working with André's self-hosted Google Workspace MCP (the `google-workspace` plugin) — driving Calendar, Gmail, Drive, Docs, Sheets, Slides, Forms, Tasks, Chat, or Contacts via the `mcp__plugin_maccing_workspace__*` tools, OR setting up / troubleshooting its OAuth (first-run consent, 7-day test-mode re-auth, credential storage). Covers the account-isolation rule (never use the `mcp__claude_ai_*` Google connectors — different account).

Installation

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.

Run Skill in Manus

Source

andredezzy

andredezzy/maccing

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

4 files

SKILL.md

readonly

name

google-workspace

description

Google Workspace

Self-hosted Google Workspace MCP server for Claude Code, built on workspace-mcp==1.21.2 (PyPI package, taylorwilsdon/google_workspace_mcp). Runs as a per-session stdio process — no daemon, no daily re-authorization. Supports Calendar, Gmail, Drive, Docs, Sheets, Slides, Forms, Tasks, Chat, and Contacts.

Account-isolation rule — the single most important rule

Always use mcp__plugin_maccing_workspace__*; NEVER the mcp__claude_ai_Google_Calendar__* / mcp__claude_ai_Gmail__* / mcp__claude_ai_Google_Drive__* connectors — they are wired to a different, unrelated Google account (nicolas1120201@gmail.com). The user's Workspace account is andrevcv1@gmail.com.

References — load on demand

Task	Reference
Google Cloud setup, enabling APIs, OAuth client, publishing consent screen, secrets, tool tiers	`references/setup.md`
First-run browser flow, credential storage, no-daily-reauth rationale, reset procedure	`references/auth-and-credentials.md`
Tool inventory by service, common workflows, parameter gotchas, user defaults	`references/tools.md`

More from this repository

same repository

notion

andredezzy/maccing

Use BEFORE the first Notion read or write on ANY task touching Notion — the Notion API or its MCP — however trivial: a one-field rename, a page icon/cover, adding one row, a single select color, even just reading a page's title. Covers creating, editing, querying, or moving databases, data sources, pages, views (table/board/gallery/calendar/timeline/list/chart/dashboard/map/form), formulas, rollups, relations, blocks, icons, covers; and any Notion API/MCP error (validation_error, pagination, permission, 400/409). MANDATORY, never optional — "small", "quick", "obvious", or "well-understood" is the exact trap: every Notion edit still owes this skill's mandatory first steps (the ancestral-AGENTS.md sweep + house-style match) that a direct quick edit silently skips and corrupts. If the work touches Notion at all, load this FIRST.

2026-07-173

naming

andredezzy/maccing

Use when naming anything — files, functions, types, variables, enum members — or choosing between a boolean, string union, and enum for a set of states. Triggers: a status/state field, vague or abbreviated names, single-letter values, Base-prefixed classes, Contract-suffixed interfaces, casing questions, PascalCase filenames, a name that covers only part of what the function does, a mechanism or pattern you invented a name for (a *Limiter/*Pool/*Gate) when the trade may already name it.

2026-07-113

researching-before-coding

andredezzy/maccing

Use when about to write code against any external library, API, framework, or tool; when hitting an error, incompatibility, or unfamiliar technology; when introducing or naming a mechanism that solves a recognized problem (a limiter, pool, queue, retry/isolation primitive) even when its code is pure internal logic; before proposing a fix or presenting a design. Especially when confident from memory, under time pressure, when the API "is well known", or when a mechanism "is just internal logic".

2026-07-113

organizing-code

andredezzy/maccing

Use when creating, splitting, or moving files; defining error classes or writing catch blocks; adding helpers, wrappers, or utils; structuring test files; or deciding where types, env vars, or server/client context live. Triggers: a file doing several things, circular imports, barrel files, a function that only forwards its arguments, a buildX(config) helper re-reading inputs a component already receives, an empty catch, a dense wall of code, inline multi-property object types, section-divider comments.

2026-07-113

composing-ui

andredezzy/maccing

Use when creating any UI component, page, route, or layout, adding a prop to an existing one, wiring data fetching for a screen (prefetch, hydration, suspense, skeletons), or touching a component that has grown large — React or any component framework — plus forms, styling, and labels. Triggers: a prop toggling a section, a god component, dot-notation sub-components (Card.Header), raw inputs with hand-rolled validation, title-case labels, "just one more prop", a page marked "use client", a dataset passed as a prop to a client component, a route-level loading file, a page re-checking auth, a client-side re-parse of search params.

2026-07-103

modeling-domains

andredezzy/maccing

Use when defining domain types, database or validation schemas, config shapes, wire payloads, or translation/message trees; when adding a domain type, union member, registry, or dispatcher; when data is flat, joined by ID references, duplicated across fields, or its nesting does not match the real-world thing it describes. Distinct from glossary-style domain-modeling: this skill dictates STRUCTURE — isomorphism, containment, registries.

2026-07-073

name

google-workspace

description

Google Workspace

Account-isolation rule — the single most important rule

References — load on demand

Task	Reference
Google Cloud setup, enabling APIs, OAuth client, publishing consent screen, secrets, tool tiers	`references/setup.md`
First-run browser flow, credential storage, no-daily-reauth rationale, reset procedure	`references/auth-and-credentials.md`
Tool inventory by service, common workflows, parameter gotchas, user defaults	`references/tools.md`