farmos-tasks_skill

Overview

This skill manages farm work orders and tasks for FarmOS. It lets you view assignments and summaries using public integration endpoints, and create, assign, or update tasks via authenticated endpoints. The skill detects actionable statements in conversation and suggests task creation without acting without confirmation.

How this skill works

Read-only data (summaries, filtered task lists, single task details) comes from integration endpoints that require no auth. Writes—creating tasks, changing status, assigning people, and using templates—use JWT-protected endpoints and require the caller's role-based token. The skill extracts assignee, priority, field, equipment, and deadlines from natural language and always confirms before posting.

When to use it

• Log new work items or restock/procurement requests mentioned in conversation.
• Check who is assigned, which tasks are overdue, or get filtered task lists by status/priority.
• Create tasks from templates or turn a spoken action item into a tracked work order.
• Start/complete/cancel tasks and assign employees (requires appropriate role/token).
• Audit counts and dashboards for summary stats (use integration dashboard/tasks-summary).

Best practices

• Use integration endpoints for reads — they don’t require auth and avoid unnecessary token use.
• Always confirm detected task details with the user before creating a task.
• Report total record counts and warn if results look unexpectedly small or paginated.
• Tag all supply/restock tasks with 'procurement' and set priority high when items are out.
• Respect role mapping: if the user lacks permission, tell them rather than using a higher-privilege token.
• Cross-reference weather, equipment, observations, and marketing only when it adds actionable value.

Example use cases

• A crew member says 'We’re low on hydraulic filters' — suggest and create a procurement restock task with quantity context.
• Manager asks 'What tasks are assigned to me?' — fetch /api/tasks/mine with their token and list counts and details.
• Someone: 'Spray field 14 before Thursday' — extract field, action, deadline, propose creation, then create on confirmation.
• Start or complete a job in the field: POST /api/tasks/{id}/start or /complete with the manager/worker token.
• Create a task from a recurring template for seasonal operations using POST /api/templates/{id}/create-task.