CtrlK
BlogDocsLog inGet started
Tessl Logo

go

Best practices for working with Go codebases. Use when writing, debugging, or exploring Go code, including reading dependency sources and documentation.

65

Quality

79%

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 ./Skills/agent-ops/go/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 well-structured, concise, and assumption-respecting, with an executable example and validation checkpoints that give a coherent workflow. Main gaps are the slightly abstract Procedure steps and an inaccurate reference path that weakens navigation.

Suggestions

Replace the generic Procedure steps with concrete, runnable commands (e.g., the specific validation commands to re-run) to lift actionability.

Fix the broken reference path from `Infrastructure/references/deep-guidance.md` to the actual `references/deep-guidance.md` so navigation resolves.

Tighten the Philosophy section or fold its principles into the existing Style/Constraints bullets to remove the last traces of padding.

DimensionReasoningScore

Conciseness

Lean, bullet-style guidance that assumes Go competence and avoids explaining basics, with only minor generic padding in the Philosophy section that could be trimmed.

4 / 5

Actionability

Provides one executable Go example (ParsePort with `%w` error wrapping) and concrete directives like "Return wrapped errors with `%w`", but the Procedure steps remain high-level ("Apply focused changes", "Re-run highest-signal validations") without specific commands.

4 / 5

Workflow Clarity

A clear 3-step Procedure is paired with a Validation section containing fail-fast and re-run-after-fix checkpoints, leaving only minor gaps in explicit feedback-loop detail.

4 / 5

Progressive Disclosure

Well-organized with a Table of Contents and a single one-level-deep, clearly signaled reference (deep-guidance.md), but the body cites the path as `Infrastructure/references/deep-guidance.md`, which does not match the actual bundle location `references/deep-guidance.md`.

4 / 5

Total

16

/

20

Passed

Description

83%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 concise and clearly answers both what the skill does and when to use it, with several concrete Go-specific actions and natural trigger phrases. It could be sharpened by adding the `.go` extension and golang synonyms, but it is otherwise strong.

DimensionReasoningScore

Specificity

Names the Go domain plus several concrete actions ("writing, debugging, or exploring Go code", "reading dependency sources and documentation"); minor gaps versus the fully comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both what ("Best practices for working with Go codebases") and when ("Use when writing, debugging, or exploring Go code") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Includes natural user phrases like "Go codebases", "Go code", and "debugging", but lacks the `.go` file extension and synonyms such as "golang" in the description itself, matching the good-but-incomplete anchor 4.

4 / 5

Distinctiveness Conflict Risk

"Go codebases" is a clear, language-scoped niche with distinct triggers, though there is minor overlap risk with the related [[rust-pro]] skill noted in See Also.

4 / 5

Total

17

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
jscraik/Agent-Skills
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.