OpenViking Experience Memory

Use this skill when the current user request starts or continues an executable task, especially tasks involving tools, files, code changes, data operations, workflow decisions, or multi-step actions.

Do not use this skill for casual chat, pure explanation, or one-off factual Q&A that does not require operational guidance.

Runtime Contract

The agent runtime must expose two tools with these exact names:

• search_experience
• read_experience

OpenViking usage reporting recognizes only completed tool parts with these exact tool names. Calls to generic find, search, read, ov_search, or ov_read do not count as experience recall or injection events.

Tool: search_experience

Purpose: search reusable execution experiences from the OpenViking experience library before assembling task context.

Input schema:

{
  "query": "string",
  "limit": 5
}

Output schema:

{
  "results": [
    {
      "uri": "viking://user/<current_user_id>/memories/experiences/example.md",
      "title": "example",
      "score": 0.82,
      "snippet": "Short summary or matched situation"
    }
  ]
}

Implementation:

The runtime tool calls OpenViking POST /api/v1/search/find with target_uri fixed to the current-user shorthand viking://user/memories/experiences/. Callers provide only query and optional limit; they cannot override or pass target_uri. OpenViking resolves the fixed shorthand against the authenticated request user. Return only canonical experience memory URIs for that user; never hardcode default or another user ID.

Usage reporting:

A completed search_experience tool part is counted as an experience recall event for every results[].uri value.

Tool: read_experience

Purpose: read the full Markdown body of a selected experience and inject it into the agent prompt as task execution guidance.

Input schema:

{
  "uri": "viking://user/<current_user_id>/memories/experiences/example.md"
}

Output schema:

{
  "uri": "viking://user/<current_user_id>/memories/experiences/example.md",
  "content": "Experience Markdown body"
}

Implementation:

Call OpenViking GET /api/v1/content/read?uri=<encoded_uri> for the selected experience URI. Always pass the canonical URI returned by search_experience; do not construct a URI with a hardcoded user ID. The returned content should be inserted into the prompt as operational guidance, not as user profile facts.

Usage reporting:

A completed read_experience tool part is counted as an experience injection event for tool_input.uri or tool_output.uri. In this design, reading an experience through read_experience means the experience was injected into the prompt.

Recommended Flow

1. When a task begins, build a short query from the latest user instruction, current plan, active skill name, and important tool/environment context.
2. Call search_experience before final prompt assembly.
3. Review returned titles/snippets and select only experiences likely to affect execution.
4. Call read_experience for selected experience URIs.
5. Inject the returned Markdown into the prompt under an explicit experience section.
6. Continue task execution.
7. Commit the session normally. The committed session must include the search_experience and read_experience tool parts so OpenViking can report usage.

Prompt Injection Format

Use a compact and explicit block:

<openviking-experience-memory>
The following guidance was retrieved from prior task execution experience.
Use it as operational guidance. Do not treat it as user identity or preference.

<experience uri="viking://user/<current_user_id>/memories/experiences/example.md">
...experience markdown...
</experience>
</openviking-experience-memory>

Commit Requirements

The session committed to OpenViking must preserve tool parts with:

• tool_name
• tool_status
• tool_input
• tool_output
• tool_id

Only tool_status == "completed" is counted. Failed, cancelled, or skipped tool parts are ignored by usage reporting.