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.
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill go-handler-generatorOverall
score
19%
Does it follow best practices?
Validation for skill structure
Activation
7%This description is severely underdeveloped, consisting mostly of auto-generated boilerplate with no substantive content. It fails to explain what the skill does, what actions it performs, or when Claude should use it. The redundant trigger terms and lack of natural keywords make it unlikely to be selected appropriately.
Suggestions
Add specific actions the skill performs, e.g., 'Generates Go HTTP handlers with routing, middleware integration, request validation, and response formatting'
Include a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to create Go endpoints, HTTP handlers, REST API routes, or scaffold web server code in Go'
Add natural trigger terms users would say: 'go endpoint', 'http handler', 'REST handler', 'gin routes', 'echo handler', 'go web server', 'API endpoint'
| 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 | Fails to answer both 'what does this do' and 'when should Claude use it'. There's no explanation of capabilities and no 'Use when...' clause or equivalent guidance for when to 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 Go language and handlers, but without describing what kind of handlers or what it generates, it could overlap with other Go-related or code generation skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%This skill content is essentially a placeholder template with no actual instructional value. It contains only generic descriptions of what a skill should do without any concrete guidance on Go handler generation - no code examples, no patterns, no specific techniques, and no actionable steps.
Suggestions
Add concrete, executable Go code examples showing how to generate HTTP handlers (e.g., using net/http, gin, or chi)
Include specific patterns for handler generation such as request validation, error handling, and response formatting
Define a clear workflow: 1) Define route, 2) Create handler function, 3) Add middleware, 4) Register route - with code for each step
Remove all generic boilerplate text ('provides automated assistance', 'follows best practices') and replace with actual technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that explains nothing Claude doesn't already know. Phrases like 'provides automated assistance' and 'follows industry best practices' are meaningless filler with no actual information. | 1 / 3 |
Actionability | There is zero concrete guidance - no code examples, no commands, no specific steps for generating Go handlers. The content only describes what the skill supposedly does without showing how to do anything. | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequence, and no validation checkpoints. The skill claims to provide 'step-by-step guidance' but contains none. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative document with no structure beyond generic headings. There are no references to detailed materials, examples, or related documentation. | 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.