gws-tasks
by googleworkspacegws-tasks helps you manage Google Tasks through the gws CLI with predictable tasklist and task operations. Use it for workflow automation, gws-tasks install steps, and repeatable gws-tasks usage when you need a clear command-line guide instead of guesswork.
This skill scores 74/100, which means it is listable and likely useful for directory users, but it is better suited to users who already know they want Google Tasks operations than to those seeking a highly guided install. The repository provides a clear trigger, a real command pattern, and substantive API coverage, but it lacks supporting files and deeper usage examples that would reduce adoption friction further.
- Clear triggerability via `gws tasks <resource> <method> [flags]` and a matching `cliHelp` entry.
- Substantive workflow content: it enumerates real Google Tasks API resources and methods for task lists and tasks.
- No placeholder or experimental markers; the skill body is substantial and appears production-oriented.
- No install command and no support files/references, so users must rely mainly on SKILL.md for adoption.
- Progressive disclosure is limited: there is no quick-start, examples beyond the command shape, or decision guidance for common task workflows.
Overview of gws-tasks skill
What gws-tasks does
The gws-tasks skill helps you manage Google Tasks through the gws CLI: listing task lists, creating and updating lists, and working with tasks inside them. It is best for users who want a command-line workflow for Google Tasks rather than a generic prompt that guesses API behavior.
Who this skill is for
Use gws-tasks if you are automating task-list operations, building workflow scripts, or validating task-management flows in a Google Workspace environment. It is most useful when you already know you need the Google Tasks API shape and want a reliable, repeatable gws tasks interface.
Why it matters
The main value of gws-tasks for Workflow Automation is consistency: the skill gives you the exact resource/method pattern, supported tasklist and task actions, and the constraints you need to avoid trial-and-error. That makes it better than a vague “manage tasks” prompt when the output must be executable.
How to Use gws-tasks skill
Install and prerequisite setup
Install with npx skills add googleworkspace/cli --skill gws-tasks. Before using it, read ../gws-shared/SKILL.md because it contains the auth, global flags, and security rules this skill depends on. If that shared file is missing, run gws generate-skills first.
Shape your request for the skill
The gws-tasks usage pattern is gws tasks <resource> <method> [flags], so your prompt should name three things clearly: the target resource, the method, and the outcome you want. Good inputs include the task list name or ID, whether you are creating, updating, deleting, or listing, and any filter or field constraints you need.
What to read first
Start with SKILL.md, then inspect any repo guidance that affects execution: README.md, AGENTS.md, metadata.json, and relevant rules/, resources/, references/, or scripts/ folders. In this repo, SKILL.md is the main source of truth, so there is little extra scaffolding to decode.
Practical workflow
Turn a rough request into an executable prompt by adding concrete identifiers and desired output. For example: “List my task lists, then create a task named ‘Submit expense report’ in the list I specify, and return the exact command sequence.” This is better than “help me with Google Tasks” because it gives the skill enough context to choose the right resource and method without inventing details.
gws-tasks skill FAQ
Is gws-tasks only for Google Tasks API work?
Yes, that is the intended fit. gws-tasks is not a general productivity assistant; it is a focused interface for task lists and tasks within the Google Workspace CLI ecosystem.
Do I need to know the CLI before using it?
Not deeply. Beginners can use gws-tasks if they can provide clear task-list intent, but they still need to supply specifics such as the list target, action, and any relevant IDs or names. Without those, the skill cannot reliably choose the right command.
When should I not use this skill?
Do not use gws-tasks if you only need brainstorming, lightweight to-do organization, or a one-off natural-language summary of tasks. It is a better match when you need a commandable workflow, reproducible operations, or integration with gws-based automation.
How is it different from a normal prompt?
A normal prompt may describe task management in broad terms. The gws-tasks skill is tied to an explicit command structure and shared repository rules, which reduces guesswork and makes the result more suitable for real execution.
How to Improve gws-tasks skill
Give the skill the exact object and action
The fastest way to improve results is to name the task list, task, and method precisely. Instead of “clean up my tasks,” say “list all task lists, identify the list named ‘Work’, then update task X to due Friday.” Specificity matters because gws-tasks maps directly to API resources and methods.
Include the output shape you need
If you want a command, a sequence of commands, or a short explanation of the chosen method, say so up front. This helps the skill stay practical for workflow automation instead of returning a generic description of Google Tasks behavior.
Watch for common failure modes
The most common miss is vague identity: a list name without an ID, or an action without the target resource. Another failure mode is omitting shared prerequisites, especially auth and global flags from gws-shared. Check those first when a command looks plausible but cannot run cleanly.
Iterate after the first draft
If the first result is close but incomplete, refine with the missing constraint rather than restating the whole request. Add details like “use patch semantics,” “limit to completed tasks,” or “target only the specified task list” so the next pass is narrower and more executable.