ov-add-data

Import local files, URLs, or repositories into OpenViking's context database.

Updated Mar 13, 2026
One-click install
npx skills add https://github.com/dawsonblock/OracleOS --skill ov-add-data-dawsonblock
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ov-add-data
Source: https://github.com/dawsonblock/OracleOS/tree/main/ThirdParty/OpenViking/examples/skills/ov-add-data
Command: npx skills add https://github.com/dawsonblock/OracleOS --skill ov-add-data-dawsonblock

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps agents persist external data into OpenViking's context database by importing resources, files, and memory content when requested.

Core Features & Use Cases

  • Import resources from local files, URLs, or repositories into the viking resources namespace.
  • Attach imported data to the agent context for future retrieval across sessions.
  • Use cases include persisting project documentation, research materials, and memory content for long-term access.

Quick Start

Instruct the agent to run ov add-resource with the target file or URL to import into the OpenViking context.

Frequently Asked Questions about ov-add-data

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import local files and URLs into agent memory for long-term retrieval?

You can import local files and URLs into agent memory by using the ov add-resource command to persist data into OpenViking's context database. This stores resources under the viking://resources namespace for future retrieval across sessions.

Can I persist project documentation and repositories so agents can access them across sessions?

Yes, you can persist project documentation and repositories by instructing the agent to run ov add-resource with the target file, URL, or repository path. The data is asynchronously processed and attached to the viking resources namespace.

Do I need the ov CLI tool configured to import resources into the OpenViking context?

Yes, importing resources into the OpenViking context requires the ov CLI tooling and proper configuration to be installed. This setup enables the asynchronous processing needed to store data under viking://resources.

What is the best way to store external research materials in a context database for agents?

The best way to store external research materials is using the ov add-resource command. It imports external resources into OpenViking's context database, making them available as memories for agents to retrieve during future interactions.

Does importing data into viking resources support asynchronous processing for large repositories?

Yes, importing data into viking resources handles asynchronous processing to store resources. This ensures that adding large repositories or extensive files into the OpenViking context database does not block agent operations.

Why does my imported memory content need to be stored under viking://resources?

Imported memory content must be stored under viking://resources because it serves as the persistent namespace within the OpenViking context database. This location allows agents to reliably retrieve the persisted data across different sessions.