experience_loader
Load relevant OpenViking experience memories via case-linked experience candidates before solving a task.
How do I install this agent skill?
npx skills add https://github.com/volcengine/openviking --skill experience-loaderIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill allows the agent to retrieve and apply historical "experience memories" from an internal platform (OpenViking). It includes detailed instructions for the agent to verify the applicability and exclusions of this guidance against current task facts. While this creates an indirect prompt injection surface by ingesting external content, the skill incorporates safety gating and prioritization of current policies to mitigate potential misuse.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
experience_loader
Use this skill before taking task actions when reusable execution experience may help.
Required workflow
- Before taking task actions, call
search_experiencewith a natural-language query that describes the current task. - Build the query from the current domain, user intent, target object, requested operation, policy keywords, and likely tool/action family. Avoid vague queries such as "help user".
- Review the returned candidates. Each candidate is a matched case plus linked experience entries; each experience entry includes its
name,uri, and a shortsituationsnippet describing its applicability and exclusions. - Gate before reading. For each linked experience, read its
situationsnippet and check whether the current task matches the experience's applicability AND does NOT match any of its exclusions / "不适用于" / "does not apply to" items. Skip experiences whose situation explicitly excludes your case (e.g. wrong cabin class, flights already flown, different action family, or different change type). Only callread_experienceon experiences that plausibly apply after this check. If no experience passes the gate, continue without experience guidance. - You may call
search_experiencemultiple times with refined keywords, and you may callread_experiencemultiple times for the experiences that pass the gate. - Treat loaded experiences as reusable guidance, not as current-task truth. Current policy, current tool results, and current user facts override prior experience.
- Re-verify after reading. Even after
read_experience, before acting on the experience, check its full## Situationagainst current facts you have obtained from tools (cabin class, reservation status, flight dates, segment state, etc.). If any "不适用于" / exclusion condition matches the current task now that you have concrete facts, DISCARD the experience and proceed from policy and tool results instead — do NOT apply its Approach or Reflect. - Multi-intent tasks (e.g. "cancel, then book", "upgrade then change flight", "refuse a modification then offer a fallback") may legitimately require more than one experience; gate and apply each segment's experience independently. Do not end the task (
done/transfer_to_human_agents) just because one segment's experience reaches a local return marker — check whether the user has a remaining intent. - If no linked experience is plausibly relevant after gating, continue without experience guidance.
Local return markers in loaded experiences
Experience return markers are local to the covered intent/subtask. They are not whole-task success/failure labels and are not automatic permission to call done.
RETURN_COMPLETED: the specific intent/subtask covered by this experience has been completed, usually after the required business read/write tool calls and required customer communication. If the user has another independent intent, continue with that next intent instead of ending the conversation.RETURN_BLOCKED(reason="..."): the covered intent/subtask cannot proceed under the current facts, policy, missing input, refusal boundary, or escalation boundary. Perform any required communication/escalation from the experience, then continue other remaining user intents if they are still actionable.RETURN_NOT_APPLICABLE: the experience does not match the current facts; discard it and use another applicable experience or current policy/tool facts.
Refusal, no-option, policy-ineligible, missing-input, and transfer_to_human_agents branches should be interpreted as RETURN_BLOCKED(...) for that local intent, not as whole-task completion. Before ending globally, verify that every user intent is completed, blocked, not applicable, or explicitly transferred/stopped by the user/environment.
Tools
search_experience(query, limit=10): searches OpenVikingmemories/casesunder the current user, reads each matched case's## Linked Experiencessection, and returns JSON candidates with case score, case URI, task signature, input summary, and linked experience entries (each withname,uri, and asituationsnippet from the experience's## Situationsection).read_experience(experience_uri): reads one OpenViking experience memory by full URI and returns Markdown.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/volcengine/openviking/experience_loader">View experience_loader on skillZs</a>