菜单
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 to-do items, create task lists, mark tasks complete, or check their Google Tasks.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/BRO3886/gtasks --skill gtasks-cli命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | gtasks-cli |
| description | 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 to-do items, create task lists, mark tasks complete, or check their Google Tasks. |
| homepage | https://github.com/BRO3886/gtasks |
| license | MIT |
| compatibility | Requires gtasks CLI tool to be installed and authenticated |
| metadata | {"author":"BRO3886","version":"1.0"} |
| required-env | [{"name":"GTASKS_CLIENT_ID","description":"Google OAuth2 client ID — can also be set in config file under [credentials]"},{"name":"GTASKS_CLIENT_SECRET","description":"Google OAuth2 client secret — can also be set in config file under [credentials]"}] |
| allowed-tools | Bash(gtasks:*) |
This skill enables you to manage Google Tasks directly from the command line using the gtasks CLI tool.
It can also be installed into supported AI agent skill directories with the built-in gtasks skills commands.
Before using any commands, ensure the following requirements are met:
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:
macOS/Linux (recommended):
curl -fsSL https://gtasks.sidv.dev/install | bash
Installs to ~/.local/bin by default. Set INSTALL_DIR to override:
INSTALL_DIR=/usr/local/bin curl -fsSL https://gtasks.sidv.dev/install | bash
Manual install:
~/.local/bin or /usr/local/bin)chmod +x gtasksWindows: Download the binary from GitHub Releases and add to PATH.
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.
Set up Google OAuth2 credentials as environment variables:
export GTASKS_CLIENT_ID="your-client-id.apps.googleusercontent.com"
GTASKS_CLIENT_SECRET=
How to get credentials:
http://localhost:8080/callbackhttp://localhost:8081/callbackhttp://localhost:8082/callbackhttp://localhost:9090/callbackhttp://localhost:9091/callbackFor persistent setup, the recommended approach is to add credentials to the gtasks config file:
# ~/.config/gtasks/config.toml (new installs)
# ~/.gtasks/config.toml (legacy installs)
[credentials]
client_id = "your-client-id.apps.googleusercontent.com"
client_secret = "your-client-secret"
Set permissions: chmod 600 ~/.config/gtasks/config.toml
Alternatively, export from your shell profile — do not commit these values to version control:
export GTASKS_CLIENT_ID="your-client-id"
export GTASKS_CLIENT_SECRET="your-client-secret"
Once environment variables are set, authenticate with Google:
gtasks login
This will open a browser for OAuth2 authentication. The token is stored in the system keyring (macOS Keychain, Linux Secret Service, Windows Credential Manager). On headless systems where no keyring is available, it falls back to a token file in the config directory. If you no longer need access, run gtasks logout to remove the stored token.
If gtasks is already installed, you can install this skill into supported agent directories with:
gtasks skills install
Supported agent targets:
claude -> ~/.claude/skills/gtasks-cli/codex -> ~/.agents/skills/gtasks-cli/openclaw -> ~/.openclaw/skills/gtasks-cli/Useful commands:
gtasks skills status
gtasks skills install --agent codex
gtasks skills install --agent all
gtasks skills uninstall --agent codex
For automated setups, prefer --agent <name> or --agent all to avoid interactive prompts.
All commands follow this pattern:
gtasks [command] [subcommand] [flags] [arguments]
gtasks login
Opens browser for Google OAuth2 authentication. Required before using any other commands.
gtasks logout
Removes stored credentials from the system keyring (and token file if present).
These commands manage installation of the gtasks-cli skill itself for supported AI agents.
gtasks skills status
Shows whether the skill is installed for Claude, Codex, and OpenClaw, along with the installed version when available.
gtasks skills install
gtasks skills install --agent claude
gtasks skills install --agent codex
gtasks skills install --agent openclaw
gtasks skills install --agent all
Installs the embedded gtasks-cli skill files into the selected agent skill directory.
gtasks skills uninstall
gtasks skills uninstall --agent codex
gtasks skills uninstall --agent all
Removes the installed gtasks-cli skill from the selected agent skill directory.
gtasks tasklists view
Displays all task lists with numbered indices.
Output Example:
[1] My Tasks
[2] Work
[3] Personal
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)gtasks tasklists rm
Interactive prompt to select and delete a task list.
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)All task commands can optionally specify a task list using the -l flag. If omitted, gtasks uses GTASKS_DEFAULT_TASKLIST env var or tasks.default_task_list from the config file. If only one list exists, it is selected automatically. Otherwise you'll be prompted interactively.
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"
}
]
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, 2024December 25tomorrownext Friday12/25/2024See dateparse examples for all supported formats.
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.
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.
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/...
When a user says "add a task to my work list":
gtasks tasks add -l "Work" -t "Task title"
gtasks tasks view --sort=due
gtasks tasks done -l "Work"
# Interactive prompt appears, select task
gtasks tasks done -l "Work"
# Repeat as needed
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"
gtasks tasks view --format=json > tasks.json
gtasks tasks view --format=csv > tasks.csv
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:
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.
Common errors and solutions:
echo $GTASKS_CLIENT_IDgtasks login to authenticategtasks tasklists view to see available listsgtasks tasks view to see current task numbersgtasks 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"
gtasks tasks view -l "Work" --sort=due
gtasks tasks done 1 -l "Work"
gtasks tasks add -l "Work" -t "Submit proposal" -n "Include budget and timeline" -d "next Friday"
gtasks tasks view --completed --format=json -l "Work" > completed_work.json
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'"
gtasks tasklists view to see available lists