task-status

$npx mdskill add aAAaqwq/AGI-Super-Team/task-status

Keep users informed with periodic task status updates.

  • Prevents user confusion during long-running multi-step operations.
  • Depends on Python scripts for manual and automated status reporting.
  • Selects status type based on task completion or failure state.
  • Delivers formatted messages with emojis and progress indicators.

SKILL.md

.github/skills/task-statusView on GitHub ↗
---
name: task-status
description: Send short status descriptions in chat for long-running tasks. Use when you need to provide periodic updates during multi-step operations, confirm task completion, or notify of failures. Includes automated periodic monitoring that sends updates every 5 seconds, status message templates, and a helper function for consistent status reporting.
---

# Task Status Skill

## Quick Start

### Manual Status Updates
```bash
python scripts/send_status.py "Starting data fetch..." "progress" "step1"
python scripts/send_status.py "Processing complete" "success" "final"
python scripts/send_status.py "Error: Missing API key" "error" "auth"
```

### Automatic Periodic Monitoring (Every 5 seconds)
```bash
# Start monitoring a long-running task
python scripts/monitor_task.py start "My Long Task" "processing"

# Monitor will send "Still working..." updates every 5 seconds
# When task completes, report final status
python scripts/monitor_task.py stop "My Long Task" "success" "Completed successfully!"
```

## Status Types

- **progress**: Ongoing work (shows 🔄 or ->)
- **success**: Task complete (shows ✅ or OK)
- **error**: Failed task (shows ❌ or !)
- **warning**: Issue but continuing (shows ⚠️ or ?)

## Periodic Monitoring

The `monitor_task.py` script provides automatic updates:

### Starting Monitor
```bash
python scripts/monitor_task.py start "<task_name>" "<status_type>" [--interval <seconds>]
```

- Automatically sends "Still working..." updates every 5 seconds
- Runs in background until stopped
- Can be customized with different intervals

### Stopping Monitor
```bash
python scripts/monitor_task.py stop "<task_name>" "<final_status>" "<final_message>"
```

### Example: Long File Processing
```bash
# Start monitoring
python scripts/monitor_task.py start "video_processing" "progress"

# ... long processing happens here ...

# Stop with final status
python scripts/monitor_task.py stop "video_processing" "success" "Processing complete!"
```

## Manual Updates (Quick Status)

For single status updates without monitoring:

```bash
python scripts/send_status.py "Still fetching data..." "progress" "fetch"
python scripts/send_status.py "Processing records: 250/1000" "progress" "process"
python scripts/send_status.py "Complete! 3 files ready" "success" "final"
python scripts/send_status.py "Error: Connection timeout" "error" "api"
```

## When to Use Each Method

### Use Manual Updates When:
- Task is short (under 30 seconds)
- You want control over when updates are sent
- Task has discrete, meaningful milestones

### Use Periodic Monitoring When:
- Task is long-running (over 1 minute)
- You want consistent "heartbeat" updates every 5 seconds
- Task has long periods of quiet work
- You want to reassure user that work is ongoing

## Message Guidelines

Keep status messages under 140 characters. Examples:

- **Progress**: "Still fetching data..." or "Processing records: 250/1000"
- **Success**: "Complete! 3 files ready" or "Task finished successfully"
- **Error**: "Error: Connection timeout" or "Failed: Missing API key"
- **Warning**: "Continuing despite timeout" or "Partial success: 5/10 files"

## Advanced Usage

### With Additional Details
```bash
python scripts/send_status.py "Uploading..." "progress" "upload" --details "File: report.pdf (2.4MB)"
```

### Different Intervals
```bash
python scripts/monitor_task.py start "data_sync" "progress" --interval 10
```

### Importing for Python Scripts
```python
from send_status import send_status

def long_task():
    send_status("Starting...", "progress", "step1")
    # ... work
    send_status("Step complete", "success", "step1")
```

## Automation with Clawdbot Cron

For scheduled tasks, use Clawdbot's cron feature:

```python
# In a script or session
from cron import add

# Every 5 seconds, check status
job = {
    "text": "Check status update",
    "interval": "5s",
    "enabled": True
}
add(job)
```

This allows status updates even when you're not actively watching.

## Installation

To use this skill, copy the `task-status` folder into your Clawdbot skills directory:

```
C:\Users\Luffy\AppData\Roaming\npm\node_modules\clawdbot\skills\task-status
```

Or add it to your workspace and reference it from `AGENTS.md` or `TOOLS.md`.

Once installed, the skill will be available for any task where you need periodic status updates.

More from aAAaqwq/AGI-Super-Team

SkillDescription
a-fund-monitor监控 A 股基金实时估值与盘后净值,自动判断交易日并生成提醒或分析。
add-leadAdd company/person/relationship to CRM
ads-agentAI-агент для управления Facebook рекламой. Вызывай для анализа, оптимизации, создания кампаний и отчётов.
afrexai-compliance-auditRun internal compliance audits against major governance and security
afrexai-personal-financeComplete personal finance system — budgeting, debt payoff, investing, tax optimization, net worth tracking, and financial independence planning. Use when managing money, building wealth, paying off debt, planning retirement, or optimizing taxes. Zero dependencies.
after-salesUse when managing post-purchase experience, building customer loyalty, or increasing repeat purchases
agent-contactsAI agent contacts — add, list, remove MCP contacts. Use when someone gives an agent URL, or when you need to view/remove contacts.
agent-model-switcher批量查看和切换子 agent 的模型配置,用于统一调整多 agent 的 provider/model 设置。
agent-patternsFormat SPAWN REQUEST messages to launch parallel agents, generate structured agent status reports, and define communication protocols within the sprint system. Use when the user needs to coordinate multiple agents, format spawn requests, produce agent reports, or establish inter-agent communication patterns.
agent-task-confirmUse when confirming whether a dispatched agent task was actually received, activated, and progressing after sessions_send or other task handoff actions.