Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Token-efficient Claude Code workflow. Other skills burn tokens polling tmux every 30s — this one uses completion callbacks and only checks when notified. Obs...
Token-efficient Claude Code workflow. Other skills burn tokens polling tmux every 30s — this one uses completion callbacks and only checks when notified. Obs...
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. Then review README.md for any prerequisites, environment setup, or post-install checks. 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. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Production-grade Claude Code workflow that doesn't waste your tokens.
Most Claude Code tmux skills work like this: Start task → Poll every 30s → Poll → Poll → Poll → Done 🔥 tokens 🔥 🔥 🔥 Each poll reads 100-200 lines of terminal output, feeds it to your agent, and burns tokens deciding "is it done yet?" A 20-minute task = 40 polls = thousands of wasted tokens.
Start task (with callback) → Wait → 📩 Notification → Read result (50 lines) 😴 zero tokens ⚡ one read The task itself tells you when it's done. Your agent sleeps until notified. One lightweight check confirms the result. That's it.
Approach20-min taskTokens burnedPoll every 30s40 reads × ~500 tokens~20,000Poll every 60s20 reads × ~500 tokens~10,000This skill1 notification + 1 read~500 80-97% token savings on supervision alone.
Before spawning Claude Code, ask: SituationAction< 3 files involvedDon't start CC. Just read + edit directly.Single bug fixDon't start CC. Faster to fix inline.Need extensive context exploration✅ Start CCMulti-file refactor✅ Start CCNew feature (5+ files)✅ Start CC The fastest token savings come from not spawning a session at all.
# Start a task — note the callback at the end bash {baseDir}/scripts/start.sh --label auth-refactor --workdir ~/project --task "Refactor auth module to use JWT. When completely finished, run: openclaw system event --text \"Done: JWT auth refactor complete\" --mode now" That's the key line: openclaw system event --text "Done: ..." --mode now. The task notifies your agent on completion. No polling needed.
bash {baseDir}/scripts/start.sh --label my-feature --workdir ~/project \ --task-file /path/to/requirements.md --mode auto Write detailed requirements once upfront → fewer mid-task corrections → fewer tokens.
# Lightweight check — 50 lines, minimal tokens bash {baseDir}/scripts/monitor.sh --session my-task --lines 50 # JSON mode — structured, even fewer tokens for agent parsing bash {baseDir}/scripts/monitor.sh --session my-task --json # Send follow-up (use sparingly — write requirements upfront instead) bash {baseDir}/scripts/send.sh --session my-task --text "Also add unit tests" # Compact context when running long bash {baseDir}/scripts/send.sh --session my-task --compact
# List all active sessions bash {baseDir}/scripts/list.sh # human-readable bash {baseDir}/scripts/list.sh --json # structured # Stop sessions bash {baseDir}/scripts/stop.sh --session my-task bash {baseDir}/scripts/stop.sh --all
tmux -L cc attach -t cc-<label>
1. DECIDE — Is this a 3+ file task? No → just edit. Yes → continue. 2. START — start.sh with detailed task + completion callback 3. WAIT — Do other work. Zero tokens spent watching. 4. NOTIFIED — Receive "Done: ..." event 5. CHECK — monitor.sh --lines 50 to confirm result 6. CLEANUP — stop.sh to end session Fallback: If no notification after 15 minutes, one lightweight poll with --json.
Always append to your task prompt: When completely finished, run this command to notify: openclaw system event --text "Done: [brief description]" --mode now This is what makes the whole approach work. The task signals completion; your agent doesn't need to guess.
ModeFlagBehaviorauto--mode autoFull permissions, runs freely (default)
Isolated tmux socket (-L cc) — doesn't interfere with your tmux sessions cc- prefix on all sessions — easy to list/filter Bracketed paste for multi-line prompts — no escaping issues JSON output from list/monitor — agent-friendly, fewer tokens to parse
ScriptPurposescripts/start.shLaunch CC in tmux with taskscripts/monitor.shLightweight output capturescripts/send.shSend prompts / compact / approvescripts/list.shList active sessionsscripts/stop.shKill sessions
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.