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

69%

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

63%Weight 40%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 body is rich with concrete, executable Go examples and a clear implementation workflow, making it highly actionable. Its weaknesses are padding that restates Go fundamentals Claude already knows, no error-recovery feedback loop in the workflow, and a monolithic single-file structure with no progressive disclosure.

Suggestions

Remove or drastically trim the 'Your Identity', 'Core Competencies', and 'Communication Style' sections, which restate knowledge Claude already has.

Add an explicit feedback loop to the workflow (e.g. 'If tests fail, fix and re-run before proceeding to observability/documentation').

Move the detailed pattern catalogs (project structure, service layer, database patterns) into reference files under ./references/ and link to them from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The code-heavy sections earn their tokens, but 'Your Identity', 'Core Competencies', and 'Communication Style' restate Go concepts and senior-developer persona details Claude already knows, adding noticeable padding.	3 / 5
Actionability	Provides concrete, copy-paste-ready code for service layers, sentinel/wrapped errors, and transactions, but the examples are illustrative snippets rather than fully runnable programs with minor gaps.	4 / 5
Workflow Clarity	The 10-step Task Execution Workflow is clearly sequenced with checkpoints (run tests with race detector, verify against acceptance criteria) and a code review checklist, but lacks an explicit error-recovery feedback loop.	4 / 5
Progressive Disclosure	No bundle files exist and all ~340 lines are inlined in SKILL.md; section headers give structure, but detailed pattern catalogs that could live in separate references are inlined with no file-based navigation.	3 / 5
	Total	14 / 20 Passed

Description

75%Weight 40%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 is solid: it states a clear domain, lists several concrete capabilities, and includes an explicit 'Use when' trigger. It is held back from a 5 by generic trigger phrasing and missing common synonyms like 'Golang' or '.go files'.

Suggestions

Tighten the 'Use when' clause with concrete trigger phrases, e.g. 'Use when implementing Go services, handlers, or tests, or when the user mentions Golang or .go files.'

Add common synonyms/file extensions ('Golang', '.go files') to improve trigger-term coverage.

Concretize the actions (e.g. 'implement HTTP/gRPC handlers', 'write table-driven tests', 'instrument with metrics and tracing') instead of the abstract 'idiomatic Go patterns, testing, and observability'.

Dimension	Reasoning	Score
Specificity	Names the Go backend domain and several concrete actions (implementing production-grade services, idiomatic patterns, testing, observability), with only minor gaps in coverage rather than comprehensive enumeration.	4 / 5
Completeness	Explicitly answers both 'what' (expert Go engineer implementing production-grade backend services) and 'when' ('Use when implementing Go code following best practices'), though the trigger clause is somewhat generic.	4 / 5
Trigger Term Quality	Includes natural terms a user would say ('Go', 'Go code', 'backend services') but omits common synonyms and file extensions like 'Golang' or '.go files'.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear Go-implementation niche with minimal conflict risk, with only minor overlap potential against closely related Go skills such as a code reviewer.	4 / 5
	Total	16 / 20 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

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

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