agent-team-task-fail

Mark task assignments as failed with a reason and optional artifact.

2|Updated May 10, 2026
One-click install
npx skills add https://github.com/tae2089/agent-team --skill agent-team-task-fail
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-team-task-fail
Source: https://github.com/tae2089/agent-team/tree/main/skills/agent-team-task-fail
Command: npx skills add https://github.com/tae2089/agent-team --skill agent-team-task-fail

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

When a task is assigned to an agent, and that work fails, teams need a reliable way to record the failure reason and an optional artifact to preserve evidence and audit trails.

Core Features & Use Cases

  • Mark a task as failed with a clear reason and optional artifact for documentation and auditing.
  • Enforce that the reporting agent matches the task assignee to prevent misattribution.
  • See also related actions like retrying or closing tasks to maintain end-to-end task lifecycle.

Quick Start

Mark the specified task as failed by supplying the task id, the responsible agent, and a reason, with an optional path to an artifact.

Frequently Asked Questions about agent-team-task-fail

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I record a task failure with a reason in agent workflows?

To record a task failure, provide the task id, assignee agent, and reason. The system marks the assignment as failed and stores the outcome for audit, optionally linking an artifact path for evidence.

What is an audit trail for failed agent tasks?

An audit trail for failed agent tasks is a stored record capturing the terminal failure event, the responsible agent, and the reason. It preserves evidence and documentation for end-to-end workflow visibility.

Can I attach an artifact when marking an agent-team task as failed?

Yes, you can attach an artifact when marking an agent-team task as failed. Supply an optional artifact path alongside the required task id, agent, and reason to store relevant evidence.

Why does the reporting agent need to match the task assignee?

The reporting agent must match the task assignee to prevent misattribution. This validation enforces accountability within agent-team workflows by ensuring only the responsible agent records the failure.

What is the best way to capture terminal failures in agent-team workflows?

The best way to capture terminal failures is to mark the task as failed using the assigned agent, a clear reason, and optional artifacts. This maintains an end-to-end task lifecycle audit trail.