openviking-skills is agent-read markdown (skill) from volcengine/openviking: Find, use, create, install, share, update, and migrate agent skills stored in OpenViking (viking://~/skills and viking://agent/skills). Use it when a search result, or the session's <available-skills> list where the harness injects one, names a skill that fits the task; when a task looks like one a stored skill would cover; when the user asks to write, save, install, or share a skill from text, a Git repository, or a local folder; when a skill should work in every harness and on every machine; o.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# OpenViking Skills
OpenViking stores skills as data, the same way it stores memories, so a skill
saved there reaches every harness and machine connected to the same account.
Each skill is a directory holding `SKILL.md` plus optional helper files
(`scripts/`, `references/`, ...):
- `viking://~/skills/<name>/` — the user's own skills (`viking://~` expands to
`viking://user/<user_id>`).
- `viking://agent/skills/<name>/` — skills shared with the whole account.
The tools may carry a harness prefix (`mcp__openviking__add_skill`,
`openviking_add_skill`); they are the same tools. `viking://` URIs are database
paths: never pass them to local file tools or shell commands.
## Find a skill
1. `find(query="<what the task needs>", context_type="skill")` ranks skills
from both roots against the task and returns one entry per skill, pointing
at its `SKILL.md`. This works in every harness; start here.
2. If the session begins with an `<available-skills>` block, it lists the
user's own skills first, then shared ones. Not every harness injects one,
and it is a snapshot from session start that drops descriptions or ends
…
Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
GET https://markdownregistry.com/api/v1/artifacts/art_7cpwqbcczkm6nafc
GET https://markdownregistry.com/api/v1/resolve?ref=volcengine/openviking/openviking-skills
GET https://markdownregistry.com/api/v1/blob/1c9b41d449d54923a17992b38be6131a46f30e7de1e40b9588a1ef972e050bc7
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
volcengine/openviking · agent-plugins/skills/openviking-memory/SKILL.md · Recall and persist long-term memory through the OpenViking MCP tools. Use at the start of any substantive task (coding…
volcengine/openviking · agent-plugins/skills/ov-experience-memory/SKILL.md · Retrieve and apply OpenViking Experience memories through the Agent runtime's generic OpenViking search and read tools…
volcengine/openviking · agent-plugins/skills/ov-memory-troubleshoot/SKILL.md · Diagnose OpenViking memory issues by tracing backward from a memory file to its archive memory_diff.json and, when…
volcengine/openviking · bot/workspace/skills/github/SKILL.md · Interact with GitHub using the `gh` CLI. Use `gh issue`, `gh pr`, `gh run`, and `gh api` for issues, PRs, CI runs, and…
volcengine/openviking · bot/workspace/skills/skill-creator/SKILL.md · Create or update AgentSkills. Use when designing, structuring, or packaging skills with scripts, references, and assets.
volcengine/openviking · bot/workspace/skills/summarize/SKILL.md · Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this…
