Manage Google Tasks lists and individual tasks via command-line API calls.
Works with
Two resource types: tasklists (create, read, update, delete, list) and tasks (create, read, update, delete, list, move, clear completed)
Supports task hierarchy with up to 2,000 subtasks per task and enforces limits of 20,000 non-hidden tasks per list and 100,000 total tasks
Handles task assignments from Google Docs and Chat Spaces, with deletion cascading to assignment surfaces
Use gws schema to inspect me
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongws-tasksExecute the skills CLI command in your project's root directory to begin installation:
Fetches gws-tasks from googleworkspace/cli and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate gws-tasks. Access via /gws-tasks in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
23.9K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
23.9K
stars
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws tasks <resource> <method> [flags]
delete — Deletes the authenticated user's specified task list. If the list contains assigned tasks, both the assigned tasks and the original tasks in the assignment surface (Docs, Chat Spaces) are deleted.get — Returns the authenticated user's specified task list.insert — Creates a new task list and adds it to the authenticated user's task lists. A user can have up to 2000 lists at a time.list — Returns all the authenticated user's task lists. A user can have up to 2000 lists at a time.patch — Updates the authenticated user's specified task list. This method supports patch semantics.update — Updates the authenticated user's specified task list.clear — Clears all completed tasks from the specified task list. The affected tasks will be marked as 'hidden' and no longer be returned by default when retrieving all tasks for a task list.delete — Deletes the specified task from the task list. If the task is assigned, both the assigned task and the original task (in Docs, Chat Spaces) are deleted. To delete the assigned task only, navigate to the assignment surface and unassign the task from there.get — Returns the specified task.insert — Creates a new task on the specified task list. Tasks assigned from Docs or Chat Spaces cannot be inserted from Tasks Public API; they can only be created by assigning them from Docs or Chat Spaces. A user can have up to 20,000 non-hidden tasks per list and up to 100,000 tasks in total at a time.list — Returns all tasks in the specified task list. Doesn't return assigned tasks by default (from Docs, Chat Spaces). A user can have up to 20,000 non-hidden tasks per list and up to 100,000 tasks in total at a time.move — Moves the specified task to another position in the destination task list. If the destination list is not specified, the task is moved within its current list. This can include putting it as a child task under a new parent and/or move it to a different position among its sibling tasks. A user can have up to 2,000 subtasks per task.patch — Updates the specified task. This method supports patch semantics.update — Updates the specified task.Before calling any API method, inspect it:
# Browse resources and methods
gws tasks --help
# Inspect a method's required params, types, and defaults
gws schema tasks.<resource>.<method>
Use gws schema output to build your --params and --json flags.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
Keeps context tight: gws-tasks is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for gws-tasks matched our evaluation — installs cleanly and behaves as described in the markdown.
gws-tasks reduced setup friction for our internal harness; good balance of opinion and flexibility.
Useful defaults in gws-tasks — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Useful defaults in gws-tasks — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
I recommend gws-tasks for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for gws-tasks matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: gws-tasks is the kind of skill you can hand to a new teammate without a long onboarding doc.
gws-tasks is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
gws-tasks is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
showing 1-10 of 58