Skylv Sql Helper
v1.0.0SQL query builder and optimizer. Generates queries, explains execution plans, and optimizes slow queries. Triggers: sql query, database query, sql optimization.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description (SQL query builder/optimizer) match the SKILL.md content: example queries, optimization rules, and anti-patterns. The skill does not claim or require database access, cloud credentials, or unrelated capabilities.
Instruction Scope
SKILL.md stays within the stated purpose (writing and optimizing SQL). It is purely advisory — it provides patterns, examples, and rules but does not include instructions to connect to databases, read files, or send data externally. Note: because it doesn't provide connection/execution steps, it will not run EXPLAIN or modify databases on its own; if you expect automated execution, a different skill that requests DB credentials would be required.
Install Mechanism
No install spec and no code files — lowest-risk instruction-only skill. Nothing is downloaded or written to disk.
Credentials
The skill declares no environment variables, credentials, or config paths, which is proportional to an advisory SQL helper that only provides examples and guidance.
Persistence & Privilege
Defaults are used (not always:true, not requesting permanent presence). The skill does not attempt to modify other skills or system-wide settings.
Assessment
This skill is advisory only and will not connect to or run queries against your databases. If you need automated execution or EXPLAIN plans run against live systems, expect a different skill to request database credentials or network access — treat that credential request as sensitive. Proceed if you only want query-writing and optimization advice; if a future version asks for secrets or installs code, review those requests carefully before granting access.Like a lobster shell, security has layers — review code before you run it.
latest
SQL Helper
Overview
Helps write, optimize, and debug SQL queries.
When to Use
- User asks to "write a SQL query" or "optimize this query"
- Debugging slow database operations
Pagination
SELECT * FROM users ORDER BY id LIMIT 20 OFFSET 40;
Join with Aggregation
SELECT u.name, COUNT(o.id) as order_count FROM users u LEFT JOIN orders o ON u.id = o.user_id GROUP BY u.id;
Optimization Rules
- Add indexes on WHERE/JOIN columns
- Avoid SELECT * - specify columns
- Use EXPLAIN to analyze execution plan
- Optimize JOIN order (small table first)
- Add LIMIT for pagination
Anti-Patterns to Avoid
- SELECT * in production code
- Nested subqueries (use JOINs or CTEs)
- OR in WHERE clause (use IN or UNION)
Comments
Loading comments...
