CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

70

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

An actionable, well-structured skill with executable Go examples and clean progressive disclosure into four real reference files. The main weaknesses are repetition (schema-creation and hidden-SQL messaging restated) and the absence of explicit validation feedback loops for batch/destructive database operations.

Suggestions

Consolidate the schema-creation prohibition into one place (e.g., keep summary point 14 and remove the separate 'Schema Creation' section, or vice versa) to reduce redundancy.

Add an explicit validation/verification checkpoint with a feedback loop for batch operations and transactions (e.g., verify row counts or re-query within the transaction before Commit).

Merge the 'Avoid Hidden SQL Features' summary point with its dedicated section so the guidance appears once.

DimensionReasoningScore

Conciseness

Mostly efficient with code and tables, but redundant — the schema-creation prohibition is restated three times (summary point 14, the 'Schema Creation' section, and the frontmatter) and 'Avoid Hidden SQL Features' appears as both a summary point and a full section. Not a 3 because of this tightening opportunity; not a 1 because it avoids padding with concepts Claude already knows.

2 / 3

Actionability

Provides fully executable Go examples — parameterized queries, dynamic IN clauses via sqlx.In/Rebind, error handling with errors.Is, defer rows.Close(), connection-pool tuning — plus concrete tables for library choice and error patterns. Copy-paste ready.

3 / 3

Workflow Clarity

Modes ('Write mode', 'Review/debug mode') give a sequence and a numbered best-practices summary exists, but batch/destructive database operations lack explicit validation checkpoints and feedback loops (validate → fix → retry). Per the rubric this caps workflow_clarity at 2; not a 1 because sequencing is present.

2 / 3

Progressive Disclosure

Body is a concise overview with well-signaled one-level-deep references to four real files — transactions.md, testing.md, performance.md, scanning.md — surfaced via inline links, a 'Deep Dives' section, and a 'References' list. Navigation is easy and nesting is shallow.

3 / 3

Total

10

/

12

Passed

Description

100%

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, third-person description that states concrete capabilities, natural trigger terms, explicit use-when guidance, and a clear negative scope. It cleanly satisfies all four dimensions with no fluff or over-claims.

DimensionReasoningScore

Specificity

Lists many concrete actions — 'parameterized queries, struct scanning, NULLable columns, transactions, isolation levels, SELECT FOR UPDATE, connection pool, batch processing, context propagation, and migration tooling' — matching the multi-specific-actions anchor.

3 / 3

Completeness

Explicitly answers both what ('Comprehensive guide for Go database access — ...') and when ('Use when writing, reviewing, or debugging Golang code...'), plus a negative-scope clause; both halves are present and explicit.

3 / 3

Trigger Term Quality

Natural user-facing terms are well covered: 'writing, reviewing, or debugging Golang code that interacts with PostgreSQL, MariaDB, MySQL, or SQLite', 'database testing', and 'database/sql, sqlx, or pgx'.

3 / 3

Distinctiveness Conflict Risk

Niche is clearly scoped to Go database access with named libraries/drivers and an explicit 'Does NOT generate database schemas or migration SQL' boundary, making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
samber/cc-skills-golang
Reviewed

Table of Contents

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.