How do I install the Dbconnect skill?

Run npx skillmds@latest add fuseraft/dbconnect in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Dbconnect safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Dbconnect?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Dbconnect free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Dbconnect?

fuseraft (@fuseraft) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Dbconnect by fuseraft — Agent Skill

Name: Dbconnect
Author: fuseraft

File contents

dbconnect

When to use

Need to test SQL Server or Oracle connectivity.
Need to list named connections from a .connections file.
Need to inspect schema or run ad hoc SQL.
Need to execute SQL files such as migrations.
Need query output written to CSV.

Inputs to gather

Target DB type: mssql or oracle
Either --conn string or named connection for --use
SQL text or path to .sql file
Optional CSV output path
Whether the SQL writes data (INSERT/UPDATE/DELETE/MERGE/DDL/EXEC) — if so, confirm intent with the user before adding --allow-write

Procedure

Read references/dbconnect-usage.md and references/dbconnect-examples.md.
Confirm dbconnect\bin\dbconnect.exe exists.
If the user wants saved connections, run scripts\dbconnect-list.bat.
For a connectivity check, run a trivial query like SELECT 1 using the right wrapper.
For schema inspection, use the schema query pattern in references/dbconnect-examples.md.
For migrations or other file-based SQL, execute the .sql file path through the wrapper. SQL Server files may contain GO batch separators; dbconnect splits and runs them as separate batches automatically.
If results must be preserved, pass an output CSV path — this also bypasses the console --max-rows cap. For large ad hoc queries without --output, either add --max-rows <n> or expect console output truncated at 200 rows by default.
Return the exact command run, summarize results, and call out any prerequisite failures.

Rules

Prefer wrapper scripts in scripts/; do not invoke the exe manually unless troubleshooting.
Do not invent connection strings, named connections, or schema names.
dbconnect blocks INSERT/UPDATE/DELETE/MERGE/DROP/ALTER/CREATE/TRUNCATE/GRANT/REVOKE/EXEC/EXECUTE statements by default (exit code 7). Confirm explicit user intent before re-running with --allow-write — this is a text-based guard, not a parser, so do not treat its absence of a block as proof the SQL is safe.
If authentication or network access fails, report the exact stderr and stop.
Keep secrets out of logs and responses when echoing commands.

References

references/dbconnect-usage.md
references/dbconnect-examples.md
scripts/dbconnect-run.ps1
scripts/dbconnect-run.bat
scripts/dbconnect-list.bat

---name: dbconnectdescription: Use dbconnect.exe to validate connectivity, inspect schema, run SQL files including migration scripts, and export results. Keep invocation specifics in references/ and execute through scripts/ wrappers.---# dbconnect## When to use- Need to test SQL Server or Oracle connectivity.- Need to list named connections from a `.connections` file.- Need to inspect schema or run ad hoc SQL.- Need to execute SQL files such as migrations.- Need query output written to CSV.## Inputs to gather- Target DB type: `mssql` or `oracle`- Either `--conn` string or named connection for `--use`- SQL text or path to `.sql` file- Optional CSV output path- Whether the SQL writes data (INSERT/UPDATE/DELETE/MERGE/DDL/EXEC) — if so, confirm intent with the user before adding `--allow-write`## Procedure1. Read `references/dbconnect-usage.md` and `references/dbconnect-examples.md`.2. Confirm `dbconnect\bin\dbconnect.exe` exists.3. If the user wants saved connections, run `scripts\dbconnect-list.bat`.4. For a connectivity check, run a trivial query like `SELECT 1` using the right wrapper.5. For schema inspection, use the schema query pattern in `references/dbconnect-examples.md`.6. For migrations or other file-based SQL, execute the `.sql` file path through the wrapper. SQL Server files may contain `GO` batch separators; dbconnect splits and runs them as separate batches automatically.7. If results must be preserved, pass an output CSV path — this also bypasses the console `--max-rows` cap. For large ad hoc queries without `--output`, either add `--max-rows <n>` or expect console output truncated at 200 rows by default.8. Return the exact command run, summarize results, and call out any prerequisite failures.## Rules- Prefer wrapper scripts in `scripts/`; do not invoke the exe manually unless troubleshooting.- Do not invent connection strings, named connections, or schema names.- dbconnect blocks INSERT/UPDATE/DELETE/MERGE/DROP/ALTER/CREATE/TRUNCATE/GRANT/REVOKE/EXEC/EXECUTE statements by default (exit code 7). Confirm explicit user intent before re-running with `--allow-write` — this is a text-based guard, not a parser, so do not treat its absence of a block as proof the SQL is safe.- If authentication or network access fails, report the exact stderr and stop.- Keep secrets out of logs and responses when echoing commands.## References- `references/dbconnect-usage.md`- `references/dbconnect-examples.md`- `scripts/dbconnect-run.ps1`- `scripts/dbconnect-run.bat`- `scripts/dbconnect-list.bat`

Frequently asked questions

Dbconnect