agentleFS
znuaibotznuaibot/openviking-skill/SKILL.md

openviking

Skill0 starsChanged 3 months agoMITView on GitHub

Manages AI agent context via OpenViking — a context database that unifies Memory, Resource, and Skill into a directory structure with semantic search and progressive content loading (L0/L1/L2). Use when adding or searching external knowledge resources, managing agent sessions and memories, operating the virtual filesystem (ls/tree/read/write/mkdir/rm/mv), registering skills, or performing vector retrieval. Not for general file storage, relational databases, or full-text search engines without semantic capabilities.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. wanikua/boluobobo-ai-court-tutorial★ 2.7ksame name
    2. drunkcoding/AgentSkillsArxiv★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Search results → relevant items in top 5 with score > 0.7

    line 115

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

OpenViking context database

OpenViking stores all agent context (Memory / Resource / Skill) as a virtual directory structure with semantic search and L0/L1/L2 progressive loading.

Local deployment (already running)

ItemValue
Serverhttp://localhost:1933 (v0.4.15, auth=trusted)
API keyf0295b83557506298fb9be1df4bf4be059d5c764ffb2b5d79799ae7209616073
Account/Userhermes / hermer-one
CLIopenviking (installed at ~/.local/bin/openviking)
MCP endpointhttp://localhost:1933/mcp (streamable HTTP, 15 tools)
WorkBuddy MCPConfigured in ~/.workbuddy/mcp.json as openviking (streamableHttp)
Embeddingollama qwen3-embedding:4b (dim=1024, localhost:11434)

Three usage paths

1. CLI (already configured):

openviking find "query" --limit 5
openviking ls viking://~/
openviking read viking://resources/foo.md

2. MCP (configured in WorkBuddy — restart WorkBuddy to activate): Tools: find, search, read, list, tree, remember, write, edit, add_resource, list_watches, cancel_watch, grep, glob, forget, health

3. Python SDK:

from openviking_sdk import SyncHTTPClient
client = SyncHTTPClient(url="http://localhost:1933", api_key="f0295b...")
results = client.find("authentication", target_uri="viking://resources/docs/")

Core concepts

ConceptSummary
Context typesResource (external knowledge), Memory (agent cognition), Skill (agent capability)
L0/L1/L2L0 = ~256 char abstract for vector recall; L1 = ~4000 char overview for rerank; L2 = full content, loaded on demand
Viking URIviking://{scope}/{path} — scopes: resources/, ~/memories/, ~/skills/, agent/skills/

Workflow decision tree

Adding knowledge? → See "Resource management" below Searching existing knowledge? → See "Search" below Managing agent memory? → See "Session & memory" below Registering agent skills? → See "Skill management" below Backup or migration? → See references/api-reference.md → "Snapshot & pack" Managing accounts/users/API keys, auth modes, or server start/stop issues? → See references/admin-and-auth.md

Key operations

Resource management

client.add_resource("https://example.com/doc.pdf", to="viking://resources/docs/",
                    tags=["team=backend", "type=api-doc"])

Search

results = client.find("OAuth", target_uri="viking://resources/", limit=10)
overview = client.overview(results[0]["uri"])  # L1
content = client.read(results[0]["uri"])        # L2

Session & memory

session = client.session()
session.add_message("user", "How to implement JWT?")
session.add_message("assistant", "JWT involves signing, verification...")
session.commit(keep_recent_count=5)  # triggers memory extraction

Skill management

client.add_skill({"name": "search-web", "description": "Search the web",
                  "content": "# search-web\n..."})

Error handling

Error codeHTTPAction
NOT_FOUND404Check URI spelling and scope
UNAUTHENTICATED401Verify api_key in client config
EMBEDDING_FAILED500Retry; check model availability
RESOURCE_EXHAUSTED429Back off and retry with delay

Full error reference: see references/api-reference.md

Success criteria

  • Resource added → wait_processed() returns without error
  • Search results → relevant items in top 5 with score > 0.7
  • Session commit → archive_uri returned and task completes
  • L0 → L1 → L2 progression → each level has strictly more content than previous

References

  • API endpoints (full): references/api-reference.md
  • Architecture & data flow: references/architecture-notes.md
  • Admin API, auth modes, key management, server ops: references/admin-and-auth.md
  • Python SDK scenarios (10 examples): examples/scenarios.py
  • TypeScript SDK examples: examples/typescript-sdk.ts
  • CLI command reference: examples/cli-examples.sh
  • Official docs: https://docs.openviking.ai/zh/
  • Source code: D:/work/agents/playgym/OpenViking/

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.