$ ~/registry/skill/composiohq-composio-skills-googletasks-automation

SKILL

googletasks-automation

Name: googletasks-automation
Author: Composio

Automate Google Tasks and lists with bulk task management workflows.

Stars

★ 67,807

Source

GitHub

Updated

2026-07-15

// securityCaution

Prompt only, no code
Open source
Community-trusted· 64.7k

Summary

This skill appears to be an open-source prompt/workflow wrapper from a relatively trustworthy source, with no clear red flags for local code execution or direct local secret collection. However, its real functionality depends on external Rube MCP and Google Tasks authorization, so task data is sent to third-party/target services and the overall posture is best classified as caution.

CredentialsCaution

The material says 'no API keys needed,' but it requires an ACTIVE `googletasks` connection via `RUBE_MANAGE_CONNECTIONS` and completing auth through a returned link, implying Google/Rube-side credentials or OAuth authorization are involved. There is no sign of asking for local plaintext environment secrets, but the scope of account permissions granted to the third-party connection should be reviewed.

Network egressCaution

The README explicitly instructs adding `https://rube.app/mcp` as an MCP server and using Composio/Rube to operate Google Tasks; task titles, notes, due dates, and list metadata would be transmitted during tool calls. The egress targets are related to the stated function, but this is not a 'no remote endpoint' design.

Code executionLow risk

Based on the provided material, this is a prompt-only/workflow-style skill with no local script installation, shell execution, or process-launch requirement. Its behavior is mainly to instruct use of existing MCP tools rather than execute arbitrary code on the local machine.

Data accessCaution

Its stated data scope is focused on the authorized Google Tasks account: it can create, list, update, delete, move, and bulk insert tasks and task lists, and read task content and status. There is no indication of local file or system resource access, but it does have substantial read/write capability over cloud task data.

Supply chainCaution

Positive signals include a GitHub open-source source and high community trust (64.7k stars), which materially lowers supply-chain risk. However, the license and maintenance status are unclear, and the actual workflow depends on external Rube MCP/Composio services whose server-side implementation is not auditable from the material, so caution is appropriate rather than high risk.

Recommendations

Review the Google Tasks permission scope requested by Rube/Composio before authorizing, and grant only the minimum access needed.
Avoid processing sensitive task content through this connection until you confirm which third-party services transmit and store the data.
Test with a low-sensitivity or secondary account first before connecting your primary Google account.
Pin to a trusted repository version and keep watching for maintenance or trust changes in both the repo and the Rube MCP service.

Audited by: gpt-5.4 · 2026-06-17

// install

Copy the install command and let the AI configure it · recommended for beginners

Please install the "googletasks-automation" skill from askskill:
1. Download https://raw.githubusercontent.com/ComposioHQ/awesome-claude-skills/master/composio-skills/googletasks-automation/SKILL.md
2. Save it as ~/.claude/skills/googletasks-automation/SKILL.md
3. Reload skills and tell me it's ready

// download

Download SKILL.mdInstall manifest ↗

// docs

Google Tasks Automation via Rube MCP

Create, manage, organize, and bulk-operate on Google Tasks and task lists using Rube MCP (Composio).

Toolkit docs: composio.dev/toolkits/googletasks

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
Active connection via RUBE_MANAGE_CONNECTIONS with toolkit googletasks
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.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
Call RUBE_MANAGE_CONNECTIONS with toolkit googletasks
If connection is not ACTIVE, follow the returned auth link to complete setup
Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. List All Task Lists

Use GOOGLETASKS_LIST_TASK_LISTS to fetch all available task lists for the authenticated user.

Tool: GOOGLETASKS_LIST_TASK_LISTS
Parameters:
  - maxResults: Maximum task lists to return
  - pageToken: Pagination token for next page

2. Create a New Task

Use GOOGLETASKS_INSERT_TASK to add a new task to a specific task list.

Tool: GOOGLETASKS_INSERT_TASK
Parameters:
  - tasklist_id (required): ID of the target task list
  - title (required): Task title
  - notes: Task description/notes
  - due: Due date in RFC3339 format (e.g., "2025-01-20T00:00:00.000Z")
  - status: "needsAction" or "completed"
  - task_parent: Parent task ID (to create subtask)
  - task_previous: Previous task ID (for ordering)

3. List All Tasks Across Lists

Use GOOGLETASKS_LIST_ALL_TASKS to fetch tasks across all task lists with optional filters.

Tool: GOOGLETASKS_LIST_ALL_TASKS
Parameters:
  - max_tasks_total: Maximum total tasks to return
  - showCompleted: Include completed tasks
  - showDeleted: Include deleted tasks
  - showHidden: Include hidden tasks
  - dueMin / dueMax: Filter by due date range
  - completedMin / completedMax: Filter by completion date
  - updatedMin: Filter by last update time
  - showAssigned: Include assigned tasks

4. Update an Existing Task

Use GOOGLETASKS_UPDATE_TASK to modify a task's title, notes, due date, or status.

Tool: GOOGLETASKS_UPDATE_TASK
Parameters:
  - tasklist_id (required): Task list ID
  - task_id (required): Task ID to update
  - title: New title
  - notes: Updated notes
  - due: New due date (RFC3339)
  - status: "needsAction" or "completed"

5. Bulk Insert Tasks

Use GOOGLETASKS_BULK_INSERT_TASKS to create multiple tasks at once in a single operation.

Tool: GOOGLETASKS_BULK_INSERT_TASKS
Parameters:
  - tasklist_id (required): Target task list ID
  - tasks (required): Array of task objects (each with title, notes, due, status)
  - batch_size: Number of tasks per batch request

6. Delete or Clear Tasks

Use GOOGLETASKS_DELETE_TASK to remove a specific task, or GOOGLETASKS_CLEAR_TASKS to permanently remove all completed tasks from a list.

Tool: GOOGLETASKS_DELETE_TASK
Parameters:
  - tasklist_id (required): Task list ID
  - task_id (required): Task ID to delete

Tool: GOOGLETASKS_CLEAR_TASKS
Parameters:
  - tasklist (required): Task list ID to clear completed tasks from

Common Patterns

Get task list ID first: Always start with GOOGLETASKS_LIST_TASK_LISTS to discover available task lists and their IDs before creating or listing tasks.
List then update: Use GOOGLETASKS_LIST_ALL_TASKS or GOOGLETASKS_LIST_TASKS to find task IDs, then use GOOGLETASKS_UPDATE_TASK to modify them.
Mark complete: Update a task with status: "completed" using GOOGLETASKS_UPDATE_TASK.
Create subtasks: Use GOOGLETASKS_INSERT_TASK with the task_parent parameter set to the parent task's ID.

…

View full docs ↗

Automate Google Docs creation, editing, search, export, and document workflows.

ComposioGet→

$ loading_