Database Manager

What This Skill Does

The Database Manager skill transforms your OpenClaw agent into a high-reliability Database Reliability Engineer (DBE). It provides a structured framework for managing relational databases by enforcing strict governance over schema changes, migrations, and incident response. The skill centralizes your database architecture within a dedicated local directory, creating a durable memory of your infrastructure. It ensures that every database modification is treated with the rigor of a product release, requiring explicit preflight packets, rollback paths, and post-deployment verification. By automating the documentation of migrations and backup drills, it removes the guesswork from maintenance and ensures your data systems remain resilient, performant, and well-indexed.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/database-manager After installation, navigate to the ~/database-manager/ directory. Initialize your environment by running the setup.md script, which will configure your operating defaults, establish your storage templates, and link your existing database connections to the agent's memory.

Use Cases

Use this skill when you need to perform complex schema migrations across environments without risking data integrity. It is ideal for teams conducting regular index performance reviews, query hygiene audits, or those establishing disaster recovery protocols. It serves as an essential guardrail when executing risky write operations, ensuring you validate your logic through read-only checks before finalizing changes. Furthermore, use this when you need to standardize your documentation for database ownership, inventory, and historical incident logs.

Example Prompts

1. "Draft a preflight packet for adding a non-nullable column to the users table; include the rollback path and validation queries."
2. "Review the current slow-query log and propose an indexing strategy that balances read latency improvements against write throughput overhead."
3. "We need to conduct a backup drill for the customer_data schema. Outline the steps to verify restoration integrity and document the total recovery time."

Tips & Limitations

To maximize the effectiveness of this skill, strictly adhere to the rule that a backup is only 'real' once a restore drill has been performed and verified. Never skip the preflight documentation, even for minor changes, as this is the primary defense against production incidents. The skill relies on you maintaining the ~/database-manager/ directory structure; avoid modifying these files manually outside of the agent's workflow to ensure the history logs remain accurate. Note that this skill requires read and write access to your local filesystem to maintain its stateful memory and inventory records.