// Use when the user explicitly types `ov dream` or `ov recall <query>` and the request should be routed to the OpenViking sync/recall CLI instead of handled as normal chat.
| name | ov_dream |
| description | Use when the user explicitly types `ov dream` or `ov recall <query>` and the request should be routed to the OpenViking sync/recall CLI instead of handled as normal chat. |
Use this skill for manual OpenViking sync and recall without occupying the OpenClaw contextEngine slot.
Use this skill when the user message begins with one of these exact prefixes:
ov dreamov recall Do not treat those messages as normal conversation. They are explicit operator commands.
ov dream
Manual sync. Read OpenClaw's sessions.json, sync eligible chat transcripts to OpenViking, then commit each session when new messages exist.
ov recall <query>
Manual recall. Search OpenViking under the default user root URI, viking://user/default.
Trigger when the user message is exactly ov dream.
Execution flow:
Run:
python3 scripts/dream.py dream
Return the sync summary.
The sync command reads OpenClaw session metadata from ~/.openclaw/agents/main/sessions/sessions.json when available. It syncs chat-like session keys such as agent:main:main, :direct:, :channel:, :group:, and :room:.
It must not sync explicitly non-chat sessions, including keys containing :cron:, :heartbeat, :subagent:, :acp:, or :hook:.
Each source session keeps an independent sync cursor in ~/.openclaw/memory/ov_dream_sync.json.
Trigger when the user message starts with ov recall .
This is a hard routing rule for this skill:
ov recall <query>, do not answer from general reasoning.Execution flow:
Extract everything after ov recall as the recall query.
Run:
python3 scripts/dream.py recall "<query>"
Return the relevant memory rows to the user.
If no memories are found, return No memories found.
Rules:
ov recall ... as a manual recall request, not a normal conversation turn.ov recall as the exact recall query.scripts/dream.py resolves correctly.ov dream unless the user separately asks for sync.OPENVIKING_BASE_URL, OPENVIKING_API_KEY, OPENVIKING_AGENT_ID, and optionally OPENVIKING_AUTH_MODE=serverless. The CLI will use Bearer auth and the serverless session message format automatically.Operate and maintain OpenViking server - configure, install, start, stop, and cleanup the server. Use when need to setup or manage OpenViking service deployment.
This skill adds data(like resources) to OpenViking Context Database (aka. ov). Use when an agent needs to add files, data from URLs, or external knowledge during interactions. Trigger this tool when 1. is explicitly requested adding files or knowledge; 2. identifies valuable resources worth importing; 3. the user mentioned adding to OV/OpenViking/Context Database. This skill helps how to use CLI like `ov add-resource`, `ov add-skill` and `ov add-memory` to add resource data, skill files, memory files to OpenViking.
Monitor and manage your OpenCode tasks using helper scripts.
Activate when the user asks about any repository listed in the system prompt under 'OpenViking — Indexed Code Repositories', or when they ask about an external library, framework, or project that may have been indexed. Also activate when the user wants to add, remove, or manage repos. Always search the local codebase first before using this skill.
Search context data(memories, skills and resource) from OpenViking Context Database (aka. ov). Trigger this tool when 1. need information that might be stored as memories, skills or resources on OpenViking; 2. is explicitly requested searching files or knowledge; 3. sees `search context`, `search openviking`, `search ov` request.
Schedule reminders and recurring tasks.