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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill go-test-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is essentially a placeholder that provides almost no useful information for skill selection. It names the skill and category but fails to describe any concrete capabilities, lacks natural trigger terms users would actually say, and provides no guidance on when Claude should select this skill over others.
Suggestions
Add specific actions the skill performs, e.g., 'Generates table-driven tests, creates mock implementations, adds test coverage for Go functions and packages'
Include a 'Use when...' clause with natural trigger terms like 'write tests for my Go code', 'golang unit tests', 'test coverage', 'go test file', '_test.go'
Remove duplicate trigger terms and expand to include variations users naturally say when requesting Go testing help
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Go Test Generator', 'Test Automation') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of generating test files, creating test cases, mocking, etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and the 'when' is only a mechanical trigger list rather than meaningful usage guidance. No 'Use when...' clause or equivalent explicit trigger guidance. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('go test generator' listed twice) and overly specific. Missing natural variations users would say like 'write tests for go', 'golang unit tests', 'test my go code', 'generate test cases'. | 1 / 3 |
Distinctiveness Conflict Risk | The Go-specific focus provides some distinctiveness from general test generators, but 'Test Automation' is broad and could overlap with other testing skills. The lack of specific capabilities makes it harder to distinguish from similar tools. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is a generic template with no actual substance about Go test generation. It contains only meta-descriptions of what the skill claims to do without any concrete guidance, code examples, or actionable instructions. The content would be equally applicable to any skill topic by simply replacing 'go test generator' with another term.
Suggestions
Add executable Go test code examples showing table-driven tests, subtests, and common testing patterns (e.g., `func TestXxx(t *testing.T) { ... }`)
Include specific commands for running tests (`go test -v ./...`, `go test -cover`, `go test -race`)
Provide concrete guidance on test file naming conventions, test organization, and mocking strategies specific to Go
Remove all generic boilerplate ('provides automated assistance', 'follows industry best practices') and replace with actual Go testing content
| 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 waste tokens without adding value. | 1 / 3 |
Actionability | No concrete code, commands, or executable guidance is provided. The skill describes what it does abstractly ('generates production-ready code') but never shows how to actually generate Go tests or provides any specific examples. | 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 generating tests. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of vague descriptions with no references to detailed materials, examples, or related documentation. No structure for discovery or navigation to deeper content. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
69%Validation — 11 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 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.