go-handler-generator
Go Handler Generator - Auto-activating skill for Backend Development. Triggers on: go handler generator, go handler generator Part of the Backend Development skill category.
33
3%
Does it follow best practices?
Impact
84%
0.93xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/06-backend-dev/go-handler-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 title repeated with boilerplate metadata. It lacks concrete actions, natural trigger terms, and any explicit guidance on when to use the skill. It would be nearly indistinguishable from other backend Go skills and provides insufficient information for Claude to make an informed selection.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Go HTTP handler functions, request/response structs, middleware chains, and route registrations for REST APIs.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create Go HTTP handlers, API endpoints, route handlers, REST controllers, or scaffold Go web server code.'
Remove the duplicate trigger term and expand with natural variations users would say, such as 'Go API handler', 'Go endpoint', 'Go route', 'Go REST handler', 'Go HTTP handler'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('Go Handler Generator') but provides no concrete actions. It doesn't explain what the skill actually does—e.g., generating HTTP handlers, routing code, middleware, etc. 'Auto-activating skill for Backend Development' is vague filler. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'Use when...' clause or equivalent guidance on when Claude should select this skill. Both dimensions are very weak. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'go handler generator' repeated twice. There are no natural variations a user might say, such as 'Go HTTP handler', 'Go API endpoint', 'generate route handler', 'Go REST handler', or 'Go web server'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'Go' and 'handler generator' provides some specificity that distinguishes it from generic coding skills, but the lack of detail about what kind of handlers (HTTP, gRPC, etc.) and the broad 'Backend Development' category could cause overlap with other Go or backend skills. | 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 template with no actual technical content. It contains no Go code, no handler generation patterns, no concrete instructions, and no examples. Every section repeats the phrase 'go handler generator' without teaching Claude anything it could act on.
Suggestions
Add concrete, executable Go code examples showing handler generation (e.g., a template for generating HTTP handlers with proper error handling, middleware, and request/response types).
Define a clear workflow: e.g., 1) Parse route definition, 2) Generate handler scaffold, 3) Add validation/middleware, 4) Verify compilation with `go build`.
Remove all meta-description sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill rather than teaching how to perform the task.
Include specific patterns such as Go handler signatures, common middleware patterns, request parsing, and response formatting with copy-paste ready code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual technical content. Every section restates the same vague information about 'go handler generator' without adding substance. | 1 / 3 |
Actionability | There is zero concrete guidance—no Go code, no handler patterns, no commands, no examples of generated output. The skill describes rather than instructs, offering only vague promises like 'provides step-by-step guidance' without actually providing any. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, no validation checkpoints. The content merely states it 'provides step-by-step guidance' without including any actual steps. | 1 / 3 |
Progressive Disclosure | The content is a flat, repetitive document with no meaningful structure. There are no references to detailed files, no code examples to organize, and the sections are redundant rather than progressively disclosing useful information. | 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
3076d78
- 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.