task-status▌
aaaaqwq/claude-code-skills · updated Apr 8, 2026
The monitor_task.py script provides automatic updates:
Task Status Skill
Quick Start
Manual Status Updates
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)
# 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
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
python scripts/monitor_task.py stop "<task_name>" "<final_status>" "<final_message>"
Example: Long File Processing
# 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:
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
python scripts/send_status.py "Uploading..." "progress" "upload" --details "File: report.pdf (2.4MB)"
Different Intervals
python scripts/monitor_task.py start "data_sync" "progress" --interval 10
Importing for Python Scripts
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:
# 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.
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.6★★★★★45 reviews- ★★★★★Zaid Gonzalez· Dec 24, 2024
Solid pick for teams standardizing on skills: task-status is focused, and the summary matches what you get after install.
- ★★★★★Charlotte Nasser· Dec 20, 2024
task-status is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Ganesh Mohane· Dec 8, 2024
Keeps context tight: task-status is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Isabella Gupta· Dec 4, 2024
Registry listing for task-status matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Rahul Santra· Nov 27, 2024
Registry listing for task-status matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Anaya Ndlovu· Nov 23, 2024
I recommend task-status for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
- ★★★★★Henry Lopez· Nov 23, 2024
Keeps context tight: task-status is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Amelia Srinivasan· Nov 15, 2024
We added task-status from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Henry Ndlovu· Nov 11, 2024
task-status reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Pratham Ware· Oct 18, 2024
task-status reduced setup friction for our internal harness; good balance of opinion and flexibility.
showing 1-10 of 45