driver-implementer

Automates adding DataEngine drivers to QoreDB via scaffold, module, and registration.

137|8|Updated Jan 12, 2026
One-click install
npx skills add https://github.com/QoreDB/QoreDB --skill driver-implementer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: driver-implementer
Source: https://github.com/QoreDB/QoreDB/tree/main/.agent/skills/driver-implementer
Command: npx skills add https://github.com/QoreDB/QoreDB --skill driver-implementer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the process of adding new DataEngine drivers to QoreDB, reducing integration time and human error when expanding supported databases.

Core Features & Use Cases

  • Provides a standardized scaffold for new drivers in Rust, including file naming and module registration.
  • Guides dependency management and driver registration to ensure consistent behavior across drivers.
  • Enables adding support for databases like Redis, SQLite, Cassandra with a repeatable, safe workflow.

Quick Start

Follow the Driver Implementer workflow to scaffold a new driver, declare its module, and register it in AppState.

Frequently Asked Questions about driver-implementer

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

FAQPage Schema
How do I add a new database driver to QoreDB?

Add a new database driver to QoreDB by using an automated workflow that handles Rust scaffolding, module declaration, and driver registration to ensure compile-time coherence and safe dependency management.

What is the process for scaffolding a DataEngine driver in Rust?

Scaffolding a DataEngine driver in Rust involves standardized file placement, module exposure, and AppState registration, establishing a repeatable workflow that enforces consistent behavior across different database integrations.

Can I use this workflow to integrate Redis, SQLite, and Cassandra into QoreDB?

Yes, you can integrate Redis, SQLite, and Cassandra into QoreDB because the driver implementation workflow provides a standardized scaffold for adding new DataEngine drivers for these and similar databases.

Why does my new driver registration fail to maintain compile-time coherence?

Driver registration lacks compile-time coherence when file placement and module exposure deviate from the standardized scaffold, which is why enforcing a safe dependency management workflow is necessary.

Do I need to manually configure AppState when adding a database driver?

Manual AppState configuration is not required because the driver implementation workflow automates driver registration, guiding module exposure and ensuring safe dependency management during the integration process.