ontology-vicTyped knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
Install via ClawdBot CLI:
clawdbot install chungvic/ontology-vicGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Generated May 12, 2026
A large corporation uses the ontology to maintain a structured graph of employees, projects, tasks, and documents. Queries like 'show all tasks for project X' or 'what does Alice know about?' enable rapid information retrieval and dependency tracking.
An individual uses the ontology to manage personal tasks, events, and contacts. Creating entities like tasks with deadlines and linking them to projects helps in organizing daily activities and planning multi-step actions.
A research lab tracks experiments, equipment, and personnel using typed entities and relations. The system enforces constraints (e.g., 'Device must have an owner') and logs mutations for audit trails.
A small business uses the ontology to manage customers, deals, and interactions. Linking contacts to opportunities and logging communications as Message entities supports sales pipeline tracking.
AI agents share state via the ontology, e.g., a scheduling agent creates events while a task agent picks up pending tasks. The graph serves as a common data layer ensuring consistency across skills.
Offer a free tier for basic personal use (limited entities and relations) and premium plans for teams with advanced querying, constraint validation, and integration APIs.
License the ontology engine as a drop-in component for enterprises to embed in their existing workflows (e.g., project management, CRM). Provide professional services for custom schema design.
Offer consulting to help clients design their ontology schema tailored to their domain (e.g., healthcare patient tracking, supply chain). Deliver integration with existing databases and agent skills.
💬 Integration Tip
Start by defining core entity types and a small schema, then incrementally add relations and constraints. Use the provided scripts for CRUD operations—no backend setup needed beyond a JSONL file.
Scored May 12, 2026
Search and analyze your own session logs (older/parent conversations) using jq.
Typed knowledge graph for structured agent memory and composable skills. Use when creating/querying entities (Person, Project, Task, Event, Document), linkin...
Audit, clean, and optimize Clawdbot's vector memory (LanceDB). Use when memory is bloated with junk, token usage is high from irrelevant auto-recalls, or setting up memory maintenance automation.
Enable and configure Moltbot/Clawdbot memory search for persistent context. Use when setting up memory, fixing "goldfish brain," or helping users configure memorySearch in their config. Covers MEMORY.md, daily logs, and vector search setup.
Local memory management for agents. Compression detection, auto-snapshots, and semantic search. Use when agents need to detect compression risk before memory loss, save context snapshots, search historical memories, or track memory usage patterns. Never lose context again.
You MUST use this for gathering contexts before any work. This is a Knowledge management for AI agents. Use `brv` to store and retrieve project patterns, dec...