Go API testing patterns -- httptest setup, table-driven tests with subtests, test helpers, middleware testing, dependency injection with interfaces, database isolation, parallel tests, testify assertions, golden files
98
98%
Does it follow best practices?
Impact
99%
1.06xAverage score across 5 eval scenarios
Passed
No known issues
Quality
Discovery
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.
This is a well-crafted skill description that excels across all dimensions. It provides comprehensive specificity with concrete testing patterns, uses natural developer terminology, explicitly states both capabilities and trigger conditions, and carves out a clear niche in Go HTTP API testing that distinguishes it from general testing or Go development skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'httptest server setup, table-driven tests with subtests, test helpers, middleware testing, dependency injection with interfaces, database setup/teardown, parallel tests, testify assertions, and golden files.' | 3 / 3 |
Completeness | Clearly answers both what ('Go API testing patterns' with detailed list of capabilities) AND when ('Triggers when writing tests for any Go HTTP API, adding test coverage, or building a new API that needs tests'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Go', 'API', 'tests', 'test coverage', 'HTTP API', 'writing tests'. These are terms developers naturally use when seeking testing help. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Go language + HTTP API + testing specifically. The combination of 'Go', 'API', and 'testing' with specific patterns like 'httptest', 'testify' creates a distinct trigger profile unlikely to conflict with general testing or general Go skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an excellent skill document that provides comprehensive, actionable Go API testing patterns. The content is well-structured with executable code examples, clear workflows, and practical guidance. The Common Mistakes table and final checklist add significant value for quick reference and validation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code examples without explaining basic Go concepts Claude already knows. Every section delivers actionable patterns without padding or unnecessary context. | 3 / 3 |
Actionability | All code examples are fully executable and copy-paste ready. The skill provides complete test helpers, mock implementations, and real test patterns with specific commands like 'go test -run TestCreateUser/missing_email -v ./...'. | 3 / 3 |
Workflow Clarity | Clear sequences are provided throughout: when to use NewRecorder vs NewServer, the pattern for table-driven tests with t.Run, database setup/teardown order, and explicit guidance on t.Cleanup vs defer. The checklist provides validation checkpoints. | 3 / 3 |
Progressive Disclosure | Content is well-organized into 10 numbered sections with clear headers. Each section is self-contained. The skill references external verifiers at the end for deeper practice. The Common Mistakes table and Checklist provide quick-reference summaries. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (593 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
Reviewed
Table of Contents