Skip to main content
Agent skill

Googleadmin Automation

Automate Google Admin tasks via Rube MCP (Composio): user management, org units, groups, and domain administration. Always search tools first for current schemas.

Get started

Get the complete skill folder, including its scripts and reference files.

This workflow depends on an external MCP integration. Check the source for the server, account access and setup it requires.

When to use this skill

Use Googleadmin Automation when an AI agent needs a reusable SKILL.md workflow for this job: Automate Google Admin tasks via Rube MCP (Composio): user management, org units, groups, and domain administration. Always search tools first for current schemas.

When not to use it

Skip Googleadmin Automation when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/googleadmin-automation
# Save SKILL.md to ~/.claude/skills/googleadmin-automation/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/googleadmin-automation/SKILL.md. For a shared project, commit the folder at .claude/skills/googleadmin-automation/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Googleadmin Automation skill for this task: Use Googleadmin Automation when this documented workflow matches the task. Confirm any required inputs or files before making changes.

What supports this recommendation?

72/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
77/100
Practical detail
68/100
Source evidence
63/100
Source signals
80/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# Google Admin Automation via Rube MCP

Automate Google Admin operations through Composio's Google Admin toolkit via Rube MCP.

**Toolkit docs**: [composio.dev/toolkits/google_admin](https://composio.dev/toolkits/google_admin)

## Prerequisites

- Rube MCP must be connected (RUBE_SEARCH_TOOLS available) - Active Google Admin connection via `RUBE_MANAGE_CONNECTIONS` with toolkit `google_admin` - 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

## Tool Discovery

Always discover available tools before executing workflows:

``` RUBE_SEARCH_TOOLS: queries=[{"use_case": "user management, org units, groups, and domain administration", "known_fields": ""}] ```

This returns: - Available tool slugs for Google Admin - Recommended execution plan steps - Known pitfalls and edge cases - Input schemas for each tool

## Core Workflows

### 1. Discover Available Google Admin Tools

``` RUBE_SEARCH_TOOLS: queries: - use_case: "list all available Google Admin tools and capabilities" ```

Review the returned tools, their descriptions, and input schemas before proceeding.

### 2. Execute Google Admin Operations

After discovering tools, execute them via:

``` RUBE_MULTI_EXECUTE_TOOL: tools: - tool_slug: "<discovered_tool_slug>" arguments: {<schema-compliant arguments>} memory: {} sync_response_to_workbench: false ```

### 3. Multi-Step Workflows

For complex workflows involving multiple Google Admin operations:

1. Search for all relevant tools: `RUBE_SEARCH_TOOLS` with specific use case 2. Execute prerequisite steps first (e.g., fetch before update) 3. Pass data between steps using tool responses 4. Use `RUBE_REMOTE_WORKBENCH` for bulk operations or data processing

## Common Patterns

### Search Before Action Always search for existing resources before creating new ones to avoid duplicates.

### Pagination Many list operations support pagination. Check responses for `next_cursor` or `page_token` and continue fetching until exhausted.

### Error Handling - Check tool responses for errors before proceeding - If a tool fails, verify the connection is still ACTIVE - Re-authenticate via `RUBE_MANAGE_CONNECTIONS` if connection expired

### Batch Operations For bulk operations, use `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` in a loop with `ThreadPoolExecutor` for parallel execution.

## Known Pitfalls

- **Always search tools first**: Tool schemas and available operations may change. Never hardcode tool slugs without first discovering them via `RUBE_SEARCH_TOOLS`. - **Check connection status**: Ensure the Google Admin connection is ACTIVE before executing any tools. Expired OAuth tokens require re-authentication. - **Respect rate limits**: If you receive rate limit errors, reduce request frequency and implement backoff. - **Validate schemas**: Always pass strictly schema-compliant arguments. Use `RUBE_GET_TOOL_SCHEMAS` to load full input schemas when `schemaRef` is returned instead of `input_schema`.

## Quick Reference

| Operation | Approach | |-----------|----------| | Find tools | `RUBE_SEARCH_TOOLS` with Google Admin-specific use case | | Connect | `RUBE_MANAGE_CONNECTIONS` with toolkit `google_admin` | | Execute | `RUBE_MULTI_EXECUTE_TOOL` with discovered tool slugs | | Bulk ops | `RUBE_REMOTE_WORKBENCH` with `run_composio_tool()` | | Full schema | `RUBE_GET_TOOL_SCHEMAS` for tools with `schemaRef` |

> **Toolkit docs**: [composio.dev/toolkits/google_admin](https://composio.dev/toolkits/google_admin)

Intended uses

  • Use Googleadmin Automation when this documented workflow matches the task.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.