Route data engineering tasks correctly
databases-data-orchestratorskillsetup L1★0
Sheshiyer/skill-clusters ↗What it does
Route data tasks to specialized database/ETL skills
Best for
When a user asks a data question but hasn't specified which database engine or skill they need.
Inputs
- · user intent (design/query/optimize/migrate/move)
- · store name if provided
Outputs
- · routed to correct skill (postgres-patterns, mysql-patterns, prisma-patterns, redis-patterns, clickhouse-io, database-migrations, data-throughput-accelerator)
Preconditions
- · databases-data-core consulted for store selection
Failure modes
- · routed to wrong spoke (e.g., analytics question to OLTP spoke)
Trust signals
- · routing map covers OLTP/OLAP/cache/ORM/migrations/ETL
- · links to core decision model