Golang Database
PassAudited by ClawScan on May 1, 2026.
Overview
This is an instruction-only Go database best-practices skill whose code-editing, command, sub-agent, and optional database-metadata behaviors are disclosed and aligned with its purpose.
Before installing, confirm you are comfortable with the agent editing Go database code, running local Go/git commands, using sub-agents to inspect repository code, and querying any configured SQL MCP database only in authorized contexts.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may edit project files and run local development commands while helping with database code.
The skill can read and modify repository files and run Go, linter, and git commands. This is expected for a Go database coding assistant, but it is still meaningful local mutation and command authority.
allowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent AskUserQuestion
Use it in coding workspaces where those actions are acceptable, and review tool approvals or diffs before accepting changes, especially for git commands or commands that execute project code.
A sub-agent may inspect parts of the repository in parallel to support code generation or review.
The skill explicitly delegates codebase inspection to another agent. This is disclosed and task-aligned, but it means repository context may be shared within a sub-agent workflow.
launch a background agent to grep for existing query patterns and naming conventions... use a sub-agent to scan for missing `rows.Close()`, un-parameterized queries, missing context propagation, and absent error checks
Install only if sub-agent code inspection is acceptable for the repository, and ask for a summary of what was inspected when working with sensitive code.
If a SQL MCP connection is available, the agent may run read-oriented metadata queries against the connected database.
The skill may use an already-configured SQL MCP/database connection to query database metadata. This is purpose-aligned for performance review and the text says to suggest changes rather than execute DDL, but it still uses delegated database access.
When a SQL MCP tool is available, query the database to check existing indexes before suggesting new ones
Ensure any SQL MCP connection points to an authorized, preferably read-only or non-production database, and require explicit approval before live database queries.