CtrlK
BlogDocsLog inGet started
Tessl Logo

update-go-version

Update the Go version in go.mod (and related config files) to the latest stable release. Fetches the current latest version from the web, updates all relevant files, runs go mod tidy, and commits.

80

1.07x
Quality

76%

Does it follow best practices?

Impact

87%

1.07x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/dev-workflows/skills/update-go-version/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

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

This is a well-structured skill with an excellent phased workflow and clear validation checkpoints. Its main weakness is that the actionability could be improved with more executable code—particularly for parsing the Go API response and performing the actual file updates. Conciseness is good but could be tightened slightly by removing obvious information.

Suggestions

Add an executable code snippet (e.g., using curl + jq) for fetching and parsing the latest Go version from the downloads API in Phase 0.

Provide concrete sed or similar commands for the version string replacements in Phase 3, rather than describing the replacements in prose.

DimensionReasoningScore

Conciseness

The content is mostly efficient and well-structured, but includes some information Claude would already know (e.g., explaining what `.nvmrc` is and marking it 'skip', listing obvious file types like Dockerfile). The file type listing is borderline—useful as a checklist but slightly verbose.

2 / 3

Actionability

Provides concrete bash commands for discovery and clear string replacement patterns, but lacks executable code for the key step of fetching and parsing the Go downloads API JSON. The update instructions describe what to do rather than providing exact sed/awk commands or code snippets for performing the replacements.

2 / 3

Workflow Clarity

Excellent phased workflow with clear sequencing (discover → identify → check → update → tidy/verify → commit). Phase 4 includes explicit validation steps (go mod tidy, go build, go test) with a feedback-aware note about pre-existing failures. The skip-if-current check in Phase 2 is a good guard.

3 / 3

Progressive Disclosure

For a standalone skill with no bundle files, the content is well-organized into clearly labeled phases with appropriate section headers. The skill is a reasonable length and doesn't need external references—everything is appropriately inline and easy to navigate.

3 / 3

Total

10

/

12

Passed

Description

82%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-written description with strong specificity and clear domain focus on Go version management. It lists concrete actions in a logical sequence and uses natural developer terminology. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to update Go version, upgrade Go, bump go.mod version, or mentions updating to the latest Go release.'

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: updating Go version in go.mod, fetching latest version from the web, updating related config files, running go mod tidy, and committing. These are clear, actionable steps.

3 / 3

Completeness

Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The when is only implied by the description of what it does.

2 / 3

Trigger Term Quality

Includes natural keywords users would say: 'Go version', 'go.mod', 'latest stable release', 'go mod tidy', 'config files'. These are terms a developer would naturally use when wanting to update their Go version.

3 / 3

Distinctiveness Conflict Risk

Very specific niche: updating Go version in go.mod and related files. Unlikely to conflict with other skills due to the precise domain (Go language version management) and specific file references (go.mod).

3 / 3

Total

11

/

12

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

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
mattermost/mattermost-ai-marketplace
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.