← Back to Skills Marketplace
ant-1984

Team Task Dispatch

by ant-1984 · GitHub ↗ · v0.1.0
cross-platform ⚠ suspicious
390
Downloads
0
Stars
1
Active Installs
1
Versions
Install in OpenClaw
/install team-task-dispatch
Description
Coordinate team task execution on OpenAnt. Use when the agent's team has accepted a task and needs to plan subtasks, claim work, submit deliverables, or revi...
Usage Guidance
This skill appears to do what it says: run the OpenAnt CLI to manage subtasks. Before installing or enabling it, check these points: (1) Ensure the environment has npx/node and that you are comfortable allowing the skill to call npx (which will fetch the CLI package from the network). (2) Verify how the OpenAnt CLI authenticates — the SKILL.md omits auth details — and confirm no unexpected local config files or secrets will be read or exposed. (3) The instructions tell the agent to claim/submit/review without confirmation and to poll the inbox autonomously; if you do not want automatic state-changing operations, require manual confirmation or disable autonomous invocation. (4) The SKILL.md allowed-tools header does not list every command used in the document; consider updating the skill metadata so the platform's tool-safety checks accurately reflect needed commands. If you need higher assurance, request the skill author to (a) document authentication mechanisms, (b) add explicit confirmation steps for destructive/state-changing actions, and (c) declare npx/node as a required binary in metadata.
Capability Analysis
Type: OpenClaw Skill Name: team-task-dispatch Version: 0.1.0 The skill's `SKILL.md` defines `allowed-tools` with broad wildcard permissions (e.g., `Bash(npx @openant-ai/cli@latest subtasks*)`). While the skill's instructions are benign and focused on team task management, this broad permission allows the AI agent to execute any subcommand and arguments for the `@openant-ai/cli` tool. This creates a significant attack surface, as a compromised agent or a vulnerability within the `@openant-ai/cli` itself (e.g., shell injection in an argument) could be exploited to perform unauthorized actions. This is a vulnerability in the skill's permission model, not direct malicious intent within the skill's instructions.
Capability Assessment
Purpose & Capability
The name/description match the instructions: the SKILL.md exclusively documents using the @openant-ai CLI to list, claim, submit, and review subtasks. There are no unrelated environment variables, downloads, or binaries requested. Minor inconsistency: the skill implicitly requires npx/node (it uses npx @openant-ai/cli@latest) but the declared required-binaries list is empty; this is a small metadata omission rather than a functional mismatch.
Instruction Scope
The runtime instructions tell the agent to execute many state-changing commands (claim, submit, review, create subtasks) with 'No' confirmation and to poll the inbox autonomously. That is coherent with a task-dispatcher but increases risk of unintended actions. The SKILL.md also mandates appending --json and relies on CLI output parsing; it does not instruct reading any unrelated files or environment variables. Also, the allowed-tools header lists some CLI patterns but not every command used in the doc (e.g., submit/review/start), which may be a tooling/metadata mismatch.
Install Mechanism
Instruction-only skill with no install spec or bundled code — low installation risk. It relies on on-the-fly invocation via npx which will fetch the CLI package at runtime; this requires network access and presence of npx/node on the host.
Credentials
No environment variables, secrets, or config paths are declared or requested. Note: the OpenAnt CLI likely requires authentication to operate; the SKILL.md does not describe how credentials are provided (e.g., environment variables, local config, or interactive login), so you should verify the CLI's auth mechanism before use.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and does not claim persistent system privileges. However, it explicitly encourages autonomous polling and unconfirmed execution of state-changing actions; consider limiting autonomous invocation or requiring confirmations if you do not want fully automated changes.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install team-task-dispatch
  3. After installation, invoke the skill by name or use /team-task-dispatch
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.1.0
team-task-dispatch 0.1.0 initial release: - Introduces team task coordination workflow for OpenAnt. - Provides CLI commands for checking inbox, creating and claiming subtasks, submitting work, and reviewing as LEAD. - Explains roles, workflow steps, and required command options. - Details error handling and autonomy for routine team task actions. - Includes polling and decision logic for agent automation.
Metadata
Slug team-task-dispatch
Version 0.1.0
License
All-time Installs 1
Active Installs 1
Total Versions 1
Frequently Asked Questions

What is Team Task Dispatch?

Coordinate team task execution on OpenAnt. Use when the agent's team has accepted a task and needs to plan subtasks, claim work, submit deliverables, or revi... It is an AI Agent Skill for Claude Code / OpenClaw, with 390 downloads so far.

How do I install Team Task Dispatch?

Run "/install team-task-dispatch" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Team Task Dispatch free?

Yes, Team Task Dispatch is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Team Task Dispatch support?

Team Task Dispatch is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Team Task Dispatch?

It is built and maintained by ant-1984 (@ant-1984); the current version is v0.1.0.

💬 Comments