golang-testing

Go testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices. Use when writing Go tests — table-driven cases, subtests, benchmarks, fuzzing, or coverage.

Quality

85%

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

78%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, executable reference with a clear TDD workflow, but it is a large monolithic document that does not use progressive disclosure to split detailed sections into reference files.

Suggestions

Split peripheral catalogs (HTTP handler testing, CI/CD integration, interface mocking) into reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Trim or consolidate the redundant Testing Commands and Test Coverage command blocks, which overlap significantly.

Add explicit validation checkpoints (e.g., verify benchmarks are stable, confirm fuzz failures are reproducible) to the benchmark and fuzz workflows.

Dimension	Reasoning	Score
Conciseness	Sections are lean and code-forward with minimal prose, but the file runs long (~715 lines) with several catalogs (HTTP testing, CI/CD, mocking) that could be trimmed; no padding of concepts Claude already knows.	4 / 5
Actionability	Fully executable, copy-paste-ready Go code throughout, with concrete shell commands (go test -bench, -coverprofile) and examples covering the common cases.	5 / 5
Workflow Clarity	The TDD RED-GREEN-REFACTOR cycle is sequenced with explicit verify-FAIL/verify-PASS checkpoints, but the benchmark/fuzz/coverage sections are parallel catalogs without their own validation checkpoints.	4 / 5
Progressive Disclosure	A single monolithic file with well-organized headers but no bundle files or external references; content that could live in separate files (HTTP testing, CI/CD, mocking) is inlined, and the under-50-line simple-skill exception does not apply.	3 / 5
	Total	16 / 20 Passed

Description

92%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 clearly states capabilities and provides explicit trigger guidance. Only minor gap is the lack of file-extension synonyms in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names five concrete capabilities — "table-driven tests, subtests, benchmarks, fuzzing, and test coverage" — giving comprehensive coverage of the domain rather than generic phrasing.	5 / 5
Completeness	Explicitly answers both what ("Go testing patterns including...") and when ("Use when writing Go tests — ...") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural user-facing terms ("table-driven cases, subtests, benchmarks, fuzzing, or coverage") but omits common synonyms like .go files or test files, so it is not fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	The "Go testing" niche with specific triggers (fuzzing, benchmarks, table-driven) is clearly distinct from other skills with minimal overlap risk.	5 / 5
	Total	19 / 20 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (722 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	13 / 16 Passed

Repository: affaan-m/ECC
Path: 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.