golang-samber-hot
Build Reliable Go Caches with samber/hot
Repeated backend reads can increase latency and overload services. This skill guides samber/hot cache design with workload-based eviction, expiration, loaders, concurrency controls, and monitoring.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "golang-samber-hot" from https://skillstore.io/skills/samber-golang-samber-hot.md and its manifest at https://skillstore.io/api/skills/samber-golang-samber-hot/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "golang-samber-hot". Which policy fits stable, heavily skewed DNS cache lookups?
Expected outcome:
- LFU is a candidate because a small, consistently popular key set dominates requests.
- Changing popularity can leave outdated items favored, so compare alternatives if the workload shifts.
- Benchmark representative lookups and choose TTL independently from eviction policy.
Using "golang-samber-hot". Can I combine disabled locking with background TTL cleanup?
Expected outcome:
- The skill identifies disabled locking and janitor cleanup as incompatible options that can panic.
- Keep locking when using background cleanup or concurrent access.
- For a single-goroutine design, omit the janitor and plan explicit cleanup.
Using "golang-samber-hot". How should I monitor a samber/hot cache?
Expected outcome:
- Enable the library's Prometheus metrics and register the cache as a collector.
- Track hit ratio, eviction rate, and cache occupancy relative to capacity.
- Set alert thresholds from workload requirements and investigate changes before increasing memory.
Security Audit
SafeAll 43 static findings are false positives involving Markdown formatting, cache terminology, documentation links, or normal development tool declarations. The installation example uses standard Go dependency tooling, not shell substitution. No evidence found of credential theft, exfiltration, destructive behavior, or prompt injection in the reviewed files.
Risk Factors
โ๏ธ External commands (33)
๐ Network access (4)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/samber-golang-samber-hot/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/samber-golang-samber-hot?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/samber-golang-samber-hot?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/samber-golang-samber-hot/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/samber-golang-samber-hot.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA ยท BibTeX ยท CFF)
APA citation
samber. (2026). golang-samber-hot security audit report (audit version 1) [Author version 1.1.2]. Skillstore. https://skillstore.io/skills/samber-golang-samber-hot/audits/1BibTeX citation
@techreport{samber-samber-golang-samber-hot-2026,
author = {samber},
title = {golang-samber-hot security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/samber-golang-samber-hot/audits/1},
note = {Author version 1.1.2}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "golang-samber-hot security audit report (audit version 1)"
version: "1.1.2"
type: report
authors:
- name: "samber"
date-released: "2026-10-18"
url: "https://skillstore.io/skills/samber-golang-samber-hot/audits/1"
identifiers:
- type: other
value: "skillstore:samber-golang-samber-hot:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Reduce Repeated Profile Queries
Design a typed user cache with expiration, batch loaders, error handling, and negative caching for missing profiles.
Investigate Cache Contention
Review measured mutex contention, evaluate sharding, and choose monitoring signals before changing capacity or eviction policy.
Review Cache Integration Safety
Check janitor cleanup, incompatible builder options, stale-data policies, and shared mutable values during code review.
Try These Prompts
Using samber/hot, create a string-to-byte-slice cache with 10,000 entries and a five-minute TTL. Include janitor cleanup and handle retrieval errors.
Compare samber/hot eviction policies for [access pattern]. Use [memory budget] and [estimated entry size] to estimate capacity. Explain what measurements would validate the choice.
Design a samber/hot cache for [entity] with a batch database loader and negative caching. Address concurrent misses, expiration jitter, loader errors, and janitor cleanup.
Review [cache implementation] against [freshness requirements], [concurrency profile], and [memory budget]. Evaluate sharding, revalidation, mutable values, Prometheus metrics, and shutdown. Propose focused validation tests.
Best Practices
- Measure access patterns and entry sizes before selecting an eviction policy or capacity.
- Set expiration deliberately, handle loader errors, and stop janitor goroutines during shutdown.
- Validate concurrency and mutable-value handling with tests, then monitor hit ratio and eviction behavior.
Avoid
- Disable locking for concurrent workloads or combine disabled locking with a background janitor.
- Call negative-cache methods before enabling missing-key cache configuration.
- Ignore loader errors or let callers mutate shared cached objects without suitable copying.
Frequently Asked Questions
What does this skill provide?
Which AI tools are listed as supported?
Does this replace Redis or provide persistence?
Which eviction algorithm should I start with?
How does it address simultaneous cache misses?
Does it automatically install dependencies or configure monitoring?
Developer Details
Author
samberLicense
MIT
Author version
v1.1.2
Skillstore revision
r1
Ref
6093890d49a212c14c65676829e1af5ee07ab3dc
Maintenance freshness
10/18/2026
Usage
0 downloads ยท 0 views
File structure
๐ evals/
๐ evals.json
๐ references/
๐ algorithm-guide.md
๐ api-reference.md
๐ SKILL.md