Sql query
Curated open Agent-Skill format skills for MyLLM (the on-device iOS AI agent). Install with /skill add teamdzx/myllm-skills.
npx -y skills add TeamDzX/myllm-skills --skill sql-queryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Write a SQL query from a plain-English request and a table schema. Use when the user wants a query written, explained, or fixed.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
1.1 KB, as published. Nobody here has run it
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:
-- one clear queryThen 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.