database

Explore database schemas before executing CRUD operations and migrations.

1|1|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/husniadil/ekstend --skill database-husniadil
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database
Source: https://github.com/husniadil/ekstend/tree/main/plugins/database/skills/database
Command: npx skills add https://github.com/husniadil/ekstend --skill database-husniadil

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a safe, schema-first approach to interacting with databases via CLI, ensuring you never guess table or column names and always validate the schema before querying.

Core Features & Use Cases

  • Safe multi-database access (MySQL, PostgreSQL, SQLite, Redis) with enforced schema exploration before queries.
  • Credential acquisition options (manual entry or file-based configuration) and guided connection testing.
  • Structured query workflow with safeguards for destructive operations and clear error handling.
  • Real-world use case: a developer verifies tables and schemas before running data migrations or ad-hoc queries in a production-like environment.

Quick Start

Connect to a configured database and start a schema-first query session with safety checks.

Frequently Asked Questions about database

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

FAQPage Schema
How do I safely query a database without guessing table or column names?

Safely query a database by enforcing schema exploration before any data operation. This schema-first approach validates table and column names through mandatory discovery commands before executing CRUD operations.

Does this database CLI skill work with both MySQL and PostgreSQL?

This database CLI skill works with MySQL, PostgreSQL, SQLite, and Redis. It supports structured query workflows across these multiple database systems with guided connection testing and credential handling.

How do I prevent destructive SQL operations when running ad-hoc queries?

Prevent destructive SQL operations by using read and write workflows with safety defaults that require confirmation before executing destructive actions. Clear error handling also stops unsafe commands from running.

Can I use file-based configuration for database credentials during schema exploration?

You can use file-based configuration or manual entry for database credentials during schema exploration. The skill supports both credential acquisition options to establish a safe connection before querying.

What is the best way to verify database schemas before running data migrations?

The best way to verify schemas before running data migrations is to execute mandatory schema discovery commands first. This schema-first workflow ensures the database structure is validated before applying any changes.

Are there limitations when using this schema-first approach for Redis databases?

The schema-first approach applies to Redis alongside MySQL, PostgreSQL, and SQLite, but enforces mandatory schema discovery commands. Users must validate the schema structure before performing any data verification or operations.