turso-memory-verification

Verify memory persistence across Turso/libSQL databases during release validation.

4|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/d-o-hub/chaotic_semantic_memory --skill turso-memory-verification
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: turso-memory-verification
Source: https://github.com/d-o-hub/chaotic_semantic_memory/tree/main/.agents/skills/turso-memory-verification
Command: npx skills add https://github.com/d-o-hub/chaotic_semantic_memory --skill turso-memory-verification

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies memory persistence across Turso/libSQL databases before releases to ensure import/export, data roundtrips, and serialization do not regress.

Core Features & Use Cases

  • End-to-end memory persistence verification across local sqlite databases and Turso/libSQL backends
  • Validate JSON and binary export/import round-trips to ensure data integrity
  • Detect serialization regressions and preserve metadata through export/import cycles
  • Suitable for release pipelines and CI to guard against regression in persisted memory

Quick Start

Run the Local SQLite Test workflow to verify that import/export and data roundtrips work correctly before a release.

Frequently Asked Questions about turso-memory-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify memory persistence across Turso and libSQL databases before a release?

To verify memory persistence, run the Local SQLite Test workflow to validate JSON and binary export/import round-trips, ensuring data integrity and metadata consistency before releasing.

What is the best way to detect serialization regressions in libSQL during CI?

Detecting serialization regressions in libSQL during CI involves enforcing a test environment with local SQLite databases to validate export/import workflows and check that persisted data remains consistent through serialization cycles.

Can I validate binary and JSON data round-trips for Turso databases locally?

Yes, you can validate binary and JSON data round-trips locally by applying a scripted verification step against local SQLite databases to ensure metadata and data remain consistent through export and import workflows.

Does this memory persistence verification approach work for both CI pipelines and local validation?

This memory persistence verification approach works for both CI pipelines and local validation scenarios, applying scripted checks to export/import workflows to guard against data round-trip regressions.

Why do I need to test local SQLite databases when validating Turso memory persistence?

Testing local SQLite databases is needed to enforce a controlled test environment where you can safely execute export/import workflows and verify metadata and data consistency before validating Turso/libSQL backends.