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.

1.07x

Quality

83%

Does it follow best practices?

Impact

87%

1.07x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-3

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

The content is a tight, fully executable phased workflow with explicit validation checkpoints and no wasted tokens. It exemplifies concise, actionable instruction design with nothing material to improve.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it never explains what Go or go.mod is, and every section (phases, file list, notes) carries actionable content with no concept padding.	3 / 3
Actionability	Provides fully executable guidance: the live API URL, concrete `find`/`go mod tidy`/`go build`/`go test` commands, exact string-replacement examples, and a copy-paste commit message template.	3 / 3
Workflow Clarity	A clear Phase 0–5 sequence with explicit validation checkpoints (Phase 2 skip-if-current, Phase 4 `go build`/`go test` verification with failure notes) covers this batch file-mutation workflow.	3 / 3
Progressive Disclosure	A single, well-organized SKILL.md with cleanly delineated phases and no need for external references; structure is appropriate for a focused single-purpose skill.	3 / 3
	Total	12 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 specific and distinctive, enumerating concrete actions and a clear niche, but it lacks an explicit 'when to use' trigger clause and misses some natural trigger-term variations. Adding a 'Use when...' sentence with terms like 'golang' and 'upgrade Go' would raise the weaker dimensions.

Suggestions

Append a 'Use when the user asks to update, upgrade, or bump the Go/golang version' clause to satisfy the completeness 'when' requirement.

Broaden trigger terms to include natural phrasings like 'golang', 'upgrade Go version', and 'bump Go' alongside 'Go version' and 'go.mod'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Fetches the current latest version from the web, updates all relevant files, runs go mod tidy, and commits' — matching the top anchor for specific capabilities.	3 / 3
Completeness	Clearly answers what the skill does, but provides no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 2.	2 / 3
Trigger Term Quality	Includes relevant terms ('Go version', 'go.mod') but omits common variations a user might say such as 'golang', 'upgrade Go', or 'bump Go version', so coverage is incomplete.	2 / 3
Distinctiveness Conflict Risk	Targets a clear niche (updating the Go toolchain version) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: mattermost/mattermost-ai-marketplace
Path: plugins/dev-workflows/skills/update-go-version/SKILL.md
Commit: 90ab32d

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