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.
自分のエージェントでインストール
このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。
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.エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。
エージェントが読めるリソース
AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。
テストする
「golang-samber-hot」を使用しています。 Which policy fits stable, heavily skewed DNS cache lookups?
期待される結果:
- 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.
「golang-samber-hot」を使用しています。 Can I combine disabled locking with background TTL cleanup?
期待される結果:
- 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.
「golang-samber-hot」を使用しています。 How should I monitor a samber/hot cache?
期待される結果:
- 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.
セキュリティ監査
安全All 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.
リスク要因
⚙️ 外部コマンド (33)
🌐 ネットワークアクセス (4)
このレポートを共有・引用
バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。
レポートリンクをコピー
https://skillstore.io/skills/samber-golang-samber-hot/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdownバッジ
[](https://skillstore.io/skills/samber-golang-samber-hot?utm_source=security_passport_badge)HTMLバッジ
<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>埋め込みカード
<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>学術引用 (APA · BibTeX · CFF)
APA形式の引用
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形式の引用
@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 スコア
このスコアの理由 証拠の信頼度: 中作成できるもの
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.
これらのプロンプトを試す
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.
ベストプラクティス
- 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.
回避
- 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.
よくある質問
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?
開発者情報
作成者
samberライセンス
MIT
作者バージョン
v1.1.2
Skillstore リビジョン
r1
参照
6093890d49a212c14c65676829e1af5ee07ab3dc
メンテナンスの新しさ
2026/10/18
利用状況
0 ダウンロード · 0 閲覧
ファイル構成