CtrlK
BlogDocsLog inGet started
Tessl Logo

golang-safety

Defensive Golang coding to prevent panics, silent data corruption, and subtle runtime bugs. Use when encountering nil panics, append aliasing, map concurrent access, float comparison pitfalls, or zero-value design questions. Also use when reviewing code for nil-safety, numeric conversion overflow, resource lifecycle issues (defer in loops), or defensive copying of slices and maps.

74

Quality

93%

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

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 defensive-Go reference with highly actionable code examples and proper progressive disclosure into two real deep-dive files. The main weakness is minor structural duplication (a repeated Cross-References section and a Common Mistakes table that restates the summary).

Suggestions

Remove the duplicate '## Cross-References' section (it appears at both line 257 and line 281) and merge the two link lists into one.

Either drop the 'Common Mistakes' table or the 'Best Practices Summary' since they cover overlapping ground, keeping the more actionable of the two.

Add a concrete linter invocation example or validation step in 'Enforce with Linters' so the guidance is executable rather than only pointing to another skill.

DimensionReasoningScore

Conciseness

Tight ✗/✓ code examples and tables with no conceptual padding, but the '## Cross-References' header is duplicated (appears twice) and the 'Common Mistakes' table restates the 'Best Practices Summary' — structural duplication that could be trimmed.

4 / 5

Actionability

Provides copy-paste-ready, executable Go snippets with bad/good pairs covering the common cases — nil interface, nil map, append aliasing, int truncation, float epsilon, defer-in-loop, sync.Once, and defensive copy via slices.Clone.

5 / 5

Workflow Clarity

Organized by clear topical sections; as a reference/knowledge skill it has no destructive multi-step process so the validation cap does not apply, but there is no explicit process sequence or checkpoint workflow to merit a 5.

4 / 5

Progressive Disclosure

Both bundle files (references/nil-safety.md, references/slice-map-safety.md) are real, linked one level deep at the appropriate sections, and clearly signaled; overview stays in SKILL.md while deep dives live in references.

5 / 5

Total

18

/

20

Passed

Description

100%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.

A high-quality description that clearly states what the skill does and when to use it, with concrete, natural trigger terms and a distinct Go-safety niche. It is comprehensive without being padded.

DimensionReasoningScore

Specificity

Lists many concrete actions/concerns — 'prevent panics, silent data corruption', 'nil panics, append aliasing, map concurrent access, float comparison pitfalls, zero-value design', 'numeric conversion overflow', 'defer in loops', 'defensive copying' — giving comprehensive coverage of the domain.

5 / 5

Completeness

'Defensive Golang coding to prevent panics, silent data corruption, and subtle runtime bugs' answers what, and two explicit 'Use when ...' / 'Also use when ...' clauses answer when with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases a Go developer or reviewer would actually say — 'nil panics', 'append aliasing', 'defer in loops', 'nil-safety', 'defensive copying', 'numeric conversion overflow' — with synonyms across both 'Use when' clauses.

5 / 5

Distinctiveness Conflict Risk

Targets a clear Go-safety/correctness niche with Go-specific triggers (append aliasing, typed-nil, defer-in-loops) that are unlikely to fire for unrelated skills, keeping conflict risk minimal.

5 / 5

Total

20

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

14

/

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.