Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use when: you want a structured audit -> options -> recommended plan to improve an OpenClaw workspace (cost, model routing, context discipline, delegation, r...
Use when: you want a structured audit -> options -> recommended plan to improve an OpenClaw workspace (cost, model routing, context discipline, delegation, r...
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.
Use this skill to tune an OpenClaw workspace for cost-aware routing, parallel-first delegation, and lean context.
This skill is advisory first. It should produce: audit, options, recommended plan, exact patch proposal, rollback, verification plan. No persistent mutations without explicit approval.
Full audit (safe, no changes) Audit my OpenClaw setup for cost, reliability, and context bloat. Output a prioritized plan with rollback notes. Do NOT apply changes. Context bloat / transcript noise My OpenClaw context is bloating (slow replies / high cost / lots of transcript noise). Identify the top offenders (tools, crons, bootstrap files, skills) and propose the smallest reversible fixes first. Do NOT apply changes. Model routing / delegation posture Propose a model routing plan for (a) coding/engineering, (b) short notifications/reminders, (c) reasoning-heavy research/writing. Include an exact config patch + rollback plan, but do NOT apply changes.
Executive summary Top drivers cost context reliability operator friction Options A/B/C with tradeoffs Recommended plan (smallest safe change first) Exact proposals + rollback + verify
Do not mutate persistent settings without explicit approval. Do not create/update/remove cron jobs without explicit approval. If an optimization reduces monitoring coverage, present options and require choice. Before any approved change, show: exact change, expected impact, rollback plan, post-change verification.
Make maintenance loops truly silent on success.
If you want alerts but want interactive context lean: do the work quietly notify out-of-band with a short human receipt
Keep always-injected files short and load-bearing only. Move long runbooks into references/ or adjacent notes.
A common hidden tax is too many always-visible specialist skills. If a workflow is low-frequency or specialist: prefer on-demand worker/subagent usage, do not keep it permanently ambient in main-chat prompt surface.
Prefer fresh-session /context json or equivalent receipts over βfeels betterβ. High-signal fields include: eligible skills skills.promptChars projectContextChars systemPrompt.chars promptTokens
After any approved optimization, verify: core chat still works recall/behavior did not degrade new session actually picks up the change rollback path is proven, not theoretical
Audit rules + memory: keep restart-critical facts only. Audit skill surface: trim ambient specialists before touching tool surface. Audit transcripts/noise: silence cron and heartbeat success paths. Audit model routing and delegation posture. Recommend the smallest viable change first. Verify on a new session when skill/bootstrap snapshotting exists.
Some runtimes snapshot skills/config per session. If you install/update skills and do not see changes, start a new session. Prefer short SKILL.md + references/ for long runbooks. If context bloat is the main complaint, pair this skill with context-clean-up (audit-only).
references/optimization-playbook.md references/model-selection.md references/context-management.md references/agent-orchestration.md references/cron-optimization.md references/heartbeat-optimization.md references/memory-patterns.md references/continuous-learning.md references/safeguards.md
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.