Context compilation
Turn the four Lighthouse sources into a small wiki, then open its body page to verify evidence and unknowns.
About LLM Wiki
LLM Wiki uses a language model to organize information scattered across documents, meeting notes, and feedback into an interlinked Markdown knowledge base. Related information about a project or concept can be brought together on one page, reached through an index, and linked back to its original sources for readers and agents to inspect, verify, and reuse.
For example, the Lighthouse project's goals, feedback process, and preparation tasks are spread across four sources. Compilation can bring them together on a project page, identify undecided dates and budget, and cite the sources for key facts. Readers can start with that page and follow its references for details.
In OpenViking, the LLM Wiki Skill defines how to organize the material, and the Compile Runtime reads the sources and generates pages. The wiki remains available for reading and retrieval; check key conclusions against the original sources. The following walkthrough compiles the Lighthouse materials.
Prepare sources and a Skill
Use a service with a configured Compile Runtime. The local default is VikingBot installed with openviking[bot] and enabled with --with-bot; see the quickstart for model and connection setup.
Complete the source-import step in Resource retrieval, and confirm viking://resources/onboarding-en-v1 is readable. Download Wiki Skill v1 and install it into a shared skills directory you can write:
ov add-skill ./llm-wiki-v1.zip -p viking://agent/skills --wait
ov read viking://agent/skills/llm-wiki/SKILL.mdThe package contains the project's LLM Wiki Skill. Compilation calls the model and writes output into a new directory.
For image sources, Compile prepares a temporary model input with a long edge of at most 2,048 pixels and an inline size of at most 3.75 MiB. Images within both limits are sent as-is. Larger static images are resized or compressed when needed, and citations still point to the original resource. The source download precheck is 20 MiB, and images above 24 million pixels are rejected before raster decoding.
Submit compilation
Create a named configuration with the sources, target, Skill, and optional --instruction and --args.
ov compile create --compile-name lighthouse-wiki \
--from viking://resources/onboarding-en-v1 \
--to viking://resources/onboarding-wiki-en-v1 \
--skill viking://agent/skills/llm-wiki \
--instruction "Generate index.md and entity/lighthouse.md in English. Explain the isolated-network feedback pilot using the project, feedback, and meeting sources. Preserve full viking:// source URIs and identify undecided dates. Write only inside the target directory."Create the configuration once. Submit each run by name:
ov compile --compile-name lighthouse-wikiExecution reuses the configuration's saved from, to, skill, and instruction.
Record the returned cmp_... task ID and inspect progress:
ov task status <cmp_task_id>Check every 5 seconds for up to 5 minutes initially. Read outputs after completed. If still running, check later or request cancellation with ov task cancel <cmp_task_id>. On failure, inspect the task error and Compile Runtime configuration.
After compilation, the target directory should contain an index and a project page. See the sample Wiki page for content organization and source citations, then follow the checks below to review your output.
The first run is full. Subsequent runs use the last successful baseline. The name is required, case-sensitive, and unique for the current user within an account; it contains Han characters, ASCII letters, digits, underscores, or hyphens. ASCII-only names allow up to 64 characters. A name containing any Han character allows up to 32 characters in total. The first character cannot be a hyphen. Different users can use the same name. See configuration and execution for schedules and invocation timestamps.
The direct ov compile --from … --to … --skill … form is deprecated and still performs a one-off full compile.
Open the body page
ov tree viking://resources/onboarding-wiki-en-v1
ov read viking://resources/onboarding-wiki-en-v1/index.md
ov read viking://resources/onboarding-wiki-en-v1/entity/lighthouse.mdIf filenames differ, use the tree and index to locate the body page. Check the isolated network, offline installer and local directory, Friday feedback exports, template and rehearsal, and undecided dates and budget. Open cited sources to verify each conclusion.
| Observation | Check |
|---|---|
| Runtime unavailable | Bot dependencies and the server's compile runtime configuration |
| Source or Skill missing | URI, read permissions, and processing results |
| Evidence missing | Actual read records and citations; refine the instruction and retry with a new target |
Completion means a readable, navigable body page with evidence for key facts. See the LLM Wiki example for structures, page types, and visualization. To clean up, identify the demo target in Studio, preserve any needed output, and delete the directory.