Back to Skills

bazinga-db

DEPRECATED - Use domain-specific skills instead. Routes to bazinga-db-core, bazinga-db-workflow, bazinga-db-agents, or bazinga-db-context.

20starsUpdated 3/25/2026

Security Assessment

Safe(100/100)
Security Score100/100

About bazinga-db

The bazinga-db skill is a deprecated router for database-related operations that has been replaced by more specialized, domain-specific skills. Originally, it provided a monolithic interface for handling sessions, state management, task planning, agent logging, and context tracking. Its primary purpose was to centralize database operations and facilitate the management of session data, task workflows, reasoning logs, context packages, and error patterns, providing developers with a unified toolset. The deprecation reflects a shift toward modular, domain-focused skills to improve maintainability and scalability, and to address file size limitations of the original monolithic skill.

The skill routes commands to four domain-specific skills: `bazinga-db-core` for session and state operations, `bazinga-db-workflow` for task and development plan management, `bazinga-db-agents` for logging, reasoning, and event tracking, and `bazinga-db-context` for managing context packages, error patterns, and strategies. It includes a comprehensive command routing table, quick reference for invoking domain skills, and technical notes such as event idempotency handling via unique database indexes. Although the CLI remains available, users are strongly advised to interact with the individual domain skills rather than the deprecated router.

Typical use cases include session management for interactive applications, task and development plan tracking, agent interaction logging, and maintaining context packages for AI workflows. Target users are developers and technical teams building AI applications or complex workflows requiring structured database interactions. By directing users to the appropriate domain-specific skill, bazinga-db ensures more efficient operations, better modularity, and reduces the risk of errors caused by monolithic database handling.

FAQ

Can I still use the bazinga-db CLI directly?

While the CLI remains available, it is not recommended. You should use the domain-specific skills (`bazinga-db-core`, `bazinga-db-workflow`, `bazinga-db-agents`, `bazinga-db-context`) to perform operations.

Which domain skill should I use for session management?

For sessions, state snapshots, and dashboard operations, use `bazinga-db-core`.

Are there any special requirements for event logging?

Yes, events support idempotency keys through the `idx_logs_idempotency` unique index. Ensure `idempotency_key` is provided when necessary to avoid duplicate entries.

Has the original bazinga-db been split into multiple skills?

Yes, the original monolithic bazinga-db skill has been divided into four domain-focused skills for maintainability and to stay within file size limits.

Where can I find schema and example commands?

Reference documentation for schema and command examples remains in the `references` directory within the skill folder, specifically `schema.md` and `command_examples.md`.

All Files

3 files
INTEGRATION_GUIDE.md7.3 KB
View
SKILL.md4.9 KB
View
MIGRATION_agent_type_constraint.md7.4 KB
View

Install bazinga-db

Download and extract the skill files to your .claude/skills/ directory.

Quick Setup:

  1. Copy the skill folder to .claude/skills/
  2. Claude will automatically detect and use the skill

Repository

mehdic/bazinga