googletasks-automation
Automate Google Tasks via Rube MCP (Composio): create, list, update, delete, move, and bulk-insert tasks and task lists. Always search tools first for current schemas.
What this skill does
# 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](https://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. 1. Verify Rube MCP is available by confirming `RUBE_SEARCH_TOOLS` responds 2. Call `RUBE_MANAGE_CONNECTIONS` with toolkit `googletasks` 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 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. - **Reorder tasks**: Use `GOOGLETASKS_MOVE_TASK` to change a task's position within its list or reparent it. - **Batch creation**: Use `GOOGLETASKS_BULK_INSERT_TASKS` for creating many tasks at once (e.g., importing from another system). ## Known Pitfalls - Both `tasklist_id` and `task_id` are **required** for `GOOGLETASKS_UPDATE_TASK`, `GOOGLETASKS_DELETE_TASK`, and `GOOGLETASKS_GET_TASK`. You cannot operate on a task without knowing which list it belongs to. - All date/time strings must be in **RFC3339 format** (e.g., `2025-01-20T00:00:00.000Z`). Other formats will be rejected. - `GOOGLETASKS_CLEAR_TASKS` permanently deletes all **completed** tasks from a list. This action is irreversible. - `GOOGLETASKS_LIST_ALL_TASKS` fetches across all lists but results may be paginated -- check for pagination tokens. - Task list IDs are not the same as task list names. Always resolve names to IDs using `GOOGLETASKS_LIST_TASK_LISTS`. - The default task list is typically named "My Tasks" but its ID is an opaque string, not "default" or "primary". ## Quick Reference | Action | Tool | Key Parameters | |--------|------|----------------| | List task lists | `GOOGLETASKS_LIST_TASK_LISTS` | `maxResults`, `pageToken` | | List all tasks | `GOOGLETASKS_LIST_ALL_TASKS` | `max_tasks_total`, `showCompleted`, `dueMin` | | List tasks in a list | `GOOGLETASKS_LIST_TASKS` | `tasklist_id`, `maxResults`, `showCompleted` | | Get single task | `GOOGLETASKS_GET_TASK` | `tasklist_id`, `task_id` | | Create task | `GOOGLETASKS_INSERT_TASK` | `tasklist_id`, `title`, `notes`, `due` | | Bulk create tasks | `GOOGLETASKS_BULK_INSERT_TASKS` | `tasklist_id`, `tasks` | | Update task | `GOOGLETASKS_UPDATE_TASK` | `tasklist_id`, `task_id`, `title`, `status` | | Delete task | `GOOGLETASKS_DELETE_TASK` | `tasklist_id`, `task_id` | | Move/reorder task | `GOOGLETASKS_MOVE_TASK` | `tasklist_id`, `task_id` | | Clear completed | `GOOGLETASKS_CLEAR_TASKS` | `tasklist` | --- *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.