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.

82

1.07x
Quality

78%

Does it follow best practices?

Impact

87%

1.07x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

86%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 well-structured, highly actionable skill with concrete commands, explicit version-precision rules, and verification steps (build and test) for a batch update operation. Its only gaps are minor redundancy around version-precision rules and the absence of an explicit fix-and-retry loop when verification fails.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence, with concrete commands throughout and no explanation of concepts Claude already knows. Minor over-trimming is possible: the Phase 1 file-type list overlaps with Phase 3's per-file update rules, and the Notes section repeats the minor-vs-patch precision rule already stated in Phase 0. Not 5 due to this minor duplication; not 3 because nearly every token is functional.

4 / 5

Actionability

Fully executable guidance throughout: a concrete fetch URL (https://go.dev/dl/?mode=json), find commands for locating files, exact before/after replacement examples ('go 1.23' → 'go 1.24', 'toolchain go1.23.5' → 'toolchain go1.24.1'), and runnable commands (go mod tidy, go mod vendor, go build ./..., go test ./...) plus a commit message template. Copy-paste ready with specific examples covering the common cases.

5 / 5

Workflow Clarity

Phases 0-5 are clearly sequenced with validation checkpoints (go build ./... and go test ./... in Phase 4) and an early skip-if-current check in Phase 2, so no missing-validation cap applies. Not 5 because error recovery is weak: 'note any failures and whether they are pre-existing' instructs observation only, with no fix-and-retry feedback loop.

4 / 5

Progressive Disclosure

No bundle files exist and none are needed at this size; the body is well-organized into numbered phases and a Notes section, with all content appropriately inline and nothing that warrants splitting into separate files. Easy to navigate as-is.

5 / 5

Total

18

/

20

Passed

Description

70%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 specific, third-person, and highly distinctive, covering the full workflow from fetching the latest version to committing. Its main weakness is the complete absence of a 'when to use' trigger clause, which caps completeness, and a few missing natural synonyms like 'upgrade' or 'bump'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to update, upgrade, or bump the Go version in go.mod, CI workflows, or other config files.'

Include common user synonyms such as 'upgrade' or 'bump' alongside 'update' to improve trigger term coverage.

Name the concrete config file types (CI workflows, Makefiles, Dockerfiles, .tool-versions) instead of the generic 'related config files'.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Fetches the current latest version from the web, updates all relevant files, runs go mod tidy, and commits') but leaves coverage of which config files (CI workflows, Makefiles, Dockerfiles) slightly abstract via 'related config files'. Not 5 because the affected file types are not named; not 3 because far more than 1-2 concrete actions are specified.

4 / 5

Completeness

The 'what' is clear and multi-step, but there is no 'Use when...' clause or any equivalent trigger guidance for when Claude should invoke this skill. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('Go version', 'go.mod', 'latest stable release', 'go mod tidy'), but misses common variations like 'upgrade', 'bump', or 'bump Go version'. Good keyword coverage with a few natural synonyms missing, matching the 4 anchor.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Go toolchain version management in go.mod and related config) with distinct triggers like 'go.mod', 'go mod tidy', and 'Go version'; minimal overlap risk with other skills.

5 / 5

Total

16

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

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.