Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Log agent activities to Mission Claw dashboard with token usage tracking. Use when completing significant tasks, subagent work, or any action worth recording in the activity feed. Triggers on task completion, activity logging, or tracking agent work.
Log agent activities to Mission Claw dashboard with token usage tracking. Use when completing significant tasks, subagent work, or any action worth recording in the activity feed. Triggers on task completion, activity logging, or tracking agent work.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Log significant tasks to the Mission Claw activity feed for tracking agent work, token usage, and project progress.
Mission Claw CLI: The mclaw binary must be installed on the host system. OpenClaw Built-ins: Relies on the session_status tool to retrieve current token usage.
mclaw log "Task description" \ --agent "AgentName" \ --project "ProjectName" \ --status completed \ --duration "Xm Ys" \ --input-tokens N \ --output-tokens N \ --total-tokens N
action - Brief task description (positional argument) --agent - Agent name (e.g., "J", "mission-claw", "type-alchemy") --total-tokens - Total tokens used (always include)
--details - Longer description of work done --project - Project name --status - completed (default), in_progress, or failed --duration - Time taken (e.g., "5m", "1h 30m") --input-tokens / --output-tokens - Token breakdown
Log after completing: Significant development tasks Bug fixes or feature implementations Research or investigation work Configuration changes Any task worth tracking
Before logging, check your session's token usage: Use the built-in session_status tool to see current tokens For subagents, tokens are in the completion announcement
# Feature implementation mclaw log "Added date-time filter to dashboard" \ --agent "mission-claw" \ --project "Mission Claw" \ --status completed \ --duration "10m" \ --total-tokens 15000 # Quick fix mclaw log "Fixed timezone bug" \ --agent "J" \ --project "ContentMorph" \ --duration "2m" \ --total-tokens 3500 # In-progress work mclaw log "Implementing payment flow" \ --agent "J" \ --project "TypeAlchemy" \ --status in_progress
mclaw list # Recent activities mclaw list --agent J # Filter by agent mclaw status # Quick stats and service status mclaw dashboard start # Start web dashboard (localhost:3101 by default)
The CLI logs to a local daemon (defaulting to http://localhost:3100). You can also POST directly to the API: POST http://localhost:3100/api/activity { "action": "Task name", "agent": "J", "project": "Project", "status": "completed", "totalTokens": 5000, "inputTokens": 4000, "outputTokens": 1000 }
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.