golang-samber-hot
In-memory caching in Golang using samber/hot — eviction algorithms (LRU, LFU, TinyLFU, W-TinyLFU, S3FIFO, ARC, TwoQueue, SIEVE, FIFO), TTL, cache loaders, sharding, stale-while-revalidate, missing key caching, and Prometheus metrics. Apply when using or adopting samber/hot, when the codebase imports github.com/samber/hot, or when the project repeatedly loads the same medium-to-low cardinality resources at high frequency and needs to reduce latency or backend pressure.
67
82%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that is specific, comprehensive, and well-targeted. It names the exact library, language, and a thorough list of features, while providing clear trigger conditions covering both explicit library usage and implicit use-case scenarios. The description is concise yet information-dense with no fluff or vague language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete capabilities: eviction algorithms (with named variants), TTL, cache loaders, sharding, stale-while-revalidate, missing key caching, and Prometheus metrics. Highly detailed and actionable. | 3 / 3 |
Completeness | Clearly answers both 'what' (in-memory caching with specific features) and 'when' with an explicit 'Apply when...' clause covering library adoption, import detection, and use-case triggers like reducing latency or backend pressure. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'caching', 'Golang', 'samber/hot', 'LRU', 'LFU', 'TTL', 'sharding', 'Prometheus metrics', 'reduce latency', 'backend pressure', and the full import path 'github.com/samber/hot'. Excellent coverage of both library-specific and general caching terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific library name 'samber/hot', the Go language context, and the detailed list of eviction algorithms. Unlikely to conflict with generic caching skills or other language-specific caching tools. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A solid, well-structured skill that provides actionable guidance with executable code examples and a useful algorithm selection table. Its main weaknesses are the absence of bundle files that the content references (algorithm guide, production patterns, API reference), some unnecessary verbosity in places (persona, disclaimers), and a lack of explicit end-to-end workflow with validation checkpoints for setting up and verifying a production cache.
Suggestions
Create the referenced bundle files (references/algorithm-guide.md, references/production-patterns.md, references/api-reference.md) to fulfill the progressive disclosure promises made in the content.
Add an explicit end-to-end workflow section with validation checkpoints: e.g., 1) configure cache → 2) verify janitor started → 3) confirm Prometheus metrics emitting → 4) load-test and check hit rate against SLO.
Remove the persona block and the 'this skill is not exhaustive' disclaimer — they consume tokens without adding actionable value for Claude.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but has some unnecessary padding: the persona block, the 'this skill is not exhaustive' disclaimer, the bug reporting line, and the capacity sizing section's conversational tone ('Ask the developer') add tokens without proportional value. The algorithm table and code examples are well-condensed though. | 2 / 3 |
Actionability | Provides fully executable Go code for basic cache setup, TTL, and loader patterns. The algorithm selection table gives concrete constants. Capacity sizing includes a worked numeric example. Common mistakes list specific failure modes (panics, OOM) with exact method names. | 3 / 3 |
Workflow Clarity | The capacity sizing section has a clear 3-step process, and common mistakes serve as implicit validation checkpoints. However, there's no explicit workflow for the most critical multi-step process — setting up a production cache end-to-end with validation steps (e.g., verify janitor is running, confirm metrics are emitting, test loader error paths). The guidance is more reference-style than workflow-oriented. | 2 / 3 |
Progressive Disclosure | References to algorithm-guide.md, production-patterns.md, and api-reference.md are well-signaled and one level deep. However, no bundle files were provided, so these references point to non-existent files, undermining the progressive disclosure structure. The cross-references section to other skills is a nice touch but the core referenced files are missing. | 2 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- samber/cc-skills-golang
- Commit
8c7e016
- 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.