← Back to Skills Marketplace
omprasad122007-rgb

Lite Sqlite

by omprasad122007-rgb · GitHub ↗ · v1.0.0
cross-platform ⚠ suspicious
775
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install lite-sqlite
Description
Fast lightweight local SQLite database for OpenClaw agents with minimal RAM and storage usage. Use when creating or managing SQLite databases for storing age...
README (SKILL.md)

Lite SQLite - Lightweight Local Database

Ultra-lightweight SQLite database management optimized for OpenClaw agents with minimal RAM (~2-5MB) and storage overhead.

Why SQLite?

Zero setup - No server, no configuration, file-based ✅ Minimal RAM - 2-5MB typical usage ✅ Fast - Millions of queries/second ✅ Portable - Single .db file ✅ Reliable - ACID compliant, crash-proof ✅ Cross-platform - Works everywhere Python works

Core Features

  • In-memory mode for temporary data (even faster!)
  • WAL mode for concurrent access
  • Connection pooling
  • Automatic schema migration
  • Built-in backup/restore
  • Query optimization hints

Quick Start

Basic Database Operations

from sqlite_connector import SQLiteDB

# Create database (auto-wal mode enabled)
db = SQLiteDB("agent_data.db")

# Create table
db.create_table("memos", {
    "id": "INTEGER PRIMARY KEY AUTOINCREMENT",
    "title": "TEXT NOT NULL",
    "content": "TEXT",
    "created_at": "TEXT DEFAULT CURRENT_TIMESTAMP",
    "tags": "TEXT"
})

# Insert data
db.insert("memos", [title="First memo", content="Hello world", tags="test"])

# Query data
results = db.query("SELECT * FROM memos WHERE tags = ?", ("test",))

# Update data
db.update("memos", "id = ?", [content="Updated content"], (1,))

# Delete data
db.delete("memos", "id = ?", (1,))

# Close connection
db.close()

In-Memory Database (Fastest)

# Fastest mode - RAM only, no disk I/O
db = SQLiteDB(":memory:")

# Perfect for temporary operations
db.create_table("temp", {...})

# Data persists only during session
# Use for caching, computations, temporary storage

Performance Optimization

Essential Settings

import sqlite3

# WAL mode (Write-Ahead Logging) - 3-4x faster
conn = sqlite3.connect("agent_data.db")
conn.execute("PRAGMA journal_mode=WAL")

# Sync OFF (faster writes, crash-safe with proper shutdown)
conn.execute("PRAGMA synchronous=NORMAL")

# Memory optimization
conn.execute("PRAGMA cache_size=-64000")  # 64MB cache
conn.execute("PRAGMA page_size=4096")

# Temp store in RAM
conn.execute("PRAGMA temp_store=MEMORY")

Query Optimization

# Use indexes for frequent queries
db.create_index("memos", "tags")
db.create_index("memos", "created_at")

# Use prepared statements (automatic in our wrapper)
db.query("SELECT * FROM memos WHERE id = ?", (id,))

# Batch inserts for large datasets
db.batch_insert("memos", rows_data)

Predefined Schemas

Agent Memo Schema (Memory Store)

db.create_table("agent_memos", {
    "id": "INTEGER PRIMARY KEY AUTOINCREMENT",
    "agent_id": "TEXT NOT NULL",           # Which agent created it
    "key": "TEXT NOT NULL",               # Lookup key
    "value": "TEXT",                      # Stored value
    "priority": "INTEGER DEFAULT 0",       # For retrieval ordering
    "created_at": "TEXT DEFAULT CURRENT_TIMESTAMP",
    "expires_at": "TEXT"                  # Optional TTL
})

# Create indexes
db.create_index("agent_memos", "agent_id")
db.create_index("agent_memos", "key")
db.create_index("agent_memos", "expires_at")

Session Log Schema

db.create_table("session_logs", {
    "id": "INTEGER PRIMARY KEY AUTOINCREMENT",
    "session_id": "TEXT NOT NULL",
    "agent": "TEXT NOT NULL",
    "message": "TEXT",
    "metadata": "TEXT",                   # JSON
    "created_at": "TEXT DEFAULT CURRENT_TIMESTAMP"
})

db.create_index("session_logs", "session_id")
db.create_index("session_logs", "created_at")

Cache Schema (TTL-based)

db.create_table("cache", {
    "id": "INTEGER PRIMARY KEY AUTOINCREMENT",
    "key": "TEXT UNIQUE NOT NULL",
    "value": "BLOB",                      # Supports binary data
    "created_at": "TEXT DEFAULT CURRENT_TIMESTAMP",
    "expires_at": "TEXT NOT NULL"
})

# Auto-cleanup expired entries
db.query("DELETE FROM cache WHERE expires_at \x3C ?", (datetime.now().isoformat(),))

db.create_index("cache", "key")
db.create_index("cache", "expires_at")

Advanced Features

Connection Pooling

from sqlite_connector import ConnectionPool

# Pool of connections for concurrent access
pool = ConnectionPool("agent_data.db", max_connections=5)

