Tasks
What it does
A two-layer task system: reusable templates (recipes) and a prioritized work queue (orders). Define recurring work once, then run it on demand.
Setup
None. Works immediately.
Permissions
- No extra OAuth. Tasks execute within the permissions of the tools they call.
Common prompts
| You say | What happens |
|---|---|
| “Create a task template for weekly status reports” | Saves a reusable definition |
| “Run my weekly report task” | Executes a saved template |
| “What is in my task queue?” | Shows prioritized items |
| “Add 'review PR #42' to my queue as high priority” | Adds a work item |
| “Mark the deployment task as done” | Updates status |
Configuration
- Priority: high, medium, low.
- Status: queued, running, awaiting_review, done.
- Templates can name required tools. If a template needs the browser, the browser skill loads.
Tips
- Templates are recipes. Queue items are orders.
- Good for repetitive workflows you want to hand off.
- Clock-driven recurrence is Schedule, not this queue.
Related: Your first skill, Self-improving skills.