CtrlK
BlogDocsLog inGet started
Tessl Logo

golang-modernize

Modernize Golang code to use recent language features, standard library improvements, and idiomatic patterns. Trigger proactively when writing or reviewing Go code and old-style patterns are detected, or when encountering a deprecation warning. Also use when the user explicitly asks for modernization, a Go version upgrade, or a CI/tooling refresh.

69

Quality

85%

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

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-structured, actionable modernization guide with clear workflows, validation checkpoints, and good use of one-level-deep reference files. The main improvement lever is removing the duplicated sub-agent description and tightening the dense priority list.

Suggestions

Deduplicate the parallel sub-agent description between the Full-scan mode bullet and Workflow step 7 — state it once and reference it from the other.

Tighten the 26-item Migration Priority Guide, e.g. collapse related items or move the exhaustive list into a reference file, keeping only the prioritized categories inline.

Add an explicit post-apply verification step (e.g. 'run the full test suite and go build ./... after applying a sweep') to close the workflow validation loop.

DimensionReasoningScore

Conciseness

Efficient and assumes Go competence with no basic-concept padding, but the parallel sub-agent description is repeated in both the Modes section and Workflow step 7, and the 26-item priority list is dense enough that minor tightening is possible.

4 / 5

Actionability

Concrete API replacements (math/rand -> math/rand/v2, reflect.PtrTo -> PointerTo), linter invocation, go mod tidy, and an example .modernize format give mostly executable guidance, with detailed before/after examples correctly delegated to references.

4 / 5

Workflow Clarity

A clear 9-step sequence with explicit validation checkpoints (go mod tidy + test suite, changelog review), a consent check, worktree isolation, and a .modernize feedback loop; only minor gaps such as an explicit post-apply build verification step.

4 / 5

Progressive Disclosure

A clear overview in SKILL.md with two well-signaled, real one-level-deep references (versions.md, tooling.md) that hold the bulk detail, making navigation easy.

5 / 5

Total

17

/

20

Passed

Description

92%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, complete, and distinctive, clearly stating both capabilities and natural trigger conditions. Trigger-term coverage is very good though not exhaustive of every synonym a user might use.

DimensionReasoningScore

Specificity

Names multiple concrete actions (recent language features, standard library improvements, idiomatic patterns) plus proactive/review and deprecation triggers, giving comprehensive coverage of what the skill does.

5 / 5

Completeness

Explicitly answers both what ('Modernize Golang code to use...') and when ('Trigger proactively when...', 'Also use when...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Strong natural trigger phrases ('writing or reviewing Go code', 'deprecation warning', 'Go version upgrade', 'CI/tooling refresh'), but a few common synonyms (e.g. 'refactor', 'migrate') are absent so it falls just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Go modernization) with distinct triggers (version upgrade, deprecation warnings, CI/tooling refresh) that minimize overlap with other skills.

5 / 5

Total

19

/

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_field

'metadata' should map string keys to string values

Warning

Total

15

/

16

Passed

Repository
samber/cc-skills-golang
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.