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
Quality
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 placeholder that provides almost no useful information for skill selection. It relies entirely on the skill name without explaining capabilities, use cases, or providing natural trigger terms. The redundant trigger terms and lack of any concrete actions make this description ineffective for Claude to distinguish when to use this skill.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates Go HTTP handlers with routing, middleware integration, request validation, and response formatting'
Add a 'Use when...' clause with natural trigger terms like 'Use when creating Go API endpoints, HTTP handlers, REST routes, or when the user mentions gin/echo/chi handlers'
Include common variations of trigger terms users might naturally say: 'go api', 'http endpoint', 'rest handler', 'web server route', specific framework names
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the domain ('Go Handler Generator') but provides no concrete actions. It doesn't explain what the skill actually does - no mention of generating HTTP handlers, creating routes, scaffolding code, etc. | 1 / 3 |
Completeness | Missing both 'what' and 'when'. The description doesn't explain what the skill does beyond its name, and there's no 'Use when...' clause or equivalent guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('go handler generator' listed twice) and overly specific. Missing natural variations users might say like 'create go endpoint', 'http handler', 'REST API handler', 'gin handler', 'echo handler', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The 'Go Handler Generator' name provides some specificity to the Go language domain, but 'Backend Development' category is very broad. Without concrete actions described, it could conflict 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 content is entirely generic boilerplate with no actionable information about Go handler generation. It describes capabilities abstractly without providing any code examples, specific patterns, or concrete guidance. The content could apply to virtually any skill topic by swapping keywords.
Suggestions
Add executable Go code examples showing how to generate handlers (e.g., a template or generator function with actual implementation)
Define a clear workflow: 1) Define route, 2) Generate handler scaffold, 3) Add business logic, 4) Register with router - with code for each step
Include specific Go handler patterns (e.g., http.HandlerFunc signature, middleware chaining, error handling patterns) rather than generic descriptions
Remove all generic boilerplate ('provides automated assistance', 'follows best practices') and replace with concrete, Go-specific guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing specific about Go handler 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 ('generates production-ready code') but never shows how to actually generate a Go handler. | 1 / 3 |
Workflow Clarity | No workflow or steps are defined. The content lists vague capabilities but provides no sequence for generating handlers, no validation steps, and no concrete process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic descriptions with no references to detailed documentation, examples, or supporting files. There's no structure for discovery or navigation. | 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
994edc4
- 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.