Self-evolving Context Database for AI Agents. Unify Agent Memory, Knowledge RAG and Skills.
Evaluation
Choose a small task you understand, record expected results, and check actual behavior with fixed inputs. Download the evaluation CSV for initial trials, configuration changes, and upgrade checks.
The v1 samples were verified on isolated local services with OpenViking, CLI, and VikingBot 0.5.2. See the verification record for models, date, executed scope, observed issues, and unverified cases.
Fix the conditions
Record server, CLI, agent or plugin versions, models, deployment mode, identity, and project scope. Preserve inputs and expected sources in isolated demo directories. For comparisons, keep questions, sources, and models consistent where possible, noting differences.
Start with the four files in Resource retrieval, then substitute your own sources. Record preparation time, time to the first useful result, help requests, and pages left along the way to assess onboarding usability.
Check retrieval with your sources
| Case | Question type | Check |
|---|---|---|
| R1 | Direct answer in one source | Accurate answer with an accessible citation |
| R2 | Evidence across sources | Complete evidence and faithful conclusions |
| R3 | No answer in the sources | Missing information clearly identified |
Record import tasks, retrieval results, read URIs, final answers, and citations. For failures, identify the earliest stage that diverged and inspect its logs.
Check memory across two sessions
Follow Memory use to save a test convention, then start a new session with the same identity. Ask for the task without repeating the convention. Record the artifact, recall evidence, and how the answer uses it. Add an unrelated question to check relevance.
| Case | Task | Check |
|---|---|---|
| M1 | A new session needs prior background | Saved conventions are applied |
| M2 | A new session is unrelated | The answer stays focused on the current question |
Inspect Skill and compiled output
Skill use compares two inputs for output structure, fact preservation, and unknowns, with evidence that the agent read the Skill. For Context compilation, open at least one body page and check citations, omissions, and unsupported claims.
Use Version management and Import and export to check restore scope, file content, metadata, and retrieval readiness.
Fill in the record
| Field | What to record |
|---|---|
| Question and input | Complete prompt, source version, or test session |
| Expected facts and sources | Known answers and evidence URIs, recorded before execution |
| Actual answer and sources | Original response and citations |
| Stage and outcome | Import, processing, retrieval, reading, answering, capture, or recall; passed, failed, or unverified |
| Duration | Actual time from submission to a verifiable result |
| Environment and notes | Versions, models, identity, configuration differences, and manual revisions |
Sample rows in the sheet are blank for your results. Define quality criteria beforehand, such as evidence for every key fact, explicit unknowns, and whether the output supports the intended task.
Diagnose and repeat
For missing files, inspect import. For empty search with existing files, inspect indexing and scope. For poor answers with correct matches, inspect agent reads and generation. For memory, follow capture, extraction, recall, and use in order. See Observability and troubleshooting.
Keep each evaluation and repeat the same tasks after changes. Technical validation records describe what was checked. Whether users can finish independently, explain the evidence, and substitute their own inputs is assessed during review and user trials.