CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

go-backend-microservices

Go backend development best practices for microservices with clean architecture, observability, and production-ready patterns

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./go-backend-microservices/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

A lean, well-organized standards reference that avoids verbosity entirely, but most guidance stays at the directive level — naming practices without code examples, specific rules, or validation steps. Claude would have to fill in the concrete implementation details itself.

Suggestions

Add short executable snippets for the core patterns — e.g., error wrapping, interface-based dependency injection, graceful shutdown with signal.NotifyContext, and a bounded worker pool — so the guidance is copy-paste ready.

Replace vague directives like "Implement proper authentication and authorization" and "Use secure defaults for JWT tokens and cookies" with specific rules or example implementations.

Add explicit validation checkpoints, e.g., "Before declaring a change done: golangci-lint run && go test ./... must pass," to give the CI/CD and testing sections a concrete verify loop.

DimensionReasoningScore

Conciseness

The body is a lean set of bullet lists with no padded explanations of concepts Claude already knows; the project-structure tree and one-line idiom ("fmt.Errorf(\"context: %w\", err)") earn their tokens. It is not 5 because a few bullets like "Always check and handle errors explicitly" and "Keep comments up to date with code changes" restate standard Go knowledge and could be trimmed.

4 / 5

Actionability

There is some concrete guidance (the wrapped-error idiom, the directory layout, "Use golangci-lint", "Export metrics in Prometheus format"), but most directives are high-level and lack executable specifics — e.g., "Apply Clean Architecture with clear separation into handlers, services, repositories, and domain models" and "Implement proper authentication and authorization" name the practice without any code example or concrete rule. It is not 4 because the core patterns have no code or commands to execute, and not 2 because the concrete elements go beyond minimal hints.

3 / 5

Workflow Clarity

Sections are logically ordered (principles → project structure → error/context handling → observability → security → testing → concurrency → documentation → CI/CD), but there is no step sequence with validation checkpoints anywhere; even the CI/CD section lists practices ("Maintain CI integration", "Run tests on every pull request") without verify steps. It is not 4 because checkpoints are absent, and not 2 because the content is coherent and gap-free for a standards reference.

3 / 5

Progressive Disclosure

The skill is a single, well-organized file with clear section headers and no external bundle files exist (references/, scripts/, assets/ are absent), so nothing is buried or nested. It is not 5 because at ~100 lines it exceeds the under-50-line threshold where section organization alone earns full marks, and a few sections (observability, testing) could be split into reference files if the skill grows.

4 / 5

Total

14

/

20

Passed

Description

61%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 communicates a clear, well-scoped niche (Go microservices backend with named practice areas) in third person without fluff, but it lists topics rather than concrete actions and omits any "when to use" trigger guidance. Both omissions cap specificity and completeness at the midpoint.

Suggestions

Add an explicit trigger clause, e.g., "Use when building, reviewing, or refactoring Go backend services, APIs, or microservices."

Convert topic nouns into concrete actions, e.g., "Applies clean architecture (handlers/services/repositories), OpenTelemetry-based observability, and table-driven testing conventions to Go microservices."

Include natural synonyms such as "Golang", "REST/gRPC APIs", and "backend services" to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

"Go backend development best practices for microservices" names the domain and "clean architecture, observability, and production-ready patterns" specifies concrete scope areas, but the description contains no action verbs — only topic nouns. It is not 4 because no specific actions are listed, and not 2 because it conveys more scoped coverage than a bare domain name.

3 / 5

Completeness

The "what" is clear (Go backend best practices with named pattern areas), but there is no "Use when..." clause or any equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not 2 because the "what" half is specific and well-stated.

3 / 5

Trigger Term Quality

"Go", "backend", "microservices", "clean architecture", and "observability" are natural terms users would say when needing this skill. It is not 5 because common synonyms and variations like "Golang", "API", "REST", or "gRPC" are missing.

4 / 5

Distinctiveness Conflict Risk

"Go backend development... for microservices" carves out a clear niche with distinct triggers and only minor overlap risk with general Go or general backend skills. It is not 5 because it would still fire on broad Go backend questions that a more narrowly scoped skill might serve better.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

Mindrally/skills

Path

go-backend-microservices/SKILL.md

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.