← Back to Skills Marketplace
2508
Downloads
1
Stars
9
Active Installs
2
Versions
Install in OpenClaw
/install dex
Description
Task tracking for async/multi-step work. Use dex to create, track, and complete tasks that span multiple sessions or require coordination (e.g., coding agent dispatches, PR reviews, background jobs). Tasks stored as JSON files in .dex/tasks/.
README (SKILL.md)
Dex Task Tracking
Track async work: coding agent dispatches, multi-step projects, anything needing follow-up.
Commands
dex create -d "Description" --context "Background, goal, done-when"
dex list # Pending tasks
dex list --all # Include completed
dex show \x3Cid> # View task
dex show \x3Cid> --full # Full context
dex complete \x3Cid> --result "What was done, decisions, follow-ups"
dex edit \x3Cid> --context "Updated context"
dex delete \x3Cid>
Task Structure
- Description: One-line summary
- Context: Background, requirements, done criteria
- Result: What was built, decisions, follow-ups
Example
# Before dispatching agent
dex create -d "Add caching to API" --context "Workspace: feat1 (100.x.x.x)
Branch: feat/cache
Done when: PR merged, CI green"
# After work complete
dex complete abc123 --result "Merged PR #50. Redis caching with 5min TTL."
Storage
.dex/tasks/{id}.json — one file per task, git-friendly.
Usage Guidance
This is an instruction-only skill that expects a 'dex' CLI and stores tasks under .dex/tasks/*.json, but it does not provide or declare that CLI. Before installing or using it: 1) confirm you have a trustworthy 'dex' binary available (know its source and verify it), or request the skill author supply an install spec or source repo; 2) be aware the agent will read/write files in a .dex directory — do not store secrets or sensitive configs in tasks; 3) test in a restricted environment to observe what commands the agent runs; 4) if you cannot verify the origin of the 'dex' tool, treat the skill cautiously or mark it untrusted. The mismatch between required tooling and the skill metadata is the primary concern here.
Capability Analysis
Type: OpenClaw Skill
Name: dex
Version: 1.1.0
The skill bundle describes a local task tracking tool named 'dex'. The `SKILL.md` file provides instructions for creating, listing, showing, completing, editing, and deleting tasks, which are stored as JSON files in a `.dex/tasks/` directory. There is no evidence of data exfiltration, malicious execution, persistence mechanisms, or prompt injection attempts against the AI agent. The content is clearly aligned with the stated purpose and lacks high-risk behaviors.
Capability Assessment
Purpose & Capability
The stated purpose (local task tracking stored as JSON in .dex/tasks/) matches the SKILL.md content. However, the SKILL.md relies on a 'dex' CLI tool (commands like dex create, dex list, dex complete) while the skill metadata lists no required binaries or install steps — this is an incoherence (the skill needs a CLI but does not declare or install it).
Instruction Scope
Instructions are narrowly scoped to creating, listing, showing, editing, completing, and deleting tasks and to storing tasks under .dex/tasks/{id}.json — all consistent with the described purpose. The SKILL.md does tell the agent to run filesystem-affecting commands (create/edit/delete files in .dex), so the agent will need local file write/read permission; nothing in the instructions asks for unrelated files, credentials, or external endpoints.
Install Mechanism
There is no install specification and no code shipped with the skill, yet the runtime instructions require a 'dex' command-line tool. That gap could cause failures or lead operators to install an unvetted binary themselves. Because the skill is instruction-only, there is no installation risk from the skill bundle itself, but the missing install step is a practical and security concern.
Credentials
The skill declares no environment variables, no credentials, and no config paths beyond the .dex/tasks folder it manages. The requested access (local task files) is proportional to the stated purpose.
Persistence & Privilege
always is false and autonomous invocation is permitted (platform default). The skill writes to its own .dex/tasks directory per design; it does not request elevated or cross-skill privileges. This level of persistence/privilege is appropriate for a local task-tracking tool.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install dex - After installation, invoke the skill by name or use
/dex - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.1.0
Trimmed for conciseness
v1.0.0
Initial release - task tracking for async/multi-step work
Metadata
Frequently Asked Questions
What is Dex Task Tracking?
Task tracking for async/multi-step work. Use dex to create, track, and complete tasks that span multiple sessions or require coordination (e.g., coding agent dispatches, PR reviews, background jobs). Tasks stored as JSON files in .dex/tasks/. It is an AI Agent Skill for Claude Code / OpenClaw, with 2508 downloads so far.
How do I install Dex Task Tracking?
Run "/install dex" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Dex Task Tracking free?
Yes, Dex Task Tracking is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Dex Task Tracking support?
Dex Task Tracking is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Dex Task Tracking?
It is built and maintained by gricha (@gricha); the current version is v1.1.0.
More Skills