routine-storage-audit

Name: routine-storage-audit
Availability: InStock
Author: Motion

Audit Runneth sandbox routines and produce a dated migration plan file.

3|Updated Apr 11, 2026

Search Tags:#SQLite #database integrity #migration planning #storage audit #read-only inspection #routine classification #buildeth app

Ready to run

npx skills add https://github.com/Motion-Creative/runneth-apps --skill routine-storage-audit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: routine-storage-audit
Source: https://github.com/Motion-Creative/runneth-apps/tree/main/routine-storage-audit
Command: npx skills add https://github.com/Motion-Creative/runneth-apps --skill routine-storage-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It prevents messy, incorrect, or wasted storage by auditing where your Runneth routines actually write versus where they should write based on storage rules.

Core Features & Use Cases

Detect misplaced routine storage: flags routines that feed an app but write to files, and routines that write to the wrong DB/files.
Find shared-writable-DB violations: identifies when two apps point at the same writable primary database (while allowing read-only _core ATTACH reference sharing).
Produce a safe migration plan artifact: generates a dated plan file under /agent/brain/migrations/ that the user can review and then hand off to routine-planner for re-authoring.

Quick Start

Ask your Runneth to "audit my routines and check the brain storage layout" to generate the migration plan file for review.

Frequently Asked Questions about routine-storage-audit

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

FAQPage Schema

How do I audit routine storage drift in a SQLite database?▼

A storage audit detects misplaced routines by checking where data is written against storage rules. It flags routines that feed an app but write to files, write to the wrong database, or share a writable primary database across multiple apps.

How do I check if two apps share the same writable SQLite database?▼

A storage audit identifies shared-writable-DB violations by detecting when two apps point at the same writable primary database. It permits read-only `_core` ATTACH reference sharing while flagging actual write conflicts for re-authoring.

What is a read-only storage audit and how does it generate a migration plan?▼

A read-only storage audit uses file reads and SELECT queries to inventory routines without modifying data. It produces a dated migration plan artifact at `/agent/brain/migrations/storage-audit-<YYYY-MM-DD>.md` for review and downstream re-authoring.

Does the storage audit modify my routine data or database files?▼

The storage audit performs plan-only read operations exclusively, using reminder lists, file reads, and SELECT queries. It modifies nothing in your sandbox, writing only a single dated migration plan file under `/agent/brain/migrations/`.

What do I need to run a routine storage layout check on my sandbox?▼

You need an existing Runneth sandbox containing Buildeth apps and routines. The storage audit performs a read-only inspection of your deployed environment to classify data writes and detect storage layout violations.