golang-database

Comprehensive guide for Go database access — parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling. Use when writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite; for database testing; or for questions about database/sql, sqlx, or pgx. Does NOT generate database schemas or migration SQL.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

77%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A high-quality, actionable skill body with excellent progressive disclosure and copy-ready examples. Its main weakness is workflow structure: best-practice rules without an explicit sequenced workflow or validation feedback loops for the destructive/batch operations it governs.

Suggestions

Add an explicit step-by-step workflow for write/review modes with validation checkpoints (e.g. after generating a query: lint with golangci-lint, run sqlmock/integration tests, verify rows.Close and *Context variants) to lift workflow_clarity above the destructive/batch cap of 3.

Remove duplicated or restated content — e.g. the repeated 'schema creation' rationale and the near-duplicate performance-rules paragraph at the end of performance.md — to tighten conciseness.

Trim conceptual padding Claude already knows, such as the full 'Why NOT ORMs' bullet list, to a one-line pointer or a single sentence.

Dimension	Reasoning	Score
Conciseness	Largely lean and code-driven assuming Claude's competence; a few passages lightly restate knowledge Claude already has (the 'Why NOT ORMs' bullets, restated schema-creation rationale, and a duplicated performance-rules paragraph), but overall each token earns its place.	4 / 5
Actionability	Provides copy-paste-ready, executable Go for the common cases (parameterized queries, sqlx.In, allowlist columns, error handling, rows.Close, context variants, pool config) plus concrete tables for library choice and error patterns.	5 / 5
Workflow Clarity	Despite the persona's named modes, the body presents best-practice rules rather than a sequenced workflow; for its destructive/batch database operations it lacks explicit validate→fix→retry checkpoints, which caps this dimension at 3 per the rubric's feedback-loop guidance.	3 / 5
Progressive Disclosure	SKILL.md is a concise overview with clearly signaled, one-level-deep references to real bundle files (transactions.md, testing.md, performance.md, scanning.md) plus a Deep Dives section; all referenced paths exist and navigation is easy.	5 / 5
	Total	17 / 20 Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that clearly states capabilities, usage triggers, and explicit boundaries. It is concise yet comprehensive and third-person throughout. Minor keyword variations are the only gap.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers 'what' (the enumerated capabilities) and 'when' ('Use when writing, reviewing, or debugging Golang code that interacts with... for database testing; or for questions about...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes strong natural triggers ('writing, reviewing, or debugging Golang code', 'database testing', 'questions about database/sql, sqlx, or pgx', plus driver names PostgreSQL/MariaDB/MySQL/SQLite), but a few common phrasings users might say (e.g. 'Go SQL', 'Go DB layer') are absent.	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche — Go database access via database/sql/sqlx/pgx with an explicit negative boundary ('Does NOT generate database schemas or migration SQL') — minimizing overlap with sibling Go skills like golang-security or golang-context.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-database/SKILL.md
Commit: 30cdf15

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.