task-status — Claude Code skill: what it does, how to install
The task-status skill posts brief progress updates for long-running work, then reports completion or failure. It fits multi-step tasks with quiet periods.
MIT 173 installs ★ 121 updated 2026-10-20
npx skills add aAAaqwq/AGI-Super-Team --skill task-status -a claude-codeWhat task-status does
task-status provides manual updates through scripts/send_status.py. A call includes the message, a status category such as progress, success, error, or warning, and a step label. Extra context can be passed with --details. Status text is meant to stay under 140 characters.
Long jobs can use scripts/monitor_task.py. Its start action runs a background monitor, while stop sends the final state and message. The monitor posts a heartbeat every 5 seconds in the supplied workflow, and --interval can change that setting. Python code can import the send_status helper. Python is required to run these scripts; a missing API key is handled as an error condition.
What it helps with
- post progress for a long-running operation
- keep a background heartbeat running
- report a task’s final success or failure
- attach extra details to a status update
Example prompts for the agent
- Use
task-statusto post “Fetching data” with the step labelfetch. - Start monitoring a long file-processing job, then stop it with a success message when the work ends.
- Send an
errorstatus for a connection failure and include the cause in the message.
How to install task-status
1Skills CLI (Vercel)
npx skills add aAAaqwq/AGI-Super-Team --skill task-status -a claude-code2Manually: put the files in place
~/.claude/skills/task-status/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/task-status/
1Skills CLI (Vercel)
npx skills add aAAaqwq/AGI-Super-Team --skill task-status -a codex2Manually: put the files in place
.agents/skills/task-status/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add aAAaqwq/AGI-Super-Team --skill task-status -a cursor2Manually: put the files in place
.cursor/skills/task-status/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install aAAaqwq/AGI-Super-Team skills/task-status2Manually: put the files in place
.github/skills/task-status/SKILL.md1Skills CLI (Vercel)
npx skills add aAAaqwq/AGI-Super-Team --skill task-status -a gemini-cli2Platform CLI
gemini skills install https://github.com/aAAaqwq/AGI-Super-Team --path skills/task-statusManually: put the files in place
.devin/skills/task-status/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add aAAaqwq/AGI-Super-Team --skill task-status -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about task-status
How do I install task-status in Claude Code?
Run npx skills add aAAaqwq/AGI-Super-Team --skill task-status -a claude-code. The installed skill is available at ~/.claude/skills/task-status/SKILL.md.
What does task-status do?
It sends short task updates either on demand or through a background monitor. The skill supports progress, success, error, and warning states.
How often does the monitor send updates?
The workflow sends a heartbeat every 5 seconds. You can change the interval with --interval.
Source text
SKILL.md · MIT
---
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.
© aAAaqwq · MIT · aAAaqwq/AGI-Super-Team