Install
openclaw skills install @ernestyu/clawsqlite-knowledgeKnowledge base skill that uses the published clawsqlite CLI for ingest, search, show, and maintenance workflows.
openclaw skills install @ernestyu/clawsqlite-knowledgeThis skill is a thin wrapper around the published clawsqlite PyPI package.
Important: installing this skill from ClawHub installs only the wrapper files.
The clawsqlite CLI is not usable until bootstrap_deps.sh has been run.
After bootstrap, prefer the stable skill-local entry:
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite
It does not:
clawsqlite source treeIt does:
clawsqlite==1.0.12 PyPI package through bootstrap_deps.shclawsqlite knowledge ... CLIThis skill directory is only the instruction shell. Do not store the user's
knowledge DB or private config here. Run clawsqlite knowledge ... from a
knowledge instance home instead. In OpenClaw, use the persistent workspace data
directory:
mkdir -p ~/.openclaw/workspace/data/clawsqlite-knowledge/default
cd ~/.openclaw/workspace/data/clawsqlite-knowledge/default
On a normal non-OpenClaw Linux install, the default falls back to
${XDG_DATA_HOME:-~/.local/share}/clawsqlite-knowledge/default.
The local private config must be:
./clawsqlite.toml
clawsqlite.toml is the single runtime configuration source. Do not create a
second config file, do not rely on shell environment variables for normal
configuration, and do not guess DB paths.
Check or install the required published package:
sh bootstrap_deps.sh
Managed Python environments may not expose a global clawsqlite command on
PATH. Use bin/clawsqlite from this skill directory; it wraps the installed
PyPI package and local fallback target.
Then create or edit ./clawsqlite.toml inside the knowledge instance home. If
no config exists yet:
bin/clawsqlite knowledge maintenance init-config --instance default
cd ~/.openclaw/workspace/data/clawsqlite-knowledge/default
After installation and config editing, validate with:
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge maintenance doctor --json
Doctor is lightweight by default. Only pass --check-llm or
--check-embedding when the user explicitly wants provider roundtrip checks.
clawsqlite CLI.clawsqlite knowledge ....record, maintenance, analysis.clawsqlite knowledge ingest.clawsqlite inside this skill directory.ERROR, ERROR_KIND, and NEXT lines from the CLI directly.Strict URL ingest:
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge record ingest \
--url "https://example.com/article" \
--category web_article \
--json
Strict text ingest:
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge record ingest \
--text "A thought worth saving." \
--title "A saved thought" \
--category thought \
--json
--title is a source_title hint for archive filenames and metadata. In
strict ingest, the stored knowledge title is generated_title from the
configured LLM.
Search:
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge record search "vector database design" --mode hybrid --topk 5 --json
Show one record:
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge record show --id 123 --full --json
Maintenance:
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge maintenance reindex --check --json
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge maintenance cleanup --days 3 --dry-run --json
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge maintenance backup --dry-run --json
Analysis:
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge analysis build-interest-clusters --json
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge analysis report-interest --days 7 --no-pdf
Explicit degraded ingest, only when the user requested it:
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge record ingest \
--text "Local no-network test." \
--title "Test" \
--gen-provider off \
--allow-heuristic \
--allow-missing-embedding \
--json