backend-golang

Golang Developer Agent. Go 언어 기반 백엔드 개발을 담당합니다. Gin, Echo, GORM, 고성능 마이크로서비스 전문.

Quality

23%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/backend-golang/SKILL.md

Quality

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description identifies the technology stack well with specific Go frameworks but fails to provide explicit trigger conditions for skill selection. It lacks concrete action verbs describing what the skill actually does and has no 'Use when...' clause, which significantly limits Claude's ability to know when to select this skill over others.

Suggestions

Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Go/Golang development, Gin/Echo APIs, GORM database operations, or .go files'

Include concrete actions such as 'Creates REST APIs, implements middleware, writes database models, builds microservices'

Add common user terms like 'Go code', 'backend API', 'REST endpoints', '.go files' to improve trigger term coverage

Dimension	Reasoning	Score
Specificity	Names the domain (Go/Golang backend development) and mentions specific frameworks (Gin, Echo, GORM) and area (microservices), but doesn't list concrete actions like 'create APIs', 'write handlers', or 'implement database models'.	2 / 3
Completeness	Describes what it does (Go backend development with specific frameworks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill.	1 / 3
Trigger Term Quality	Includes relevant keywords like 'Golang', 'Go 언어', 'Gin', 'Echo', 'GORM', '마이크로서비스', but missing common variations users might say like 'Go code', 'backend API', 'REST endpoints', or file extensions like '.go'.	2 / 3
Distinctiveness Conflict Risk	The Go-specific frameworks (Gin, Echo, GORM) provide some distinction from generic backend skills, but '백엔드 개발' and 'microservices' could overlap with other language-specific backend developer skills.	2 / 3
	Total	7 / 12 Passed

Implementation

14%

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 essentially a placeholder that lists Go-related technologies and concepts without providing any actionable guidance. It lacks code examples, concrete patterns, workflow instructions, or references to detailed documentation. The content tells Claude what topics exist but not how to actually perform Go development tasks.

Suggestions

Add executable code examples for common patterns (e.g., Gin route setup, GORM model definition, error handling idioms)

Include a concrete workflow for setting up a new Go project with recommended structure and validation steps

Provide specific examples of Go idioms like proper error handling patterns and interface-based design with actual code

Add references to detailed documentation files for each framework (e.g., GIN.md, GORM.md) or include inline quick-start examples

Dimension	Reasoning	Score
Conciseness	The content is brief and doesn't over-explain concepts Claude knows, but it's essentially just a list of keywords and categories without actionable content, making the brevity feel empty rather than efficient.	2 / 3
Actionability	No concrete code examples, commands, or executable guidance provided. The content only lists frameworks and concepts without showing how to use them or what patterns to follow.	1 / 3
Workflow Clarity	No workflows, processes, or sequences are defined. The skill provides no guidance on how to approach Go development tasks, error handling patterns, or project setup steps.	1 / 3
Progressive Disclosure	No references to additional documentation, no structure for discovering more detailed information, and no clear organization beyond simple bullet lists of keywords.	1 / 3
	Total	5 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	10 / 11 Passed

Repository: shaul1991/shaul-agents-plugin
Commit: 9242c58

Reviewed: 29 days ago

Table of Contents

Discovery Implementation Validation

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.