Database Operations

v1.0.0

Use when designing database schemas, writing migrations, optimizing SQL queries, fixing N+1 problems, creating indexes, setting up PostgreSQL, configuring EF Core, implementing caching, partitioning tables, or any database performance question.

7· 9.7k·96 current·99 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the SKILL.md content: SQL patterns, EXPLAIN usage, indexing, migrations, EF Core guidance and caching. There are no unrelated environment variables, binaries, or installs requested.
Instruction Scope
SKILL.md is an instruction-only expert prompt containing SQL examples, migration and trigger patterns, and operational advice. It does not ask the agent to read local files, call external endpoints, or access credentials. Caution: some examples use dynamic SQL (EXECUTE format with a table identifier) and create triggers/audit tables — these are reasonable for the stated purpose but should be reviewed before running in production because dynamic identifiers and triggers can introduce SQL-injection risks or operational side effects if misused.
Install Mechanism
No install specification or code files are present; this is instruction-only so nothing will be written to disk or downloaded by default.
Credentials
The skill declares no environment variables, credentials, or config paths. That is proportional for a guidance/SQL-snippet skill.
Persistence & Privilege
always:false and user-invocable:true (defaults). The skill does not request permanent or privileged platform presence and does not modify other skills or global agent settings.
Assessment
This skill is internally coherent and appears to be a pure guidance / code-snippet resource for database work. It does not request credentials or install software. Before you act on its suggestions: (1) never run SQL in production without reviewing and testing it in a staging environment; (2) review dynamic SQL (EXECUTE/format) usages to ensure identifiers are validated to avoid injection; (3) be aware that triggers and audit logging can add write overhead and quickly grow storage — plan retention/archival; (4) follow least-privilege practices for any functions/triggers (avoid running as superuser/definer unless necessary); (5) ensure backups and rollback/migration plans are in place before applying schema changes. If you want additional assurance, share specific snippets you plan to run and the target DB environment so they can be reviewed for safety and correctness.

Like a lobster shell, security has layers — review code before you run it.

latestvk974yyhym9ghf82sf01wb6f2kn80dc0n

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Comments