← Back to Skills Marketplace
agent-task-tracker
by
Sunshine-del-ux
· GitHub ↗
· v1.0.0
563
Downloads
0
Stars
3
Active Installs
1
Versions
Install in OpenClaw
/install new-agent-task-tracker
Description
Proactive task state management. Use on EVERY task start, progress update, completion, or failure. Tracks what was requested, what's running (background proc...
Usage Guidance
This skill appears to be what it says (a small persistent task-state tracker) but there are a few things to check before installing: 1) Provenance: the included _meta.json ownerId/version differ from the registry metadata—verify the publisher and source. 2) Invocation: the doc says it should 'trigger automatically' but the registry metadata doesn't force always-on; decide whether you want automatic triggering. 3) Privacy: it records session IDs, PIDs, server names and full commands — avoid storing commands or arguments that contain secrets, and confirm the memory/tasks.md location is access-controlled. 4) Redaction: ask for or add a rule to redact sensitive fields before writing (tokens, passwords, private keys, secret-bearing args). 5) Minimality: consider making it user-invoked or limiting fields recorded to reduce leakage. If you cannot verify the owner or you are uncomfortable with persistent recording of process/host/command details, do not install or only enable it in a constrained/testing environment.
Capability Analysis
Type: OpenClaw Skill
Name: new-agent-task-tracker
Version: 1.0.0
The skill is designed for proactive task state management, storing operational details in `memory/tasks.md`. It instructs the agent to record its own task status, background processes (including session ID, PID, server, and command), and progress updates. While recording commands could log sensitive information if the agent were compromised by another vector, this is a functional requirement for task tracking and not indicative of malicious intent by the skill itself. There are no instructions for data exfiltration, unauthorized network calls, persistence, or other harmful actions. The instructions are clear, focused on the stated purpose, and lack any prompt injection attempts to subvert the agent for malicious ends.
Capability Assessment
Purpose & Capability
Name/description (task tracker that persists state) align with the SKILL.md instructions to read/write a single state file. However the package metadata and included _meta.json disagree (different ownerId and version) and the SKILL.md asserts it “Triggers automatically — not user-invoked” while the registry flags show normal user-invocable/autonomous behavior (always: false). These inconsistencies around provenance and invocation model are unexpected.
Instruction Scope
Instructions explicitly instruct the agent to write/read memory/tasks.md and to record session IDs, PIDs, server names, and full commands. That is coherent with a task tracker, but these fields can contain sensitive data (server identifiers, command-line arguments that may include secrets). The SKILL.md also mandates 'Update the file BEFORE reporting to user (write-first)', which increases the chance of persisting transient or sensitive state. The document does not reference any other files or env vars, which is consistent, but it does not declare the memory/tasks.md path in the skill metadata (no required config paths), so there's a minor mismatch between declared requirements and runtime instructions.
Install Mechanism
Instruction-only skill with no install spec and no code files — low install risk because nothing will be downloaded or written by an installer. The runtime behavior is limited to read/write of a small state file.
Credentials
The skill requests no environment variables or external credentials. That is proportionate to its stated purpose. However, the data it instructs the agent to capture (commands, PIDs, server names) can contain secrets; absence of declared secrets is appropriate but the skill should document redaction rules.
Persistence & Privilege
The skill expects to persist state across sessions (survive resets), which fits its purpose. It does not request 'always: true' or system-wide privileges. The main concern is that the SKILL.md claims automatic triggering (runs on EVERY task event) while registry flags do not indicate forced inclusion — a mismatch that affects how broadly this skill will act in practice.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install new-agent-task-tracker - After installation, invoke the skill by name or use
/new-agent-task-tracker - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Task Tracker skill v1.0.0 — Tracks and maintains live task state to survive session resets.
- Proactively records task lifecycles: start, progress, completion, or failure.
- Tracks background processes with session ID, PID, server, and command.
- Stores state in memory/tasks.md, capped at 50 lines or 2KB.
- Ensures up-to-date status before any user reporting.
- Auto-prunes completed tasks, preserving recent activity only.
Metadata
Frequently Asked Questions
What is agent-task-tracker?
Proactive task state management. Use on EVERY task start, progress update, completion, or failure. Tracks what was requested, what's running (background proc... It is an AI Agent Skill for Claude Code / OpenClaw, with 563 downloads so far.
How do I install agent-task-tracker?
Run "/install new-agent-task-tracker" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is agent-task-tracker free?
Yes, agent-task-tracker is completely free (open-source). You can download, install and use it at no cost.
Which platforms does agent-task-tracker support?
agent-task-tracker is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created agent-task-tracker?
It is built and maintained by Sunshine-del-ux (@sunshine-del-ux); the current version is v1.0.0.
More Skills