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

78%

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

72%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.

Highly actionable with executable examples throughout, but the skill is a flat catalog of patterns rather than a guided workflow, lacks validation feedback loops, and keeps all content inline with no progressive disclosure into reference files.

Suggestions

Add a short sequenced workflow with validation checkpoints (e.g., write test -> run `go test -race ./...` -> check coverage -> fix -> re-run) instead of presenting patterns as a flat catalog.

Replace the fragile coverage-threshold grep hack with a concrete, validated command such as a small script or `go test -cover` paired with an explicit threshold check and a fix-and-retry loop.

Move detailed reference material (mocking patterns, testcontainers integration, full coverage/benchmark commands) into separate referenced files and link to them from the overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Largely lean and example-driven with executable snippets, though the recurring 'Benefits'/'Why' bullet blocks restate concepts Claude already knows and could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready Go code and shell commands across table-driven tests, helpers, fixtures, race detection, coverage, benchmarking, mocking, and integration testing, covering the common cases.	5 / 5
Workflow Clarity	The skill presents parallel patterns rather than a sequenced workflow, and there are no validation checkpoints; the coverage-threshold approach ('grep ... && exit 1') is fragile and lacks a validate-fix-retry loop.	3 / 5
Progressive Disclosure	A single self-contained SKILL.md with no bundle files or external references; sections are well-labeled, but substantial reference-style material (mocking, integration/testcontainers, coverage commands) could be split into referenced files.	3 / 5
	Total	15 / 20 Passed

Description

83%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, specific description that names concrete capabilities and includes a clear use-trigger. The main gap is a slightly narrow 'Use when' clause relative to the full feature list and a few missing natural synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Clearly states what the skill covers and includes an explicit 'Use when writing or improving Go tests' trigger; the 'when' is present but narrower than the breadth of capabilities listed.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('Go tests', 'writing or improving Go tests', 'race detection', 'benchmarking') but lacks some common synonyms or file-extension cues (e.g. 'go test', '_test.go').	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to Go testing with distinct triggers ('Go tests', 'race detection', 'coverage analysis'), making collision with non-Go or non-testing skills minimal.	5 / 5
	Total	18 / 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: d8409a4

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.