CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

73

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.

The body is a well-structured, actionable guide with executable examples and properly split references to real bundle files. Its only weakness is minor verbosity in the intro and a guidance-oriented rather than strictly sequenced workflow shape.

Suggestions

Trim the restated library summary ("Generic, type-safe in-memory caching library for Go 1.22+...") since it duplicates the frontmatter description.

Tighten the opening persona/intro paragraphs to reduce tokens that restate what the description already conveys.

DimensionReasoningScore

Conciseness

Mostly efficient with dense, actionable content (algorithm table, code blocks, numbered sizing steps); minor over-explanation such as restating the library summary after the frontmatter and a slightly padded intro paragraph.

4 / 5

Actionability

Provides copy-paste-ready, executable Go code for the basic cache and loader patterns, specific builder methods, install command, and concrete fixes for common mistakes covering the common cases.

5 / 5

Workflow Clarity

The capacity-sizing section is a clear 3-step sequence with a validation checkpoint (measure with a unit test and runtime.ReadMemStats); the rest is guidance rather than a sequenced workflow, so most checkpoints rather than all are explicit.

4 / 5

Progressive Disclosure

SKILL.md is a clear overview with well-signaled, one-level-deep references to real bundle files (algorithm-guide.md, production-patterns.md, api-reference.md, all present in references/), with content appropriately split and easy to navigate.

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.

The description is comprehensive, concrete, and explicitly covers both capabilities and trigger conditions, anchored to a specific library and import path. It is among the strongest possible descriptions for a library-specific skill.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — "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" — with comprehensive coverage of the library's feature surface.

5 / 5

Completeness

Explicitly answers both what ("In-memory caching in Golang using samber/hot — ...") and when ("Apply when using or adopting samber/hot, when the codebase imports ... or when the project repeatedly loads...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including "using or adopting samber/hot", "codebase imports github.com/samber/hot", and "repeatedly loads the same medium-to-low cardinality resources at high frequency" with synonyms like latency and backend pressure.

5 / 5

Distinctiveness Conflict Risk

Clear niche tied to a specific library (samber/hot) with its import path as a trigger, making overlap with other skills minimal.

5 / 5

Total

20

/

20

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.

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_field

'metadata' should map string keys to string values

Warning

relative_links

Relative link issues: 2 missing

Warning

Total

13

/

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.