go-implementor

Expert Go software engineer for implementing production-grade backend services with idiomatic Go patterns, testing, and observability. Use when implementing Go code following best practices.

Quality

49%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/dev-skills/skills/go-implementor/SKILL.md

Quality

Content

46%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill provides genuinely useful, executable Go code patterns covering common backend scenarios, which is its primary strength. However, it is significantly bloated with persona descriptions, competency lists, and explanations of concepts Claude already knows. The content would benefit greatly from being split into a concise overview with references to detailed pattern files, and from adding explicit validation/feedback loops to the workflow.

Suggestions

Remove the 'Your Identity', 'Core Competencies', and 'Communication Style' sections entirely — these describe traits Claude already has and waste tokens on persona-building rather than actionable guidance.

Split the large code examples (service layer, database patterns, error handling, testing) into separate referenced files (e.g., PATTERNS.md, TESTING.md) and keep SKILL.md as a concise overview with links.

Add explicit feedback loops to the Task Execution Workflow: e.g., 'If tests fail → review error output → fix → re-run before proceeding' and 'If linter fails → address warnings → re-run'.

Remove the DON'T examples section — Claude already knows not to use panic for error handling or ignore errors; replace with a brief 'avoid' bullet list if needed.

Dimension	Reasoning	Score
Conciseness	Heavily padded with identity/persona sections ('8+ years of experience', listing cloud providers, 'Financial services and payment systems') that Claude doesn't need. Core competencies section is a bullet-point list of concepts Claude already knows. The DON'T examples explain obvious anti-patterns. The communication Style section at the end is unnecessary filler. Much of this could be cut to focus on the genuinely useful code patterns.	2 / 5
Actionability	Contains substantial executable Go code examples covering handlers, services, repositories, error handling, table-driven tests, and transactions. The code is concrete and copy-paste ready. Minor gap: the usage section shows CLI-style invocations that aren't real tool commands, and some patterns (like writeJSON, writeError helpers) are referenced but not defined.	4 / 5
Workflow Clarity	The 'Task Execution Workflow' provides a 10-step sequence but lacks explicit validation checkpoints and feedback loops. Steps like 'Run Tests' and 'Verify' are listed but there's no guidance on what to do if they fail. The code review checklist is useful but is a static list rather than an integrated workflow with error recovery.	3 / 5
Progressive Disclosure	This is a monolithic ~300-line file with no references to external files and no bundle structure. The extensive code examples for service layers, database patterns, error handling, and testing could each be separate reference files. Everything is inlined in a single document with no navigation aids beyond section headers.	2 / 5
	Total	11 / 20 Passed

Description

53%Scale 1-5

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 establishes the domain (Go backend development) and includes a 'Use when' clause, which is good. However, it lacks concrete actions and specific trigger terms, relying instead on broad categories like 'idiomatic Go patterns' and 'observability' without detailing what specific tasks the skill performs. The trigger clause is too generic to reliably differentiate this skill from other coding-related skills.

Suggestions

Add concrete actions such as 'write HTTP handlers, create middleware, implement interfaces, set up structured logging, write table-driven tests'

Include natural trigger terms and synonyms like 'Golang,' '.go files,' 'API endpoints,' 'microservices,' 'goroutines,' 'concurrency'

Make the 'Use when' clause more specific, e.g., 'Use when the user asks to write, review, or refactor Go code, build REST APIs in Go, or set up Go project structure'

Dimension	Reasoning	Score
Specificity	Names the domain (Go backend services) and mentions broad categories like 'testing' and 'observability,' but does not list concrete actions (e.g., 'write HTTP handlers,' 'create middleware,' 'set up structured logging'). The phrase 'idiomatic Go patterns' is vague.	2 / 5
Completeness	Has both a 'what' (implementing production-grade backend services with Go patterns, testing, observability) and a 'when' ('Use when implementing Go code following best practices'), though the 'when' clause is generic and could be more specific about trigger scenarios.	4 / 5
Trigger Term Quality	Includes relevant keywords like 'Go,' 'backend services,' 'testing,' and 'observability,' but misses common natural terms users would say such as 'Golang,' 'API,' 'microservice,' 'HTTP server,' 'goroutine,' or '.go files.'	3 / 5
Distinctiveness Conflict Risk	Specifying 'Go' helps distinguish it from generic coding skills, but 'backend services,' 'testing,' and 'observability' are broad enough to overlap with skills for other languages or general backend development skills.	3 / 5
	Total	12 / 20 Passed

Validation

81%

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 — 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

Repository: rikdc/ai-skills
Path: plugins/dev-skills/skills/go-implementor/SKILL.md
Commit: a43676e

Reviewed: 3 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.