google-admin-automation
Automate Google Workspace Admin tasks via Rube MCP (Composio): manage users, groups, memberships, suspend accounts, create users, add aliases. Always search tools first for current schemas.
What this skill does
# Google Workspace Admin Automation via Rube MCP Manage Google Workspace users, groups, memberships, and organizational settings programmatically using Rube MCP (Composio). **Toolkit docs**: [composio.dev/toolkits/google_admin](https://composio.dev/toolkits/google_admin) ## Prerequisites - Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_admin` - Google Workspace admin privileges for the authenticated account - Always call `RUBE_SEARCH_TOOLS` first to get current tool schemas ## Setup **Get Rube MCP**: Add `https://rube.app/mcp` as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `google_admin` 3. If connection is not ACTIVE, follow the returned auth link to complete setup 4. Confirm connection status shows ACTIVE before running any workflows ## Core Workflows ### 1. List All Users Use `GOOGLE_ADMIN_LIST_USERS` to retrieve Google Workspace users with optional filtering and pagination. ``` Tool: GOOGLE_ADMIN_LIST_USERS Parameters: - customer: Customer ID or "my_customer" (default) - domain: Domain to list users from - query: Filter string (e.g., "orgName=Engineering", "isSuspended=false") - max_results: Maximum results (1-500, default 100) - order_by: Sort by "email", "givenName", or "familyName" - sort_order: "ASCENDING" or "DESCENDING" - page_token: Pagination token ``` ### 2. Create a New User Use `GOOGLE_ADMIN_CREATE_USER` to provision a new Google Workspace account. ``` Tool: GOOGLE_ADMIN_CREATE_USER Parameters: - primary_email (required): User's email (e.g., "[email protected]") - given_name (required): First name - family_name (required): Last name - password (required): Password meeting domain requirements - org_unit_path: Organizational unit (default: "/") - change_password_at_next_login: Force password change (default: true) - recovery_email: Recovery email address - recovery_phone: Recovery phone number - suspended: Whether account starts suspended (default: false) ``` ### 3. List and Manage Groups Use `GOOGLE_ADMIN_LIST_GROUPS` to list groups, and `GOOGLE_ADMIN_CREATE_GROUP` to create new ones. ``` Tool: GOOGLE_ADMIN_LIST_GROUPS Parameters: - customer: "my_customer" (default) - domain: Filter by domain - query: Filter (e.g., "name=Engineering*") - max_results: Max results (1-200) - order_by: Sort by "email" - page_token: Pagination token Tool: GOOGLE_ADMIN_CREATE_GROUP Parameters: - email (required): Group email address (e.g., "[email protected]") - name (required): Display name (e.g., "Engineering Team") - description: Group purpose description ``` ### 4. Add Users to Groups Use `GOOGLE_ADMIN_ADD_USER_TO_GROUP` to manage group membership. ``` Tool: GOOGLE_ADMIN_ADD_USER_TO_GROUP Parameters: - group_key (required): Group email or ID - user_key (required): User email or ID to add - role: "MEMBER" (default), "MANAGER", or "OWNER" ``` ### 5. Suspend or Unsuspend Users Use `GOOGLE_ADMIN_SUSPEND_USER` to toggle user account suspension. ``` Tool: GOOGLE_ADMIN_SUSPEND_USER Parameters: - user_key (required): User's email or unique ID - suspended: true to suspend, false to unsuspend (default: true) - suspension_reason: Reason for suspension (optional) ``` ### 6. Get User or Group Details Use `GOOGLE_ADMIN_GET_USER` or `GOOGLE_ADMIN_GET_GROUP` to retrieve detailed information. ``` Tool: GOOGLE_ADMIN_GET_USER Parameters: - user_key (required): User's email or unique ID Tool: GOOGLE_ADMIN_GET_GROUP Parameters: - group_key (required): Group's email or unique ID ``` ## Common Patterns - **Onboarding workflow**: Use `GOOGLE_ADMIN_CREATE_USER` to provision the account, then `GOOGLE_ADMIN_ADD_USER_TO_GROUP` to add them to relevant groups. - **Offboarding workflow**: Use `GOOGLE_ADMIN_SUSPEND_USER` to disable access, or `GOOGLE_ADMIN_DELETE_USER` for permanent removal. - **Audit group membership**: Use `GOOGLE_ADMIN_LIST_GROUPS` to find groups, then `GOOGLE_ADMIN_LIST_GROUP_MEMBERS` to review members. - **Bulk user management**: List users with `GOOGLE_ADMIN_LIST_USERS` and filter queries, then iterate for updates. - **Add email aliases**: Use `GOOGLE_ADMIN_ADD_USER_ALIAS` to add alternative email addresses for a user. - **Look up user details**: Use `GOOGLE_ADMIN_GET_USER` to retrieve full profile information before making changes. ## Known Pitfalls - **Admin privileges required**: All tools require the authenticated user to have Google Workspace administrator privileges. Non-admin accounts will receive permission errors. - **Delete is permanent**: `GOOGLE_ADMIN_DELETE_USER` permanently removes a user account. This action cannot be undone. - **user_key accepts email or ID**: The `user_key` parameter accepts both the user's primary email address and their unique numeric user ID. - **Group membership replaces**: When adding to groups, the `role` parameter controls the member's role. There is no "update role" -- remove and re-add to change roles. - **Customer ID**: Use `"my_customer"` as the `customer` parameter for the authenticated user's organization. Specific customer IDs look like `C01abc123`. - **Pagination**: Both user and group list endpoints may return paginated results. Always check for `page_token` in responses for complete results. - **Password requirements**: `GOOGLE_ADMIN_CREATE_USER` requires a password that meets the domain's password policy. Weak passwords will be rejected. ## Quick Reference | Action | Tool | Key Parameters | |--------|------|----------------| | List users | `GOOGLE_ADMIN_LIST_USERS` | `customer`, `domain`, `query`, `max_results` | | Get user details | `GOOGLE_ADMIN_GET_USER` | `user_key` | | Create user | `GOOGLE_ADMIN_CREATE_USER` | `primary_email`, `given_name`, `family_name`, `password` | | Delete user | `GOOGLE_ADMIN_DELETE_USER` | `user_key` | | Suspend user | `GOOGLE_ADMIN_SUSPEND_USER` | `user_key`, `suspended` | | Add user alias | `GOOGLE_ADMIN_ADD_USER_ALIAS` | (see full schema via RUBE_SEARCH_TOOLS) | | List groups | `GOOGLE_ADMIN_LIST_GROUPS` | `customer`, `domain`, `query` | | Get group details | `GOOGLE_ADMIN_GET_GROUP` | `group_key` | | Create group | `GOOGLE_ADMIN_CREATE_GROUP` | `email`, `name`, `description` | | Add to group | `GOOGLE_ADMIN_ADD_USER_TO_GROUP` | `group_key`, `user_key`, `role` | | List group members | `GOOGLE_ADMIN_LIST_GROUP_MEMBERS` | (see full schema via RUBE_SEARCH_TOOLS) | --- *Powered by [Composio](https://composio.dev)*
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.