---
slug: "claw-sqlite-knowledge-x"
source_type: "clawhub"
source_url: "https://clawhub.ai/skills/clawsqlite-knowledge"
repo: ""
source_file: "description"
---
---
name: clawsqlite-knowledge
description: Knowledge base skill that uses the published clawsqlite CLI for ingest, search, show, and maintenance workflows.
version: 1.0.12
metadata: {"openclaw":{"homepage":"https://github.com/ernestyu/clawsqlite","tags":["knowledge","sqlite","search","cli"],"requires":{"bins":["python"],"env":[]},"dependencies":{"python":["clawsqlite==1.0.12"]},"install":[{"id":"clawsqlite_knowledge_bootstrap","kind":"bash","label":"Install clawsqlite Python package from PyPI","script":"set -e && cd {baseDir} && bash bootstrap_deps.sh"}]}}
---

# ClawSQLite Knowledge Skill

This 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:

```bash
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite
```

It does not:

- vendor the `clawsqlite` source tree
- clone any Git repository
- define a second runtime layer on top of the official CLI
- redefine a parallel JSON API

It does:

- install the pinned `clawsqlite==1.0.12` PyPI package through `bootstrap_deps.sh`
- guide agents to use the official `clawsqlite knowledge ...` CLI
- document common workflows for knowledge-base operations

## Knowledge Instance Home

This 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:

```bash
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:

```text
./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.

## Bootstrap

Check or install the required published package:

```bash
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:

```bash
bin/clawsqlite knowledge maintenance init-config --instance default
cd ~/.openclaw/workspace/data/clawsqlite-knowledge/default
```

## Validate

After installation and config editing, validate with:

```bash
<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.

## Agent Rules

- Use only the official `clawsqlite` CLI.
- Stay in the knowledge instance home when running `clawsqlite knowledge ...`.
- Use the three-level command tree: `record`, `maintenance`, `analysis`.
- Do not call removed flat commands such as `clawsqlite knowledge ingest`.
- Do not vendor, clone, or patch `clawsqlite` inside this skill directory.
- Do not use degraded ingest unless the user explicitly asks for it.
- Report `ERROR`, `ERROR_KIND`, and `NEXT` lines from the CLI directly.

## Common Commands

Strict URL ingest:

```bash
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge record ingest \
  --url "https://example.com/article" \
  --category web_article \
  --json
```

Strict text ingest:

```bash
<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:

```bash
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge record search "vector database design" --mode hybrid --topk 5 --json
```

Show one record:

```bash
<workspace>/skills/clawsqlite-knowledge/bin/clawsqlite knowledge record show --id 123 --full --json
```

Maintenance:

```bash
<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:

```bash
<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:

```bash
<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
```