CtrlK
BlogDocsLog inGet started
Tessl Logo

use-modern-go

Apply modern Go syntax guidelines based on the project's Go version. Use whenever writing, editing, or reviewing Go (.go) code — not only when explicitly asked for guidelines.

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

88%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 content is a highly actionable, well-structured reference with executable commands, concrete before/after examples, and a validation-backed modernization workflow. It is lean but carries minor redundancy in its imperative phrasing and could in principle split the feature catalog into a reference file.

DimensionReasoningScore

Conciseness

The body is a lean feature catalog using a tight 'X not Y' pattern with no padding about what Go is, and assumes Claude's competence; minor verbosity comes from repeated 'ALWAYS use...' imperatives and full Before/After blocks for every recent version that could be trimmed slightly.

4 / 5

Actionability

Fully executable guidance throughout: copy-paste go fix/build/test commands and concrete Before/After Go code blocks covering the common modernization cases per version.

5 / 5

Workflow Clarity

The modernization workflow is clearly sequenced — detect version, gate on installed toolchain, run go fix, then build and test — with explicit validation steps (go build/go test), feedback loops ('compilation errors after go fix are normal and require manual resolution'), and a caveats checklist for the destructive batch operation.

5 / 5

Progressive Disclosure

Well-organized with clear version-keyed section headers making navigation easy, and appropriately self-contained with no nested references; the large per-version feature catalog could arguably live in a separate reference file, which keeps it just short of a 5.

4 / 5

Total

18

/

20

Passed

Description

82%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 strong: it explicitly states what the skill does and when to use it, with natural trigger terms and the .go extension. Its only weakness is that the 'what' is somewhat abstract ('apply guidelines') rather than listing concrete actions.

DimensionReasoningScore

Specificity

Names the domain ('modern Go syntax guidelines based on the project's Go version') and one concrete action ('apply guidelines'), but does not enumerate the multiple specific actions (modernizing, reviewing, fixing) it actually performs, so coverage is not comprehensive.

3 / 5

Completeness

Explicitly answers both 'what' ('Apply modern Go syntax guidelines based on the project's Go version') and 'when' ('Use whenever writing, editing, or reviewing Go (.go) code — not only when explicitly asked for guidelines') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural terms users would say are well covered — 'writing, editing, or reviewing Go (.go) code' including the .go file extension — but synonyms like 'modernizing Go' or 'Go version upgrade' are absent.

4 / 5

Distinctiveness Conflict Risk

A clear niche — version-aware modern Go syntax guidance — with distinct triggers (Go/.go code) and minimal overlap with other skills; the 'based on the project's Go version' framing further narrows it.

5 / 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

relative_links

Relative link issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
ardanlabs/service
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.