Squix Skill for AI Coding Agents

Run SQL queries non-interactively by using the -f flag with SELECT statements to stream results directly to stdout in machine-friendly formats like json, csv, or tsv. This avoids interactive TUI pitfalls and ensures predictable output for automation.

SQL query execution fails in automation when using interactive commands like squix shell or omitting the -f flag for SELECT queries. Always check squix status, switch to the target connection, and use -f to force non-interactive output formatting.

Execute parameterized queries for repeatable automation by using :name syntax with optional defaults like :name|default. This allows AI agents to pass variables dynamically to saved queries, ensuring consistent execution across configured database connections.

Yes, you can use saved query libraries with specific database connections for CLI automation. First switch to the correct connection using squix switch, then run named or ID queries with squix run, applying the -f flag for SELECT exports to format stdout output.

Before executing non-interactive SQL, the required connection safety workflow is checking connectivity with squix status and switching to the correct database connection using squix switch. This ensures queries target the intended database and run reliably without interactive prompts.

The limitations of using interactive SQL commands in automated pipelines include execution failures and unpredictable output. Commands like squix shell or squix run without the -f flag for SELECT queries break automation, requiring strict adherence to non-interactive output formatting rules.