knowledge-graph
Maintain Clawdbot's compounding knowledge graph under life/areas/** by adding/superseding atomic facts (items.json), regenerating entity summaries (summary.md), and keeping IDs consistent. Use when you need deterministic updates to the knowledge graph rather than manual JSON edits.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/safatinaztepe/knowledge-graphKnowledge Graph (file-based)
Use the bundled Python script to safely update life/areas/**.
Commands
Add a new fact:
python3 skills/knowledge-graph/scripts/kg.py add \
--entity people/safa \
--category status \
--fact "Runs Clawdbot on a Raspberry Pi" \
--source conversation
Supersede an old fact (mark old as superseded + create new fact):
python3 skills/knowledge-graph/scripts/kg.py supersede \
--entity people/safa \
--old safa-002 \
--category status \
--fact "Moved Clawdbot from Pi to a Mac mini"
Regenerate an entity summary from active facts:
python3 skills/knowledge-graph/scripts/kg.py summarize --entity people/safa
Notes
- Entities live under:
life/areas/<kind>/<slug>/ - Facts live in
items.json(array). Summaries live insummary.md. - IDs auto-increment per entity:
<slug>-001,<slug>-002, ... - Never delete facts; supersede them.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-safatinaztepe-knowledge-graph": {
"enabled": true,
"auto_update": true
}
}
}Related Skills
stdio-skill
Stdin/stdout file inbox/outbox bridge for passing files to/from Clawdbot using an MCP stdio server. Use when you want a simple filesystem-backed dropbox: accept files into an inbox, move to tmp for processing, and emit deliverables to an outbox (or a specified path).
project-router
Terminal-first project bootstrapper and workspace context manager. Use when the user asks for /project-style workflows: detect current project, read project context/brief, run standardized targets (build/test/lint/deploy), init a .project bundle via plan/apply, manage artifacts, or expose these actions via MCP server mcp-project-router and CLI project.