Workflow Skills

# Batch Operations Skill Use `batch_execute` for running the same tool on multiple inputs, or `execute_parallel_work_streams` for running independent sub-agent tasks in parallel. ## Quick Decision Guide | Use Case | Tool | |----------|------| | Fetch multiple documents by ID | `batch_execute` | | Run same search on many queries | `batch_execute` | | Complex multi-step research tasks | `execute_parallel_work_streams` | | Tasks needing different tools | `execute_parallel_work_streams` | ## batch_execute Execute a single tool multiple times with different inputs. ### Parameters | Parameter | Type | Required | Default | Description | |-----------|------|----------|---------|-------------| | `tool_name` | string | Yes | - | Tool to execute | | `inputs` | array | Yes | - | Array of `{ id, input }` objects | | `parallel` | boolean | No | `true` | Run in parallel or sequentially | | `max_concurrency` | number | No | `10` | Max parallel executions (1-50) | | `continue_on_error` | boolea...

# Agent Scheduling Skill Schedule agents to run automatically — either once at a specific time or on a recurring cron schedule. ## One-Time Execution Use `schedule_agent` to run an agent once at a future datetime: ``` schedule_agent( interaction: "my-report-agent", run_at: "2024-02-15T16:00:00Z", name: "Earnings report", vars: { ticker: "AAPL" } ) ``` - `run_at`: ISO 8601 datetime (e.g., `"2024-02-15T16:00:00Z"` or `"2024-02-15T11:00:00-05:00"`) - If the datetime is in the past, the agent runs immediately - No persistent schedule record — fire and forget ## Recurring Schedule Use `schedule_recurring_agent` to create a persistent cron-based schedule: ``` schedule_recurring_agent( name: "Weekly Sales Report", interaction: "sales-report-agent", cron_expression: "0 9 * * MON", timezone: "America/New_York", vars: { report_type: "weekly" } ) ``` ### Cron Format Five fields: `minute hour day month weekday` | Field | Range | Examples | |-------|-------|---------| ...