go-test-generator
Go Test Generator - Auto-activating skill for Test Automation. Triggers on: go test generator, go test generator Part of the Test Automation skill category.
35
Quality
3%
Does it follow best practices?
Impact
93%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/09-test-automation/go-test-generator/SKILL.mdQuality
Discovery
7%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 description is essentially a template placeholder with minimal useful content. It lacks concrete actions, meaningful trigger terms, and explicit usage guidance. The redundant trigger term and generic category label provide almost no value for skill selection.
Suggestions
Add specific actions the skill performs, e.g., 'Generates table-driven tests, creates mock implementations, scaffolds test files with proper Go conventions'
Add a 'Use when...' clause with natural trigger terms like 'Use when writing Go tests, creating unit tests for Go functions, generating test cases for .go files, or when user mentions golang testing'
Include file type triggers and common user phrases: '.go files', 'golang', 'go unit test', 'test coverage', 'go test -v'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states 'Go Test Generator' and 'Test Automation' without describing any concrete actions. It doesn't explain what the skill actually does - no mention of generating test files, creating test cases, mocking, or any specific testing operations. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and has no explicit 'Use when...' clause or equivalent guidance. The 'Triggers on' section is not a proper when-to-use explanation. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('go test generator' listed twice) and overly narrow. Missing natural variations users would say like 'write tests for go', 'golang unit tests', 'test my go code', 'create test file', or 'generate test cases'. | 1 / 3 |
Distinctiveness Conflict Risk | The 'Go' language specification provides some distinctiveness from generic test generators, but 'Test Automation' is vague enough to potentially conflict with other testing-related skills. The lack of specific capabilities makes differentiation difficult. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is essentially a placeholder with no actionable content. It describes what a Go test generator skill would do without providing any actual guidance, code examples, or workflows. The content consists entirely of generic boilerplate that could apply to any skill topic.
Suggestions
Add executable Go test code examples showing table-driven tests, subtests, and common patterns like `func TestXxx(t *testing.T)`
Include a concrete workflow: 1) Identify function to test, 2) Generate test file with naming convention, 3) Write test cases, 4) Run `go test -v` to validate
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with specific Go testing guidance
Add examples of mocking with interfaces, using testify or gomock, and show expected test output formats
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Go test generation. Phrases like 'provides automated assistance' and 'follows industry best practices' are filler that Claude doesn't need. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly but never shows how to actually generate Go tests - no examples, no code snippets, no specific patterns. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content mentions 'step-by-step guidance' but provides none. There are no validation checkpoints or sequences for test generation. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, no links to examples, and no structured navigation to deeper content. | 1 / 3 |
Total | 4 / 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 |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
f17dd51
- 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.