golang-testing
tessl i github:ysyecust/everything-claude-code --skill golang-testingGo testing patterns including table-driven tests, subtests, benchmarks, fuzzing, and test coverage. Follows TDD methodology with idiomatic Go practices.
Validation
69%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (711 lines); consider splitting into references/ and linking | Warning |
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
Implementation
77%This is a high-quality, comprehensive Go testing skill with excellent actionability and clear workflows. The code examples are executable and well-structured. The main weakness is length - the skill tries to cover everything in one file, and some introductory explanations (TDD basics, what table-driven tests are) could be trimmed since Claude already knows these concepts.
Suggestions
Consider splitting advanced topics (fuzzing, benchmarks, HTTP handler testing) into separate reference files linked from a shorter main SKILL.md
Remove or significantly condense the TDD workflow explanation - Claude understands RED-GREEN-REFACTOR; just show the Go-specific implementation pattern
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some sections that could be tightened. The TDD workflow explanation and some introductory text add tokens without providing unique value Claude wouldn't already know. However, most code examples are lean and purposeful. | 2 / 3 |
Actionability | Excellent actionability with fully executable, copy-paste ready code examples throughout. Every pattern includes complete, working Go code with proper imports, test commands, and expected outputs. The bash commands are specific and immediately usable. | 3 / 3 |
Workflow Clarity | Clear TDD workflow with explicit RED-GREEN-REFACTOR cycle, step-by-step numbered processes, and validation checkpoints (run test - verify failure, run test - verify pass). The CI/CD section includes coverage threshold validation as a checkpoint. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers and logical progression from basic to advanced topics. However, this is a monolithic file (~400 lines) that could benefit from splitting advanced topics (fuzzing, benchmarks, HTTP testing) into separate reference files. | 2 / 3 |
Total | 10 / 12 Passed |
Activation
50%The description excels at specificity and distinctiveness by listing concrete Go-specific testing patterns and practices. However, it critically lacks any 'Use when...' guidance, which is essential for Claude to know when to select this skill from a large skill library. The trigger terms could also be expanded to include more natural user phrasings.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when writing Go tests, creating _test.go files, or when the user asks about testing Go code, benchmarking, or test coverage.'
Include common user phrasings as trigger terms: 'unit tests', 'write tests', 'test file', '_test.go', 'go test'
Consider adding file extension triggers like '.go test files' or 'testing package' to improve discoverability
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'table-driven tests, subtests, benchmarks, fuzzing, and test coverage' along with methodology 'TDD' and 'idiomatic Go practices'. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Go testing', 'table-driven tests', 'benchmarks', 'fuzzing', 'TDD', but missing common user variations like 'unit tests', 'test file', '_test.go', or 'write tests'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Go language testing with specific Go-idiomatic concepts (table-driven tests, subtests) that distinguish it from generic testing skills or other language testing skills. | 3 / 3 |
Total | 9 / 12 Passed |
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.