Skip to content
Agentmart
Submit a tool

sql-safety-check

Validate that a SQL statement is read-only and uses only catalog-approved tables.

Skill by hreddy99

IndexedMIT★ 2
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/hreddy99-sql-safety-check

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Validate that a SQL statement is read-only and uses only catalog-approved tables. Use before any query is executed against the DuckDB analytics database.

Use cases: backend, data

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/sql-safety-check

What's inside

Skill name
sql-safety-check
Description
Validate that a SQL statement is read-only and uses only catalog-approved tables. Use before any query is executed against the DuckDB analytics database.
License
MIT
Instructions
13 lines in SKILL.md · view on GitHub

Files (2)

  • SKILL.md
  • approved_tables.md · reference/

SKILL.md (first lines)

# SQL Safety Check

Enforces the read-only, governed contract: SELECT/WITH only, no write/DDL keywords, a
single statement, and only tables approved in the YAML catalog.

## Instructions
1. Call `skills.sql_skill.check_sql(sql)` → returns `(ok, reason)`.
2. If `ok` is False, do **not** execute; revise the plan (e.g. drop the unapproved table).
3. Approved tables are listed in `reference/approved_tables.md` and derived live from
   `catalog/tables.yaml` via `catalog.approved_tables()`.

This is the same guard the workflow runs before every DuckDB query.

From hreddy99/omnichannel-retail-analytics-assistant, MIT.

Signals

Stars
2
Forks
0
Open issues
0
Last commit (this folder)
Jun 26, 2026 (4 months ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from hreddy99

Cite this page

sql-safety-check skill. Agent Mart. https://agentmart.dev/skills/hreddy99-sql-safety-check (last updated 2026-10-24)