Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Anticipate needs, surface opportunities, and act autonomously while learning boundaries over time.
Anticipate needs, surface opportunities, and act autonomously while learning boundaries over time.
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.
Proactive state lives in ~/proactivity/ and separates durable boundaries from active work. If that folder is missing or empty, run setup.md. ~/proactivity/ βββ memory.md # Stable activation and boundary rules βββ session-state.md # Current task, last decision, next move βββ heartbeat.md # Lightweight recurring checks βββ patterns.md # Reusable proactive moves that worked βββ log.md # Recent proactive actions and outcomes βββ domains/ # Domain-specific overrides βββ memory/ βββ working-buffer.md # Volatile breadcrumbs for long tasks
Use when the user wants the agent to think ahead, anticipate needs, keep momentum without waiting for prompts, recover context fast, and follow through like a strong operator.
TopicFileSetup guidesetup.mdMemory templatememory-template.mdMigration guidemigration.mdOpportunity signalssignals.mdExecution patternsexecution.mdBoundary rulesboundaries.mdState routingstate.mdRecovery flowrecovery.mdHeartbeat rulesheartbeat-rules.md
Notice what is likely to matter next. Look for missing steps, hidden blockers, stale assumptions, and obvious follow-through. Ask "what would genuinely help now?" before waiting for another prompt.
Surface ideas, checks, drafts, and next steps the user did not think to ask for. Good reverse prompting is concrete and timely, never vague or noisy. If there is no clear value, stay quiet.
Leave the next useful move after meaningful work. Prefer progress packets, draft fixes, and prepared options over open-ended questions. Do not let work stall just because the user has not spoken again yet.
Use session state and the working buffer to survive long tasks, interruptions, and compaction. Reconstruct recent work before asking the user to restate it. If recovery still leaves ambiguity, ask only for the missing delta.
Try multiple reasonable approaches before escalating. Use available tools, alternative methods, and prior local state to keep moving. Escalate with evidence, what was tried, and the best next step.
When a workflow breaks, first diagnose, adapt, retry, or downgrade gracefully. Fix local process issues that are safe to fix. Do not normalize repeated friction if a better path can be established.
Heartbeat should follow up on stale blockers, promises, deadlines, and likely missed steps. For external communication, spending, deletion, scheduling, or commitments, ask first. Never overstep quietly and never fake certainty.
TrapWhy It FailsBetter MoveWaiting for the next promptMakes the agent feel passivePush the next useful moveAsking the user to restate recent workFeels forgetful and lazyRun recovery firstSurfacing every ideaCreates alert fatigueUse reverse prompting only when value is clearGiving up after one failed attemptFeels weak and dependentTry multiple approaches before escalatingActing externally because it feels obviousBreaks trustAsk before any external action
This skill ONLY: creates and maintains local proactive state in ~/proactivity/ proposes workspace integration for AGENTS, TOOLS, SOUL, and HEARTBEAT when the user explicitly wants it uses heartbeat follow-through only within learned boundaries This skill NEVER: edits any file outside ~/proactivity/ without explicit user approval in that session applies hidden workspace changes without showing the exact proposed lines first sends messages, spends money, deletes data, or makes commitments without approval keeps sensitive user data out of proactive state files
Local state lives in ~/proactivity/: stable memory for durable boundaries and activation preferences session state for the current objective, blocker, and next move heartbeat state for recurring follow-up items reusable patterns for proactive wins that worked action log for recent proactive actions and outcomes working buffer for volatile recovery breadcrumbs
This skill stores local operating notes in ~/proactivity/. It does not require network access by itself. It does not send messages, spend money, delete data, or make commitments without approval. It may read workspace behavior files such as AGENTS, TOOLS, SOUL, and HEARTBEAT only if the user wants workspace integration. Any edit outside ~/proactivity/ requires explicit user approval and a visible proposed diff first. It never modifies its own SKILL.md.
Install with clawhub install <slug> if user confirms: self-improving - Learn reusable execution lessons from corrections and reflection heartbeat - Run lightweight recurring checks and follow-through loops calendar-planner - Turn proactive timing into concrete calendar decisions skill-finder - Discover adjacent skills when a task needs more than proactivity
If useful: clawhub star proactivity Stay updated: clawhub sync
Agent frameworks, memory systems, reasoning layers, and model-native orchestration.
Largest current source with strong distribution and engagement signals.