Why Use This
This skill provides specialized capabilities for bonny's codebase.
Use Cases
- Developing new features in the bonny repository
- Refactoring existing code to follow bonny standards
- Understanding and working with bonny's codebase structure
Install Guide
2 steps - 1
- 2
Install inside Ananke
Click Install Skill, paste the link below, then press Install.
https://github.com/bonny/WordPress-Simple-History/tree/main/.claude/skills/sql
Skill Snapshot
Auto scan of skill assets. Informational only.
Valid SKILL.md
Checks against SKILL.md specification
Source & Community
Updated At Jan 16, 2026, 07:48 PM
Skill Stats
SKILL.md 54 Lines
Total Files 1
Total Size 0 B
License NOASSERTION
---
name: sql
description: Runs SQL queries against the WordPress development database. Use when inspecting tables, checking event data, or debugging database issues.
disable-model-invocation: true
allowed-tools: Read, Bash
---
# Run SQL Queries
Run SQL queries against the WordPress development database.
**Security:** Development database only. Always confirm UPDATE/DELETE with user first.
## Command Pattern
```bash
docker compose exec mariadb mysql -u<USER> -p<PASSWORD> <DATABASE> -e "YOUR_SQL_HERE"
```
Credentials are in `CLAUDE.local.md` under "Database Access".
## Common Queries
```bash
# Show all tables
docker compose exec mariadb mysql -u<USER> -p<PASSWORD> <DATABASE> -e "SHOW TABLES;"
# Recent Simple History events
docker compose exec mariadb mysql -u<USER> -p<PASSWORD> <DATABASE> -e "SELECT * FROM wp_simple_history ORDER BY id DESC LIMIT 10;"
# Describe table structure
docker compose exec mariadb mysql -u<USER> -p<PASSWORD> <DATABASE> -e "DESCRIBE wp_simple_history;"
```
## Table Prefixes
| Prefix | Installation |
| --------------- | ------------- |
| `wp_` | Main install |
| `wp_nightly_` | Nightly build |
| `wp_multisite_` | Multisite |
## Simple History Tables
- `wp_simple_history` - Main events table
- `wp_simple_history_contexts` - Event context/metadata
## Workflow
1. Read credentials from `CLAUDE.local.md`
2. Ask user for query (if not specified)
3. Run query and display results
4. **For UPDATE/DELETE:** Always confirm with user first