Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Developer Tools
gtasks-cli
Manage Google Tasks from the command line - view, create, update, delete tasks and task lists. Use when the user asks to interact with Google Tasks, manage t...
skill openclawclawhub Free
Manage Google Tasks from the command line - view, create, update, delete tasks and task lists. Use when the user asks to interact with Google Tasks, manage t...
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, references/QUICK-REFERENCE.md, references/ADVANCED.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.2
Provenance
- Publisher
- BRO3886
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Google Tasks CLI Skill
This skill enables you to manage Google Tasks directly from the command line using the gtasks CLI tool.
Prerequisites
Before using any commands, ensure the following requirements are met:
1. GTasks Installation
Check if gtasks is installed on the system: # Cross-platform check (works on macOS, Linux, Windows Git Bash) gtasks --version 2>/dev/null || gtasks.exe --version 2>/dev/null || echo "gtasks not found" # Or use which/where commands # macOS/Linux: which gtasks # Windows (Command Prompt): where gtasks # Windows (PowerShell): Get-Command gtasks If gtasks is not installed: Download the binary for your system from GitHub Releases Install it: macOS/Linux: Move to /usr/local/bin or add to PATH Windows: Add to a folder in your PATH environment variable Verify installation: gtasks --version IMPORTANT for Agents: Always check if gtasks is installed before attempting to use it. If the command is not found, inform the user and provide installation instructions.
2. Environment Variables
Set up Google OAuth2 credentials as environment variables: export GTASKS_CLIENT_ID="your-client-id.apps.googleusercontent.com" export GTASKS_CLIENT_SECRET="your-client-secret" How to get credentials: Go to Google Cloud Console Create a new project or select an existing one Enable the Google Tasks API Create OAuth2 credentials (Application type: "Desktop app") Note the authorized redirect URIs that gtasks uses: http://localhost:8080/callback http://localhost:8081/callback http://localhost:8082/callback http://localhost:9090/callback http://localhost:9091/callback For persistent setup, use a secrets manager or a ~/.env file with restrictive permissions โ do not commit these values to version control or add them to shared shell profile files: # Recommended: store in a file with restricted permissions echo 'export GTASKS_CLIENT_ID="your-client-id"' >> ~/.gtasks_env echo 'export GTASKS_CLIENT_SECRET="your-client-secret"' >> ~/.gtasks_env chmod 600 ~/.gtasks_env # Source it from your shell profile echo 'source ~/.gtasks_env' >> ~/.zshrc
2. Authentication
Once environment variables are set, authenticate with Google: gtasks login This will open a browser for OAuth2 authentication. The token is stored in ~/.gtasks/token.json with 0600 permissions. Verify with ls -la ~/.gtasks/token.json. If you no longer need access, run gtasks logout to revoke and delete the token.
Core Concepts
Task Lists: Containers that hold tasks (like "Work", "Personal", "Shopping") Tasks: Individual to-do items within a task list Task Properties: Title (required), notes/description (optional), due date (optional), status (pending/completed)
Command Structure
All commands follow this pattern: gtasks [command] [subcommand] [flags] [arguments]
Login
gtasks login Opens browser for Google OAuth2 authentication. Required before using any other commands.
Logout
gtasks logout Removes stored credentials from ~/.gtasks/token.json.
View All Task Lists
gtasks tasklists view Displays all task lists with numbered indices. Output Example: [1] My Tasks [2] Work [3] Personal
Create a Task List
gtasks tasklists add -t "Work Projects" gtasks tasklists add --title "Shopping List" Creates a new task list with the specified title. Flags: -t, --title: Task list title (required)
Delete a Task List
gtasks tasklists rm Interactive prompt to select and delete a task list.
Update Task List Title
gtasks tasklists update -t "New Title" Interactive prompt to select a task list and update its title. Flags: -t, --title: New title for the task list (required)
Task Management
All task commands can optionally specify a task list using the -l flag. If omitted, you'll be prompted to select one interactively.
View Tasks
Basic view: gtasks tasks view gtasks tasks view -l "Work" Include completed tasks: gtasks tasks view --include-completed gtasks tasks view -i Show only completed tasks: gtasks tasks view --completed Sort tasks: gtasks tasks view --sort=due # Sort by due date gtasks tasks view --sort=title # Sort by title gtasks tasks view --sort=position # Sort by position (default) Output formats: gtasks tasks view --format=table # Table format (default) gtasks tasks view --format=json # JSON output gtasks tasks view --format=csv # CSV output Table Output Example: Tasks in Work: No Title Description Status Due 1 Finish report Q4 analysis pending 25 December 2024 2 Team meeting Weekly sync pending - 3 Code review PR #123 completed 20 December 2024 JSON Output Example: [ { "number": 1, "title": "Finish report", "description": "Q4 analysis", "status": "pending", "due": "2024-12-25" } ]
Create a Task
Interactive mode: gtasks tasks add gtasks tasks add -l "Work" Prompts for title, notes, and due date. Flag mode: gtasks tasks add -t "Buy groceries" gtasks tasks add -t "Finish report" -n "Q4 analysis" -d "2024-12-25" gtasks tasks add -t "Call dentist" -d "tomorrow" gtasks tasks add -t "Team meeting" -d "Dec 25" Flags: -t, --title: Task title (required for non-interactive mode) -n, --note: Task notes/description (optional) -d, --due: Due date (optional, flexible format) Date Format Examples: The date parser supports many formats: 2024-12-25 (ISO format) Dec 25, 2024 December 25 tomorrow next Friday 12/25/2024 See dateparse examples for all supported formats.
Mark Task as Complete
With task number: gtasks tasks done 1 gtasks tasks done 3 -l "Work" Interactive mode: gtasks tasks done gtasks tasks done -l "Personal" Prompts to select a task from the list.
Delete a Task
With task number: gtasks tasks rm 2 gtasks tasks rm 1 -l "Shopping" Interactive mode: gtasks tasks rm gtasks tasks rm -l "Work" Prompts to select a task to delete.
View Task Details
With task number: gtasks tasks info 1 gtasks tasks info 3 -l "Work" Interactive mode: gtasks tasks info gtasks tasks info -l "Personal" Output Example: Task: Finish report Status: Needs action Due: 25 December 2024 Notes: Complete Q4 analysis and submit to manager Links: - https://docs.google.com/document/d/... View in Google Tasks: https://tasks.google.com/...
Quick Task Creation
When a user says "add a task to my work list": gtasks tasks add -l "Work" -t "Task title"
Check Today's Tasks
gtasks tasks view --sort=due
Complete Multiple Tasks
gtasks tasks done -l "Work" # Interactive prompt appears, select task gtasks tasks done -l "Work" # Repeat as needed
View All Tasks Across Lists
Run view command multiple times for each list, or first list all task lists: gtasks tasklists view gtasks tasks view -l "Work" gtasks tasks view -l "Personal"
Export Tasks
gtasks tasks view --format=json > tasks.json gtasks tasks view --format=csv > tasks.csv
Best Practices
Always check authentication first: If commands fail with authentication errors, run gtasks login Use task list flag for automation: When scripting or when the user specifies a list name, use -l flag to avoid interactive prompts Leverage flexible date parsing: The --due flag accepts natural language dates like "tomorrow", "next week", etc. Use appropriate output format: Table format for human-readable output JSON for parsing/integration with other tools CSV for spreadsheet import Task numbers are ephemeral: Task numbers change when tasks are added, completed, or deleted. Always view the list first to get current numbers. Handle missing lists gracefully: If a user specifies a non-existent list name, the command will error. Always verify list names first with gtasks tasklists view.
Error Handling
Common errors and solutions: "Failed to get service" or Authentication errors: First, ensure environment variables are set: echo $GTASKS_CLIENT_ID If variables are not set, export them (see Prerequisites section) Then run gtasks login to authenticate "incorrect task-list name": The specified list name doesn't exist. Use gtasks tasklists view to see available lists "Incorrect task number": The task number is invalid. Use gtasks tasks view to see current task numbers "Date format incorrect": The date string couldn't be parsed. Use formats like "2024-12-25", "tomorrow", or "Dec 25"
Example 1: Create a shopping list and add items
gtasks tasklists add -t "Shopping" gtasks tasks add -l "Shopping" -t "Milk" gtasks tasks add -l "Shopping" -t "Bread" gtasks tasks add -l "Shopping" -t "Eggs"
Example 2: Review and complete work tasks
gtasks tasks view -l "Work" --sort=due gtasks tasks done 1 -l "Work"
Example 3: Add task with deadline
gtasks tasks add -l "Work" -t "Submit proposal" -n "Include budget and timeline" -d "next Friday"
Example 4: Export completed tasks
gtasks tasks view --completed --format=json -l "Work" > completed_work.json
Before Running Any Commands
Check gtasks installation first: # Try to run gtasks version check gtasks --version 2>/dev/null || gtasks.exe --version 2>/dev/null If this fails, inform the user that gtasks is not installed and provide installation instructions from the Prerequisites section. Verify environment variables are set: # Check if variables exist (macOS/Linux) [ -n "$GTASKS_CLIENT_ID" ] && echo "GTASKS_CLIENT_ID is set" || echo "GTASKS_CLIENT_ID is not set" [ -n "$GTASKS_CLIENT_SECRET" ] && echo "GTASKS_CLIENT_SECRET is set" || echo "GTASKS_CLIENT_SECRET is not set" # Windows PowerShell if ($env:GTASKS_CLIENT_ID) { "GTASKS_CLIENT_ID is set" } else { "GTASKS_CLIENT_ID is not set" } if ($env:GTASKS_CLIENT_SECRET) { "GTASKS_CLIENT_SECRET is set" } else { "GTASKS_CLIENT_SECRET is not set" } Check authentication status: gtasks tasklists view &>/dev/null && echo "Authenticated" || echo "Not authenticated - run 'gtasks login'"
General Tips
When the user mentions "tasks" without specifying a tool, ask if they want to use Google Tasks If the user asks about their tasks, first run gtasks tasklists view to see available lists Always confirm which task list to use if not specified by the user When creating tasks with dates, prefer explicit date formats (YYYY-MM-DD) over relative terms for clarity Remember that task numbers are 1-indexed and change after modifications If a command requires interaction but you're running non-interactively, use flags to provide all required information
Category context
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs
- SKILL.md
- references/ADVANCED.md
- references/QUICK-REFERENCE.md