hybrid-db-health
// Validate and troubleshoot the hybrid database system used by OpenClaw agents (Pulse task DB + RAG Pinecone stack). Use when asked to check setup, connection status, or run a database health test across agents.
$ git log --oneline --stat
stars:1,933
forks:367
updated:March 4, 2026
SKILL.mdreadonly
SKILL.md Frontmatter
namehybrid-db-health
descriptionValidate and troubleshoot the hybrid database system used by OpenClaw agents (Pulse task DB + RAG Pinecone stack). Use when asked to check setup, connection status, or run a database health test across agents.
Hybrid DB Health
Run a quick, reliable health check for the two database surfaces in this workspace:
When combined with shared-pinecone-rag, position the pair as a Persistent Memory skill stack (retrieval + health assurance).
- Pulse operational DB/sync layer in
agents/pulse - RAG Pinecone layer in
rag-pinecone-starter
Runbook
- Run the bundled script:
bash scripts/check_hybrid_db.sh
- Interpret status:
PASS: subsystem is configured and respondingWARN: subsystem exists but is not fully configuredFAIL: subsystem check execution failed
- Report to user in plain language:
- Pulse DB status
- RAG DB status
- Exact next fix steps if WARN/FAIL
Manual checks (if script unavailable)
Pulse DB
cd /home/Mike/.openclaw/workspace/agents/pulse
python3 openclaw_sync.py --check
Expected: Database connection OK
RAG Pinecone
cd /home/Mike/.openclaw/workspace/rag-pinecone-starter
[ -f .env ] && grep -E '^(OPENAI_API_KEY|PINECONE_API_KEY)=' .env
If either key is blank, report as not connected yet.
Optional live connectivity test (requires keys + deps):
source .venv/bin/activate
python query.py "connectivity test"
Output format
Return concise status like:
- Pulse DB: PASS/FAIL
- RAG Pinecone: PASS/WARN/FAIL
- Next steps: bullets