task-distributor
PassAudited by ClawScan on May 10, 2026.
Overview
This instruction-only skill is coherent with task and queue distribution, but users should ensure any real workflow changes or inter-agent data sharing are authorized and based on measured data.
This skill appears safe to install as an instruction-only task distribution helper. Before using it with real systems, confirm which queues, agents, task metadata, and performance metrics it can access, and require approval before it changes routing, escalation, or workload allocation.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may recommend or perform workflow-routing changes if given suitable tools, which could affect how work is assigned.
If connected to real queue or work-management tools, these instructions could change routing and allocation behavior. This is aligned with the skill purpose, but the user should retain approval for operational changes.
Implementation approach: - Configure queues - Setup routing - Implement balancing - Track capacities - Monitor distribution - Handle exceptions
Use with explicit user approval for queue, routing, escalation, or workload-assignment changes, especially in production or shared team environments.
Task details, capacity information, and performance metrics may be shared across agent components if the surrounding environment supports that.
The skill expects exchanging task requirements and capacity information with a context manager and other agents. This is purpose-aligned for task distribution, but it creates a data-boundary consideration.
When invoked: 1. Query context manager for task requirements and agent capacities
Ensure the connected agents and context manager are trusted and that only necessary task metadata is shared.
The agent could overstate results if it reuses example metrics instead of reporting actual observed performance.
The artifact includes a sample success message with specific metrics. It appears illustrative, but users should ensure any reported metrics are measured rather than copied as a template.
Delivery notification: "Task distribution system completed. Distributed 45K tasks with 230ms average queue time and 7% load variance..."
Ask the agent to cite measured queue, latency, deadline, and utilization data when reporting distribution outcomes.