Running the recipe verbatim writes fixed example tasks to the user’s Google Tasks
Source references: 2The steps are write commands with a fixed list name, task content, and an already-past due date; the instructions do not require replacing these values with user-confirmed content before execution.
If an agent treats the recipe as directly executable, unrelated, duplicate, or incorrectly dated items may be added to the user’s account.
These are presented as the recipe’s execution steps, not merely illustrative examples. They create a list named “Q2 Goals” and insert two fixed tasks, one with a 2024-04-01 due date. If an agent follows the steps, that content would be written to the user’s authorized Google Tasks account; the visible text provides no confirmation step for the titles, notes, or date. A user can ask for a preview and explicit confirmation, and restrict access to a designated task list.
1. Create task list: `gws tasks tasklists insert --json '{"title": "Q2 Goals"}'`2. Add a task: `gws tasks tasks insert --params '{"tasklist": "TASKLIST_ID"}' --json '{"title": "Review Q1 metrics", "notes": "Pull data from analytics dashboard", "due": "2024-04-01T00:00:00Z"}'`3. Add another task: `gws tasks tasks insert --params '{"tasklist": "TASKLIST_ID"}' --json '{"title": "Draft Q2 OKRs"}'`4. List tasks: `gws tasks tasks list --params '{"tasklist": "TASKLIST_ID"}' --format table`Show 1 other places
> **PREREQUISITE:** Load the following skills to execute this recipe: `gws-tasks`Set up a new Google Tasks list with initial tasks.