golang-data-structures

Golang data structures — slices (internals, capacity growth, preallocation, slices package), maps (internals, hash buckets, maps package), arrays, container/list/heap/ring, strings.Builder vs bytes.Buffer, generic collections, pointers (unsafe.Pointer, weak.Pointer), and copy semantics. Use when choosing or optimizing Go data structures, implementing generic containers, using container/ packages, unsafe or weak pointers, or questioning slice/map internals.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 reference skill: concise overview with executable examples and decision tables, supported by clearly signaled one-level-deep bundle files that all resolve to real files. It is advisory rather than a sequenced workflow, which fits a selection/reference skill but keeps workflow_clarity just below full marks.

Dimension	Reasoning	Score
Conciseness	Lean, table-driven reference that assumes Go competence and avoids re-explaining basics; minor instances of phrasing that could be tightened (e.g. the Best Practices Summary repeats detail later expanded per-section), but no padding of concepts Claude already knows.	4 / 5
Actionability	Provides copy-paste-ready code for preallocation, slices.Grow, generic Set, array-as-map-key, plus concrete decision tables (container/ choice, Builder vs Buffer, pointer types) and a Common Mistakes table with specific fixes covering the common cases.	5 / 5
Workflow Clarity	No fragile multi-step build/deploy pipeline requiring validation checkpoints, so the simple-skill guidance applies; the Best Practices Summary and Common Mistakes table give an explicit decision->fix feedback pattern, though it is advisory rather than a sequenced validate-retry loop.	4 / 5
Progressive Disclosure	SKILL.md is a well-signaled overview with one-level-deep references to five real bundle files (slice-internals, map-internals, containers, generics, pointers), each linked inline at the relevant section with a short description of what it contains; no nested reference chains.	5 / 5
	Total	18 / 20 Passed

Description

91%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 dense, concrete description that clearly states both what the skill covers and when to invoke it, with specific Go data-structure terminology as natural triggers. It is comprehensive and largely self-disambiguating against sibling skills.

Suggestions

Add a couple of lay synonyms (e.g. 'Go generics', 'Go collections') to the trigger clause to catch users who phrase the need less technically.

The first sentence is a long enumeration; consider splitting the capability list from the 'Use when' clause more sharply so the trigger remains scannable.

Dimension	Reasoning	Score
Specificity	Lists numerous concrete capabilities — slices (internals, capacity growth, preallocation), maps (hash buckets), container/list/heap/ring, strings.Builder vs bytes.Buffer, unsafe/weak pointers — with comprehensive coverage of the domain.	5 / 5
Completeness	Explicitly answers both what (enumerates slices/maps/arrays/containers/pointers with their subtopics) and when (a clear 'Use when...' clause listing five concrete triggering situations).	5 / 5
Trigger Term Quality	Strong natural triggers like 'choosing or optimizing Go data structures', 'implementing generic containers', 'using container/ packages', and 'questioning slice/map internals'; missing some common synonyms a user might say (e.g. 'generics', 'Go collections').	4 / 5
Distinctiveness Conflict Risk	Carves a clear niche (Go data-structure internals and selection) and the trigger situations are specific enough to avoid overlapping with the sibling safety/concurrency/performance skills it itself cross-references.	5 / 5
	Total	19 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-data-structures/SKILL.md
Commit: 30cdf15

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