ov-resources
Search and read documents, repos, URLs, and other resources stored in OpenViking under viking://resources/. Use whenever the user asks about docs, specs, codebases, papers, or notes that were added to OpenViking ("check the docs", "what does our design doc say", "find it in OpenViking"), or when a task needs reference material this session does not have. Covers picking between find, grep, glob, and list, and drilling from a hit down to the exact file.
How do I install this agent skill?
npx skills add https://github.com/volcengine/openviking --skill ov-resourcesIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill provides tools for searching and reading documents within the OpenViking platform. While it does not perform dangerous operations directly, it is designed to process untrusted external content, which could contain instructions intended to manipulate the agent.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
What does this agent skill do?
OpenViking Resources
Resources are documents a user added to OpenViking (files, repos, URLs).
They live in a file tree under viking://resources/ (and sometimes
viking://user/<id>/resources/ for user-private ones). Each directory has two
summaries next to its files:
.abstract.md— one paragraph: what the directory holds (L0).overview.md— a structured overview of its contents (L1)
Read summaries first and open full files last. The summaries exist so you can decide where to look without reading everything.
Pick the tool
| You know… | Use |
|---|---|
| roughly what it is about | find(query, target_uri="viking://resources") |
| an exact word, name, or error string | grep(uri, pattern=[...]) |
| a file name or extension | glob(pattern, uri) e.g. **/*.pdf |
| where it is | list(uri) and read(uri), or read(uris=[...]) for several files |
Default to find. Scope it with target_uri as soon as you know which
resource you are in — narrower scopes give better hits. Use search instead
of find only when the question is vague and needs intent analysis.
Drill down
findreturns URIs with a score. A hit on<dir>/.abstract.mdmeans the whole directory matched, not that the answer is in the abstract.readthat directory's.overview.mdto see what is inside.listthe directory, or run a scopedfind/grepinside it, to reach the specific file.readthe file. For long files,grepfirst and thenreadwithoffset/limitaround the match.
Stop as soon as you have what the task needs. Two or three targeted reads beat ten broad ones.
Tips
- If
findreturns nothing useful,list viking://resourcesto see what exists, then search inside the closest directory. - Low scores (under ~0.4) are usually noise; rephrase with the domain's
own terms rather than raising
limit. - Cite the
viking://URI of what you used so the user can open it. - To add a new resource, use
add_resourcewith the file path or URL; do not copy its text in withwrite.
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/ov-resources">View ov-resources on skillZs</a>