# Get connection
conn = pool.get_connection()
# Use conn...
pool.release_connection(conn)

Automatic Backup

# Backup database
db.backup("agent_data_backup.db")

# Automatic daily backup
db.auto_backup("backups/", "daily")

Schema Migration

# Add column if not exists
db.add_column("memos", "updated_at", "TEXT DEFAULT CURRENT_TIMESTAMP")

# Migrate data
db.migrate("memos", {
    "old_column": "new_column"
})

Performance Benchmarks

Typical Performance

Operation Rows Time (In-Memory) Time (Disk)
Insert 10,000 0.05s 0.3s
Select (indexed) 10,000 0.001s 0.01s
Select (full scan) 10,000 0.05s 0.5s
Update 1,000 0.01s 0.1s
Delete 1,000 0.01s 0.1s

Memory Usage

  • Base Memory: 2-5MB
  • With 100K rows: ~10-15MB
  • With 1M rows: ~50-100MB
  • In-memory mode: Same as data size + overhead

Best Practices for OpenClaw Agents

1. Choose the Right Mode

# Use :memory: for temporary operations
temp_db = SQLiteDB(":memory:")

# Use file DB for persistent storage
persist_db = SQLiteDB("agent_storage.db")

2. Use Proper Indexes

# Always index columns used in WHERE clauses
db.create_index("table", "column_name")

# Index multiple columns for composite queries
db.create_index("table", "col1, col2")

3. Batch Operations

# Instead of individual inserts:
for row in rows:
    db.insert("table", row)  # Slow!

# Use batch insert:
db.batch_insert("table", rows)  # Fast!

4. Use TTL for Expiring Data

# Auto-cleanup old data
db.cleanup_expired("cache", "expires_at")
db.cleanup_old("logs", "created_at", days=7)

5. Compact Database Periodically

# Reclaim space after many deletes
db.vacuum()  # Should be run during downtime

DuckDB Alternative (Analytics)

For analytical queries (aggregations, joins on large datasets), consider DuckDB:

import duckdb

conn = duckdb.connect(":memory:")

# Faster than SQLite for complex analytics
conn.execute("""
    SELECT COUNT(*) as rows,
           AVG(value) as avg_value
    FROM large_table
""").fetchall()

When to use DuckDB:

  • Analytics on large datasets (>100M rows)
  • Complex aggregations and joins
  • Columnar data operations
  • Statistical analysis

When to use SQLite:

  • Transactional operations
  • Small to medium datasets (\x3C100M rows)
  • Point queries and updates
  • General-purpose storage

Common Patterns

1. Memo Storage

def save_memo(db, agent_id, key, value, ttl_hours=24):
    expires_at = (datetime.now() + timedelta(hours=ttl_hours)).isoformat()
    db.insert("agent_memos", {
        "agent_id": agent_id,
        "key": key,
        "value": json.dumps(value),
        "expires_at": expires_at
    })

2. Session Persistence

def save_session(db, session_id, agent, message, metadata=None):
    db.insert("session_logs", {
        "session_id": session_id,
        "agent": agent,
        "message": message,
        "metadata": json.dumps(metadata) if metadata else None
    })

3. Caching Layer

def cache_get(db, key):
    if expired_key := db.query_one(
        "SELECT value FROM cache WHERE key = ? AND expires_at > ?",
        (key, datetime.now().isoformat())
    ):
        return json.loads(expired_key)
    return None

def cache_set(db, key, value, ttl_seconds=3600):
    expires_at = (datetime.now() + timedelta(seconds=ttl_seconds)).isoformat()
    db.insert_or_replace("cache", {
        "key": key,
        "value": json.dumps(value),
        "expires_at": expires_at
    })

Error Handling

try:
    db.insert("metrics", {...})
except sqlite3.IntegrityError:
    # Duplicate key violation
    pass
except sqlite3.OperationalError:
    # Table doesn't exist or database locked
    pass

Size Optimization Tips

Reduce Storage

  1. Use appropriate data types:

    • INTEGER instead of TEXT for numbers
    • REAL instead of TEXT for floats
    • Use CHECK constraints for validation
  2. Normalize data:

    • Store JSON as TEXT
    • Use TEXT for variable-length strings
    • Avoid storing redundant data
  3. Vacuum regularly:

    db.vacuum()  # Reclaims space after deletes
    
  4. Use WAL instead of journal:

    conn.execute("PRAGMA journal_mode=WAL")
    

Migration from Other Stores

From JSON Files

# Load JSON into SQLite
import json

with open("data.json") as f:
    data = json.load(f)

db.create_table("json_data", {key: "TEXT" for key in data[0].keys()})
db.batch_insert("json_data", data)

From CSV Files

import pandas as pd

df = pd.read_csv("data.csv")
df.to_sql("csv_data", conn, if_exists="replace", index=False)

Troubleshooting

Database Locked Error

# Use WAL mode for concurrent access
conn.execute("PRAGMA journal_mode=WAL")

# Or use connection pool
pool = ConnectionPool("db.db", timeout=5.0)

Slow Queries

