docs: add support for Aurora PostgreSQL and MySQL (#2320)

Co-authored-by: kartik4shastrakar <kartik.shastrakar@actin.co.in>

skills/index.json

@@ -7,7 +7,7 @@
   "skills": [
     {
       "name": "wren-onboarding",
-      "version": "2.1",
+      "version": "2.2",
       "description": "Onboard a user to Wren Engine end-to-end. Walks the user through environment checks, .env configuration, connection profile creation, project scaffolding, binding the profile to the project, and first query. Defers procedural details, per-datasource notes, and the troubleshooting playbook to docs/core/guides/connect.md so the skill stays focused on agent-side rules and routing. Use when the user wants to install Wren Engine, set up a new data source connection, or bootstrap a new project from scratch.",
       "tags": [
         "wren",
@@ -46,7 +46,7 @@
     },
     {
       "name": "wren-generate-mdl",
-      "version": "2.2",
+      "version": "2.3",
       "description": "Generate a Wren MDL project by exploring a database with available tools (SQLAlchemy, database drivers, MCP connectors, or raw SQL). Guides agents through schema discovery, type normalization, and MDL YAML generation using the wren CLI.",
       "tags": [
         "wren",
@@ -65,7 +65,7 @@
     },
     {
       "name": "wren-usage",
-      "version": "2.3",
+      "version": "2.4",
       "description": "Wren Engine CLI workflow guide for AI agents. Triggers on data questions, reports, metrics, revenue, trends, 'how many', 'show me', 'top N', 'compare', 'breakdown'. Answer data questions end-to-end using the wren CLI.",
       "tags": [
         "wren",

skills/versions.json

@@ -1,6 +1,6 @@
 {
   "wren-dlt-connector": "1.0",
-  "wren-generate-mdl": "2.2",
-  "wren-onboarding": "2.1",
-  "wren-usage": "2.3"
+  "wren-generate-mdl": "2.3",
+  "wren-onboarding": "2.2",
+  "wren-usage": "2.4"
 }

skills/wren-generate-mdl/SKILL.md

@@ -4,7 +4,7 @@ description: "Generate a Wren MDL project by exploring a database with available
 license: Apache-2.0
 metadata:
   author: wrenai
-  version: "2.2"
+  version: "2.3"
 ---
 
 # Generate Wren MDL — CLI Agent Workflow
@@ -77,7 +77,7 @@ If no existing project is detected, proceed directly to Phase 1.
 2. Ask the user:
    - Which **schema(s)** or **dataset(s)** to include (skip if only one exists)
    - Whether to include **all tables** or a subset
-   - The **datasource type** for wren (e.g., `postgres`, `bigquery`, `snowflake`) — needed for type normalization dialect
+   - The **datasource type** for wren (e.g., `postgres` (including Aurora), `mysql` (including Aurora), `bigquery`, `snowflake`) — needed for type normalization dialect
 
 ---
 

skills/wren-onboarding/SKILL.md

@@ -4,7 +4,7 @@ description: "Onboard a user to Wren Engine end-to-end. Walks through environmen
 license: Apache-2.0
 metadata:
   author: wrenai
-  version: "2.1"
+  version: "2.2"
 ---
 
 # Wren Onboarding — Agent Workflow
@@ -63,7 +63,7 @@ These two are the only thing Step 2 needs; ask both together so the user has a c
 
 > "Two things before I scaffold:
 > 1. **Project name** — I'll create `~/<name>/` and `cd` into it.
-> 2. **Database type** — run `wren docs connection-info` (no argument) to see the full list, or pick a common one: `postgres`, `mysql`, `bigquery`, `snowflake`, `clickhouse`, `trino`, `duckdb`, …"
+> 2. **Database type** — run `wren docs connection-info` (no argument) to see the full list, or pick a common one: `postgres` (use for Aurora PostgreSQL), `mysql` (use for Aurora MySQL), `bigquery`, `snowflake`, `clickhouse`, `trino`, `duckdb`, …"
 
 Wait for both. Don't ask for credentials.
 

skills/wren-usage/SKILL.md

@@ -4,7 +4,7 @@ description: "Wren Engine CLI workflow guide for AI agents. Answer data question
 license: Apache-2.0
 metadata:
   author: wrenai
-  version: "2.3"
+  version: "2.4"
 ---
 
 # Wren Engine CLI — Agent Workflow Guide
@@ -55,7 +55,7 @@ Run `wren --version`. If the command is not found or errors:
 
    **Ask the user:** If no project is detected or no datasource can be
    inferred, ask the user which database they plan to connect to. Valid
-   extras: `postgres`, `mysql`, `bigquery`, `snowflake`, `clickhouse`,
+   extras: `postgres` (for Aurora Postgres), `mysql` (for Aurora MySQL), `bigquery`, `snowflake`, `clickhouse`,
    `trino`, `mssql`, `databricks`, `redshift`, `spark`, `athena`, `oracle`.
    DuckDB is included by default — no extra needed.
 
@@ -216,7 +216,7 @@ after execution, the query was classified as exploratory.
 1. Check active profile: `wren profile debug`
 2. Verify datasource and connection fields are correct
 3. Test: `wren --sql "SELECT 1"`
-4. Valid datasource values: `postgres`, `mysql`, `bigquery`, `snowflake`, `clickhouse`, `trino`, `mssql`, `databricks`, `redshift`, `spark`, `athena`, `oracle`, `duckdb`
+4. Valid datasource values: `postgres` (for Aurora Postgres), `mysql` (for Aurora MySQL), `bigquery`, `snowflake`, `clickhouse`, `trino`, `mssql`, `databricks`, `redshift`, `spark`, `athena`, `oracle`, `duckdb`
 5. If no profile exists, create one: `wren profile add --ui` (or `--interactive` / `--from-file`)
 
 ### SQL syntax / planning error (enhanced)