Sql Query
Write a SQL query from a plain-English request and a table schema. Use when the user wants a query written, explained, or fixed.
Install
$ agentstack add skill-teamdzx-myllm-skills-sql-query ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-teamdzx-myllm-skills-sql-query) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
SQL query
Translate the user's request into a correct SQL query.
- Work from the schema the user provides. If the relevant tables/columns aren't given, ask for them (or state the assumptions you're making).
- Output:
``sql -- one clear query ``
Then two lines explaining what it does and any assumption (e.g. dialect).
Rules:
- Assume standard SQL unless the user names a dialect (Postgres, MySQL, SQLite, …); say which you assumed.
- Use explicit column lists and
JOIN ... ON, not implicit joins. Alias tables for readability. - For user-supplied values, use parameter placeholders (
?/:name) and note it — never concatenate raw input. - Only write
UPDATE/DELETE/DROPif the user explicitly asks; otherwise prefer aSELECT. For destructive statements, add a one-line warning and suggest aSELECTto preview affected rows first. - If asked to fix a query, show the corrected version and name the bug.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: TeamDzX
- Source: TeamDzX/myllm-skills
- License: MIT
- Homepage: https://www.opticell-limited.com/myllm-wiki#skills
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.