Does this skill work with production databases?

This skill is specifically designed for development environments using Docker Compose and local credentials stored in CLAUDE.local.md.

How does the skill handle database credentials?

It automatically reads the required user, password, and database name from your CLAUDE.local.md file under the 'Database Access' section.

Is there a risk of accidentally deleting data?

The skill includes instructions to always confirm with the user before executing any UPDATE or DELETE queries to ensure data safety.

Can I query WordPress multisite installations?

Yes, the skill is pre-configured to recognize and handle various prefixes including wp_multisite_, wp_nightly_, and version-specific prefixes like wp_6_6_.

WordPress Database SQL Manager

Name: WordPress Database SQL Manager
Author: Activer007

byActiver007

Database Management

Executes SQL queries against WordPress development databases via Docker containers to inspect data and debug issues.

About

The WordPress Database SQL Manager skill enables Claude to interact directly with MariaDB databases within a Docker-based WordPress development environment. It automates the process of fetching credentials from local configuration files and provides a standardized pattern for querying multiple WordPress installations, including multisite and version-specific builds. This skill is particularly useful for developers needing to inspect Simple History logs, verify data persistence, or perform structural analysis across various database prefixes without leaving the Claude interface.

Key Features

Automated credential retrieval from local configuration files
Deep integration with Simple History event logs for debugging
Seamless integration with Docker Compose MariaDB services
Safety protocols for data-modifying queries like UPDATE and DELETE
Support for multiple WordPress table prefixes and installations
0 GitHub stars

Use Cases

Verifying schema changes and record counts during plugin development
Debugging database-level issues across multiple WordPress versions
Inspecting audit logs and metadata in Simple History tables

About

Key Features

Automated credential retrieval from local configuration files
Deep integration with Simple History event logs for debugging
Seamless integration with Docker Compose MariaDB services
Safety protocols for data-modifying queries like UPDATE and DELETE
Support for multiple WordPress table prefixes and installations
0 GitHub stars

Use Cases

Verifying schema changes and record counts during plugin development
Debugging database-level issues across multiple WordPress versions
Inspecting audit logs and metadata in Simple History tables