# Check query plan
plan = conn.execute("EXPLAIN QUERY PLAN SELECT * FROM ...").fetchall()

# Add indexes
db.create_index("table", "column")

# Use ANALYZE
conn.execute("ANALYZE")

Large Database Size

# Check size info
size_info = conn.execute("PRAGMA page_count, page_size").fetchone()
print(f"Size: {(page_count * page_size) / (1024*1024):.2f} MB")

# Vacuum to reclaim space
db.vacuum()

CLI Tool

The bundled sqlite_cli.py provides command-line access:

# Create database
python scripts/sqlite_cli.py create agent_data.db

# Add table
python scripts/sqlite_cli.py create-table agent_memos -c id:INTEGER:P -c title:TEXT -c content:TEXT

# Insert data
python scripts/sqlite_cli.py insert agent_memos '{"title": "Test", "content": "Hello"}'

# Query data
python scripts/sqlite_cli.py query "SELECT * FROM agent_memos"

# Optimize
python scripts/sqlite_cli.py optimize agent_data.db

Resources

Usage Guidance
This skill appears to do what it claims (a local SQLite wrapper and CLI). Before installing: 1) Only use it with trusted inputs—its execute()/query() and CLI accept arbitrary SQL and unsanitized table/column names (risk of SQL injection or destructive SQL if inputs are attacker-controlled). 2) Be cautious about backup/output paths: the code will create directories and write files and could overwrite sensitive files if given paths you don't expect. 3) Run the skill with limited filesystem permissions (or in a sandbox/container) if possible, and avoid granting it agent-level privileges that let untrusted prompts trigger DB actions. If you need stricter safety, request changes: sanitize identifiers, avoid executing raw SQL from untrusted sources, and add path whitelisting for backups.
Capability Analysis
Type: OpenClaw Skill Name: lite-sqlite Version: 1.0.0 The skill is classified as suspicious due to critical vulnerabilities found in `scripts/sqlite_cli.py` and `scripts/sqlite_connector.py`. The `sqlite_cli.py`'s `query` command directly passes user-supplied SQL to `SQLiteDB.query()` without sanitization, leading to a severe SQL injection vulnerability. Additionally, the `SQLiteDB.backup()` and `auto_backup()` methods in `sqlite_connector.py` allow writing database backups to arbitrary file system paths, posing an arbitrary file write vulnerability. These flaws could be exploited by an attacker to execute arbitrary SQL commands, potentially leading to data exfiltration, modification, or unauthorized file system operations.
Capability Assessment
Purpose & Capability
Name/description match the included code: a lightweight SQLite wrapper and CLI. No unrelated environment variables, binaries, or install steps are requested. The files provide the DB functionality described (table management, queries, backup, pooling).
Instruction Scope
SKILL.md and the code focus on local DB operations. However, the API/CLI intentionally accepts arbitrary SQL (execute/query) and constructs SQL identifiers (table/column names) via string interpolation; the CLI can read JSON files and write backups to arbitrary paths. These behaviors are expected for a DB tool but increase risk if the skill is fed untrusted input or run with broad filesystem access.
Install Mechanism
No install spec or remote downloads; this is instruction+source files only. Nothing is pulled from external URLs or installed automatically.
Credentials
No environment variables, credentials, or external service tokens are requested. The code does not rely on unrelated secrets or configuration.
Persistence & Privilege
Skill does not request always:true and does not modify other skill configs. It performs local filesystem writes (databases, backups). Because autonomous invocation is allowed by default, an agent could run SQL or write files with this skill — consider limiting who/what can invoke it or run it in a restricted environment.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install lite-sqlite
  3. After installation, invoke the skill by name or use /lite-sqlite
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of lite-sqlite — a lightweight, fast, and low-memory SQLite database wrapper for OpenClaw agents. - Provides zero-setup, file-based local database with 2–5MB RAM footprint. - Supports in-memory mode, WAL mode, connection pooling, and automatic schema migration. - Includes built-in functions for backup/restore, query and batch operations, and index management. - Features predefined schemas for agent memos, session logs, and caching with TTL. - Offers best practices and performance optimization recommendations for agent developers. - Documents advanced options like auto-backup, schema migration tools, and guidance on switching to DuckDB for analytics.
Metadata
Slug lite-sqlite
Version 1.0.0
License
All-time Installs 2
Active Installs 2
Total Versions 1
Frequently Asked Questions

What is Lite Sqlite?

Fast lightweight local SQLite database for OpenClaw agents with minimal RAM and storage usage. Use when creating or managing SQLite databases for storing age... It is an AI Agent Skill for Claude Code / OpenClaw, with 775 downloads so far.

How do I install Lite Sqlite?

Run "/install lite-sqlite" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Lite Sqlite free?

Yes, Lite Sqlite is completely free (open-source). You can download, install and use it at no cost.

Which platforms does Lite Sqlite support?

Lite Sqlite is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Lite Sqlite?

It is built and maintained by omprasad122007-rgb (@omprasad122007-rgb); the current version is v1.0.0.

💬 Comments