Find and read documents, code, papers, and notes stored in OpenViking. The skill chooses a search method, uses directory summaries to locate relevant files, and cites resource addresses so readers can open the supporting material.
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.
Review the instructions the agent will receive before you install.
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.
| 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(uris) |
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.
find returns URIs with a score. A hit on <dir>/.abstract.md means the
whole directory matched, not that the answer is in the abstract.read that directory's .overview.md to see what is inside.list the directory, or run a scoped find/grep inside it, to reach the
specific file.read the file. For long files, grep first and then read with
offset/limit around the match.Stop as soon as you have what the task needs. Two or three targeted reads beat ten broad ones.
find returns nothing useful, list viking://resources to see what
exists, then search inside the closest directory.limit.viking:// URI of what you used so the user can open it.add_resource with the file path or URL; do not
copy its text in with write.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Schedule reminders and recurring work with the cron tool. Send fixed messages, have an agent execute tasks and report results, or arrange a one-time action at a specified time. List and remove scheduled jobs as needed.
Turn conversation logs, meeting notes, task records, and other OpenViking materials into daily Markdown reports. The skill separates confirmed outcomes from plans, consolidates repeated evidence, and links reported progress, decisions, blockers, and commitments to their sources.
Find relevant past execution experience in OpenViking before starting a task. Check when each experience applies and when it does not, then load suitable guidance while giving current facts, policies, and tool results priority.
Work with GitHub issues, pull requests, and automated checks through the gh command-line tool. Inspect failed workflow steps and their logs, retrieve selected fields, and query the GitHub API for data beyond standard commands.
Convert GitHub resource links into proxy URLs for cloning repositories and downloading files when access is slow. Covers release attachments, raw files, repository archives, and Gist files, with a Python helper for URL conversion.
Set up the OpenViking long-term memory plugin for OpenClaw through conversation. The skill handles installation, configuration, and verification so chat facts can be saved and relevant memories recalled across sessions, using an existing OpenViking server.