CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

golang

Write, test, and maintain Go code following idiomatic patterns, standard library conventions, and Go best practices. Use when working with Go/Golang projects, writing Go code, or reviewing Go implementations.

Quality

67%

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 ./dotfiles/shared/.config/claude/forgoty-marketplace/plugins/software-engineering/skills/golang/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

32%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 a thin index that adds little beyond the description: it delegates all substance to GOLANG-RULES.md, which is missing from the bundle, and the file is cut off mid-list under "Rule Categories Overview" with no categories enumerated. Combined with grammar slips ("follow this rules") and duplicated trigger guidance, the content provides neither executable guidance nor working navigation.

Suggestions

Include the referenced GOLANG-RULES.md in the bundle (under references/) so the body's primary pointer resolves, and verify every referenced path exists.

Complete the truncated "Rule Categories Overview" section by actually listing the rule categories with severity context, or link per-category reference files so the body serves as a real navigable index.

Add concrete, executable guidance to the Quick Start (e.g., a short idiomatic code example, a go test/gofmt command, or the expected rule-severity workflow) and drop the bullets and steps that merely restate the description.

DimensionReasoningScore

Conciseness

The body is short but contains redundancy: the "When to Use This Skill" bullet list restates trigger guidance already in the description, and step 4 "Follow idiomatic Go patterns (simplicity, clarity, composition)" repeats the intro sentence — mostly efficient but could be tightened.

3 / 5

Actionability

There is no code, command, or concrete example; guidance consists of high-level directives ("Read GOLANG-RULES.md", "RESPECT rules by severity: Critical → High → Medium → Low") that delegate everything to a referenced file — which does not exist in the bundle.

2 / 5

Workflow Clarity

The numbered Quick Start exists but steps 2–4 ("STRICTLY follow this rules", "RESPECT rules by severity", "Follow idiomatic Go patterns") are parallel directives rather than a sequence, no validation checkpoints exist, and the document ends mid-sentence at "in these categories:" with the promised list missing.

2 / 5

Progressive Disclosure

The single reference to GOLANG-RULES.md is one level deep and clearly signaled, but the file is absent from the bundle and the "Rule Categories Overview" section that would enable navigation is truncated, so the pointer fails in practice and no other structure guides discovery.

2 / 5

Total

9

/

20

Passed

Description

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

A strong description: concrete capabilities, explicit "Use when" triggers covering writing and reviewing workflows, and the Go/Golang synonym pair. Only minor gaps — "Go best practices" is mildly fluffy and a few natural trigger terms like .go files are absent.

DimensionReasoningScore

Specificity

"Write, test, and maintain Go code following idiomatic patterns, standard library conventions" lists several concrete actions with clear qualifiers, but the trailing "and Go best practices" is generic padding, leaving minor gaps versus the comprehensive 5 anchor.

4 / 5

Completeness

It explicitly answers what ("Write, test, and maintain Go code following idiomatic patterns...") and when ("Use when working with Go/Golang projects, writing Go code, or reviewing Go implementations") with concrete trigger phrases, matching the 5 anchor.

5 / 5

Trigger Term Quality

"Go/Golang projects", "writing Go code", and "reviewing Go implementations" are natural user phrases and the Go/Golang pairing covers the main synonym, but common variations like the .go extension or tool names (gofmt, unit tests) are missing.

4 / 5

Distinctiveness Conflict Risk

The Go/Golang niche with language-specific triggers ("Go projects", "Go implementations") is clearly distinguishable from other language or general coding skills with minimal overlap risk.

5 / 5

Total

18

/

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

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

forgoty/dotfiles

Path

dotfiles/shared/.config/claude/forgoty-marketplace/plugins/software-engineering/skills/golang/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.