golang-testing

Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./.kiro/skills/golang-testing/SKILL.md

Quality

Content

63%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 highly actionable Go testing reference with nearly executable examples throughout, weakened by monolithic inline structure and recurring explanatory padding that teaches concepts Claude already knows. Splitting advanced sections into reference files and trimming Benefits/Why blocks would lift both conciseness and progressive disclosure.

Suggestions

Split advanced sections (Mocking, Integration Tests, Benchmarking, Common Patterns) into reference files under references/ with clearly signaled one-level-deep links, keeping SKILL.md as a concise overview with the core table-driven test pattern and test helpers.

Remove or trim the 'Benefits:' and 'Why:' bullet blocks that restate knowledge Claude already has (e.g., what the race detector does, what t.Helper is for) — the code examples are self-justifying.

Complete the fragmentary examples: replace 'testcontainers.GenericContainer(ctx, ...)' and '// ... test logic' placeholders with runnable code, and add a short decision guide for when to apply each pattern (e.g., unit vs integration vs benchmark).

Dimension	Reasoning	Score
Conciseness	The body is dominated by dense, useful code, but "Benefits:" and "Why:" blocks explain concepts Claude already knows (e.g., race detection "Detects concurrent access bugs / Prevents production race conditions", t.Helper "Correct line numbers in test failures"), matching anchor 3 ("mostly efficient but includes some unnecessary explanation or could be tightened"). Not 4 because these explanatory blocks recur across multiple sections.	3 / 5
Actionability	Nearly all guidance is copy-paste-ready Go code and shell commands (table-driven test, t.Cleanup, benchstat comparison, build tags). Not 5 because a few examples are literal fragments: "testcontainers.GenericContainer(ctx, ...)" with ellipsis and repeated "// ... test logic" placeholders.	4 / 5
Workflow Clarity	Sequences are clear where they matter (benchstat old/new comparison flow, CI race-detector step, integration build-tag flow) and no destructive or batch operation demands validation checkpoints. Not 5 because there is no top-level guidance sequencing which pattern to apply when, and per-pattern checkpoints are implicit.	4 / 5
Progressive Disclosure	Sections are well-organized with headers, but the skill is a ~320-line monolith with zero reference files — mocking, integration testing, and benchmarking sections are natural candidates for separate files. No bundle files exist, so all content is inlined; anchor 3 ("content that should be separate is inline") fits better than anchor 4, which expects appropriately split content.	3 / 5
	Total	14 / 20 Passed

Description

78%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 description that clearly states what the skill covers and when to use it, with specific Go-testing capabilities and natural trigger terms. Minor improvements possible by converting topic nouns into concrete actions and enriching the when clause with more trigger scenarios.

Dimension	Reasoning	Score
Specificity	"table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns" lists several specific capabilities covering the Go testing domain. Not 5 because these are topic nouns rather than concrete action verbs like the anchor-5 example ("Extract text and tables from PDF files, fill forms").	4 / 5
Completeness	Both what ("Go testing best practices including table-driven tests... coverage analysis") and when ("Use when writing or improving Go tests") are explicitly stated. Not 5 because the when clause is a single general phrase without the multiple concrete trigger scenarios of the anchor-5 example; clearly above 3 since the when is explicit, not merely implied.	4 / 5
Trigger Term Quality	Natural phrases a user would say appear ("Go tests", "test coverage", "benchmarks", "race detection", "integration testing") alongside an explicit "Use when writing or improving Go tests" trigger. Not 5 because common variations like "go test", "_test.go", or "flaky tests" are missing.	4 / 5
Distinctiveness Conflict Risk	"Go testing" carves out a clear niche with distinct, Go-specific triggers (table-driven tests, race detection, coverage) unlikely to fire for other skills. Written in third person with minimal conflict risk against general testing or non-Go skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Path: .kiro/skills/golang-testing/SKILL.md
Commit: c70874f

Reviewed: 1 day 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.