ov-experience-memory — Claude Code skill: what it does, how to install
Retrieves OpenViking operational memories during coding, migrations, and deployment. It equips agents with past debugging steps to resolve recurring failures.
npx skills add volcengine/OpenViking --skill ov-experience-memory -a claude-codeWhat ov-experience-memory does
This skill directs the agent to query viking://~/memories/experiences before running multi-step tasks. It targets executable operations such as refactoring, environment setup, and pipeline recoveries. The agent skips memory lookups for basic conversation or straightforward factual queries.
The search focuses on a single targeted query with the task goal and any visible error signatures. The agent inspects top hits and selects up to three files, ignoring .abstract.md sidecars. Past procedures act strictly as advice. Current safety rules and user instructions always take priority.
The agent runtime must have registered OpenViking search and URI read tools available. On servers older than v0.4.16, the home alias fails with an INVALID_URI error, requiring the explicit user ID in the target path.
What it helps with
- pull diagnostic routines for recurring deployment failures
- retrieve verified operational steps before running migrations
- check past environment fixes during multi-step setup
- filter out irrelevant memory files and summary sidecars
Example prompts for the agent
- Resolve the Kubernetes private registry pull failure using our saved operational memories.
- Deploy the updated worker service and check OpenViking for previous pipeline errors.
How to install ov-experience-memory
1Skills CLI (Vercel)
npx skills add volcengine/OpenViking --skill ov-experience-memory -a claude-code2Manually: put the files in place
~/.claude/skills/ov-experience-memory/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ov-experience-memory/
1Skills CLI (Vercel)
npx skills add volcengine/OpenViking --skill ov-experience-memory -a codex2Manually: put the files in place
.agents/skills/ov-experience-memory/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add volcengine/OpenViking --skill ov-experience-memory -a cursor2Manually: put the files in place
.cursor/skills/ov-experience-memory/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install volcengine/OpenViking ov-experience-memory2Manually: put the files in place
.github/skills/ov-experience-memory/SKILL.md1Skills CLI (Vercel)
npx skills add volcengine/OpenViking --skill ov-experience-memory -a gemini-cli2Platform CLI
gemini skills install https://github.com/volcengine/OpenViking --path agent-plugins/skills/ov-experience-memoryManually: put the files in place
.devin/skills/ov-experience-memory/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add volcengine/OpenViking --skill ov-experience-memory -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set2
The whole set →Similar
Questions about ov-experience-memory
How do I install ov-experience-memory in Claude Code?
Run npx skills add volcengine/OpenViking --skill ov-experience-memory -a claude-code in your terminal. This sets up the skill under ~/.claude/skills/ov-experience-memory/SKILL.md.
When does ov-experience-memory trigger?
The skill activates for practical, multi-step actions like code refactoring, infrastructure adjustments, and incident recovery. Casual chat and basic factual questions do not trigger memory searches.
How does it handle servers without the home alias?
OpenViking releases prior to v0.4.16 reject viking://~ with HTTP 400. In such cases, the agent extracts the user identifier from session evidence and retries against viking://user/<user_id>/memories/experiences.
