opencode-session-toolkit

Read the local OpenCode SQLite database, run cross-directory session queries, and export sessions to Markdown files.

This skill appears to implement exactly what it says (read a local OpenCode SQLite DB and export sessions), but verify a few things before you install/use it: 1) The SKILL.md and script call the local `opencode` CLI to resolve the DB path (and examples use `sqlite3`, `column`, `date`) — make sure those tools are present and trustworthy; the registry metadata failing to list them is an omission. 2) The script opens the DB read-only (good), but exported sessions may contain sensitive chat/message contents — review the output location and use filters (or avoid --all) if you don't want to export everything. 3) The script requires Python 3.11+ per its header and the shebang is unusual; run it explicitly with a known Python interpreter (python3.11 ./scripts/export_opencode_sessions.py --output-dir <dir> [filters]). 4) If you want higher assurance, inspect the included script (scripts/export_opencode_sessions.py) yourself and test it in a safe/isolated environment. If the metadata were corrected to list the external CLI dependencies and clarify the Python requirement, the coherence concerns would be resolved.

Type: OpenClaw Skill Name: opencode-session-toolkit Version: 1.0.0 The opencode-session-toolkit skill is designed to query and export local OpenCode session data from a SQLite database. The implementation follows security best practices, such as using read-only database connections (via the -readonly flag in shell and mode=ro in Python) and parameterized SQL queries to prevent injection. The Python script scripts/export_opencode_sessions.py includes path sanitization for file exports and lacks any network communication or data exfiltration logic. The instructions in SKILL.md are transparent and include explicit warnings about sensitive data in specific tables.