[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79ATZ0030ZBFPXQ2W5ZAFTY":3,"skill-same:01M79ATZ0030ZBFPXQ2W5ZAFTY":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":38,"commitSha":39,"skillDirectory":40,"forksCount":41,"repositoryHtmlUrl":42,"repositoryHomepageUrl":6,"ownerHtmlUrl":43,"ownerBlogUrl":44,"ownerDescription":6,"updatedAt":45,"install":46,"resources":58},"01M79ATZ0030ZBFPXQ2W5ZAFTY","golang-samber-hot",null,"In-memory caching in Golang using samber\u002Fhot — 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\u002Fhot, when the codebase imports github.com\u002Fsamber\u002Fhot, or when the project repeatedly loads the same medium-to-low cardinality resources at high frequency and needs to reduce latency or backend pressure.","CCH-HQ\u002Fcchp-automation","CCH-HQ","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F253065381?v=4","01M79AG9QPRTJEVTCT1ZS7TM9J","CCH HQ","01M79AG9RNM4TAB3PJQH71X62P",2,"MIT","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-samber-hot\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: golang-samber-hot\ndescription: \"In-memory caching in Golang using samber\u002Fhot — 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\u002Fhot, when the codebase imports github.com\u002Fsamber\u002Fhot, or when the project repeatedly loads the same medium-to-low cardinality resources at high frequency and needs to reduce latency or backend pressure.\"\nuser-invocable: true\nlicense: MIT\ncompatibility: Designed for Claude Code or similar AI coding agents, and for projects using Golang.\nmetadata:\n  author: samber\n  version: \"1.0.6\"\n  openclaw:\n    emoji: \"🔥\"\n    homepage: https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang\n    requires:\n      bins:\n        - go\n    install: []\n    skill-library-version: \"0.13.0\"\nallowed-tools: Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch mcp__context7__resolve-library-id mcp__context7__query-docs AskUserQuestion Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__*\n---\n\n**Persona:** You are a Go engineer who treats caching as a system design decision. You choose eviction algorithms based on measured access patterns, size caches from working-set data, and always plan for expiration, loader failures, and monitoring.\n\n# Using samber\u002Fhot for In-Memory Caching in Go\n\nGeneric, type-safe in-memory caching library for Go 1.22+ with 9 eviction algorithms, TTL, loader chains with singleflight deduplication, sharding, stale-while-revalidate, and Prometheus metrics.\n\n**Official Resources:**\n\n- [pkg.go.dev\u002Fgithub.com\u002Fsamber\u002Fhot](https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fsamber\u002Fhot)\n- [github.com\u002Fsamber\u002Fhot](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fhot)\n\nThis skill is not exhaustive. Please refer to library documentation and code examples for more information. For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`) — prefer it over Context7 for Go package facts. To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`). Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\n```bash\ngo get -u github.com\u002Fsamber\u002Fhot\n```\n\n## Algorithm Selection\n\nPick based on your access pattern — the wrong algorithm wastes memory or tanks hit rate.\n\n| Algorithm | Constant | Best for | Avoid when |\n| --- | --- | --- | --- |\n| **W-TinyLFU** | `hot.WTinyLFU` | General-purpose, mixed workloads (default) | You need simplicity for debugging |\n| **LRU** | `hot.LRU` | Recency-dominated (sessions, recent queries) | Frequency matters (scan pollution evicts hot items) |\n| **LFU** | `hot.LFU` | Frequency-dominated (popular products, DNS) | Access patterns shift (stale popular items never evict) |\n| **TinyLFU** | `hot.TinyLFU` | Read-heavy with frequency bias | Write-heavy (admission filter overhead) |\n| **S3FIFO** | `hot.S3FIFO` | High throughput, scan-resistant | Small caches (\u003C1000 items) |\n| **ARC** | `hot.ARC` | Self-tuning, unknown patterns | Memory-constrained (2x tracking overhead) |\n| **TwoQueue** | `hot.TwoQueue` | Mixed with hot\u002Fcold split | Tuning complexity is unacceptable |\n| **SIEVE** | `hot.SIEVE` | Simple scan-resistant LRU alternative | Highly skewed access patterns |\n| **FIFO** | `hot.FIFO` | Simple, predictable eviction order | Hit rate matters (no frequency\u002Frecency awareness) |\n\n**Decision shortcut:** Start with `hot.WTinyLFU`. Switch only when profiling shows the miss rate is too high for your SLO.\n\nFor detailed algorithm comparison, benchmarks, and a decision tree, see [Algorithm Guide](.\u002Freferences\u002Falgorithm-guide.md).\n\n## Core Usage\n\n### Basic Cache with TTL\n\n```go\nimport \"github.com\u002Fsamber\u002Fhot\"\n\ncache := hot.NewHotCache[string, *User](hot.WTinyLFU, 10_000).\n    WithTTL(5 * time.Minute).\n    WithJanitor().\n    Build()\ndefer cache.StopJanitor()\n\ncache.Set(\"user:123\", user)\ncache.SetWithTTL(\"session:abc\", session, 30*time.Minute)\n\nvalue, found, err := cache.Get(\"user:123\")\n```\n\n### Loader Pattern (Read-Through)\n\nLoaders fetch missing keys automatically with singleflight deduplication — concurrent `Get()` calls for the same missing key share one loader invocation:\n\n```go\ncache := hot.NewHotCache[int, *User](hot.WTinyLFU, 10_000).\n    WithTTL(5 * time.Minute).\n    WithLoaders(func(ids []int) (map[int]*User, error) {\n        return db.GetUsersByIDs(ctx, ids) \u002F\u002F batch query\n    }).\n    WithJanitor().\n    Build()\ndefer cache.StopJanitor()\n\nuser, found, err := cache.Get(123) \u002F\u002F triggers loader on miss\n```\n\n## Capacity Sizing\n\nBefore setting the cache capacity, estimate how many items fit in the memory budget:\n\n1. **Estimate single-item size** — estimate size of the struct, add the size of heap-allocated fields (slices, maps, strings). Include the key size. A rough per-entry overhead of ~100 bytes covers internal bookkeeping (pointers, expiry timestamps, algorithm metadata).\n2. **Ask the developer** how much memory is dedicated to this cache in production (e.g., 256 MB, 1 GB). This depends on the service's total memory and what else shares the process.\n3. **Compute capacity** — `capacity = memoryBudget \u002F estimatedItemSize`. Round down to leave headroom.\n\n```\nExample: *User struct ~500 bytes + string key ~50 bytes + overhead ~100 bytes = ~650 bytes\u002Fentry\n         256 MB budget → 256_000_000 \u002F 650 ≈ 393,000 items\n```\n\nIf the item size is unknown, ask the developer to measure it with a unit test that allocates N items and checks `runtime.ReadMemStats`. Guessing capacity without measuring leads to OOM or wasted memory.\n\n## Common Mistakes\n\n1. **Forgetting `WithJanitor()`** — without it, expired entries stay in memory until the algorithm evicts them. Always chain `.WithJanitor()` in the builder and `defer cache.StopJanitor()`.\n2. **Calling `SetMissing()` without missing cache config** — panics at runtime. Enable `WithMissingCache(algorithm, capacity)` or `WithMissingSharedCache()` in the builder first.\n3. **`WithoutLocking()` + `WithJanitor()`** — mutually exclusive, panics. `WithoutLocking()` is only safe for single-goroutine access without background cleanup.\n4. **Oversized cache** — a cache holding everything is a map with overhead. Size to your working set (typically 10-20% of total data). Monitor hit rate to validate.\n5. **Ignoring loader errors** — `Get()` returns `(zero, false, err)` on loader failure. Always check `err`, not just `found`.\n\n## Best Practices\n\n1. Always set TTL — unbounded caches serve stale data indefinitely because there is no signal to refresh\n2. Use `WithJitter(lambda, upperBound)` to spread expirations — without jitter, items created together expire together, causing thundering herd on the loader\n3. Monitor with `WithPrometheusMetrics(cacheName)` — hit rate below 80% usually means the cache is undersized or the algorithm is wrong for the workload\n4. Use `WithCopyOnRead(fn)` \u002F `WithCopyOnWrite(fn)` for mutable values — without copies, callers mutate cached objects and corrupt shared state\n\nFor advanced patterns (revalidation, sharding, missing cache, monitoring setup), see [Production Patterns](.\u002Freferences\u002Fproduction-patterns.md).\n\nFor the complete API surface, see [API Reference](.\u002Freferences\u002Fapi-reference.md).\n\nIf you encounter a bug or unexpected behavior in samber\u002Fhot, open an issue at \u003Chttps:\u002F\u002Fgithub.com\u002Fsamber\u002Fhot\u002Fissues>.\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-performance` skill for general caching strategy and when to use in-memory cache vs Redis vs CDN\n- → See `samber\u002Fcc-skills-golang@golang-observability` skill for Prometheus metrics integration and monitoring\n- → See `samber\u002Fcc-skills-golang@golang-database` skill for database query patterns that pair with cache loaders\n- → See `samber\u002Fcc-skills@promql-cli` skill for querying Prometheus cache metrics via CLI\n","**Persona:** You are a Go engineer who treats caching as a system design decision. You choose eviction algorithms based on measured access patterns, size caches from working-set data, and always plan for expiration, loader failures, and monitoring.\n\n# Using samber\u002Fhot for In-Memory Caching in Go\n\nGeneric, type-safe in-memory caching library for Go 1.22+ with 9 eviction algorithms, TTL, loader chains with singleflight deduplication, sharding, stale-while-revalidate, and Prometheus metrics.\n\n**Official Resources:**\n\n- [pkg.go.dev\u002Fgithub.com\u002Fsamber\u002Fhot](https:\u002F\u002Fpkg.go.dev\u002Fgithub.com\u002Fsamber\u002Fhot)\n- [github.com\u002Fsamber\u002Fhot](https:\u002F\u002Fgithub.com\u002Fsamber\u002Fhot)\n\nThis skill is not exhaustive. Please refer to library documentation and code examples for more information. For Go package docs, symbols, versions, importers, and known vulnerabilities, → See `samber\u002Fcc-skills-golang@golang-pkg-go-dev` skill (`godig`) — prefer it over Context7 for Go package facts. To navigate this library's usage in your own code (definitions, call sites, diagnostics), → See `samber\u002Fcc-skills-golang@golang-gopls` skill (`gopls`). Context7 remains a fallback for docs not indexed on pkg.go.dev.\n\n```bash\ngo get -u github.com\u002Fsamber\u002Fhot\n```\n\n## Algorithm Selection\n\nPick based on your access pattern — the wrong algorithm wastes memory or tanks hit rate.\n\n| Algorithm | Constant | Best for | Avoid when |\n| --- | --- | --- | --- |\n| **W-TinyLFU** | `hot.WTinyLFU` | General-purpose, mixed workloads (default) | You need simplicity for debugging |\n| **LRU** | `hot.LRU` | Recency-dominated (sessions, recent queries) | Frequency matters (scan pollution evicts hot items) |\n| **LFU** | `hot.LFU` | Frequency-dominated (popular products, DNS) | Access patterns shift (stale popular items never evict) |\n| **TinyLFU** | `hot.TinyLFU` | Read-heavy with frequency bias | Write-heavy (admission filter overhead) |\n| **S3FIFO** | `hot.S3FIFO` | High throughput, scan-resistant | Small caches (\u003C1000 items) |\n| **ARC** | `hot.ARC` | Self-tuning, unknown patterns | Memory-constrained (2x tracking overhead) |\n| **TwoQueue** | `hot.TwoQueue` | Mixed with hot\u002Fcold split | Tuning complexity is unacceptable |\n| **SIEVE** | `hot.SIEVE` | Simple scan-resistant LRU alternative | Highly skewed access patterns |\n| **FIFO** | `hot.FIFO` | Simple, predictable eviction order | Hit rate matters (no frequency\u002Frecency awareness) |\n\n**Decision shortcut:** Start with `hot.WTinyLFU`. Switch only when profiling shows the miss rate is too high for your SLO.\n\nFor detailed algorithm comparison, benchmarks, and a decision tree, see [Algorithm Guide](.\u002Freferences\u002Falgorithm-guide.md).\n\n## Core Usage\n\n### Basic Cache with TTL\n\n```go\nimport \"github.com\u002Fsamber\u002Fhot\"\n\ncache := hot.NewHotCache[string, *User](hot.WTinyLFU, 10_000).\n    WithTTL(5 * time.Minute).\n    WithJanitor().\n    Build()\ndefer cache.StopJanitor()\n\ncache.Set(\"user:123\", user)\ncache.SetWithTTL(\"session:abc\", session, 30*time.Minute)\n\nvalue, found, err := cache.Get(\"user:123\")\n```\n\n### Loader Pattern (Read-Through)\n\nLoaders fetch missing keys automatically with singleflight deduplication — concurrent `Get()` calls for the same missing key share one loader invocation:\n\n```go\ncache := hot.NewHotCache[int, *User](hot.WTinyLFU, 10_000).\n    WithTTL(5 * time.Minute).\n    WithLoaders(func(ids []int) (map[int]*User, error) {\n        return db.GetUsersByIDs(ctx, ids) \u002F\u002F batch query\n    }).\n    WithJanitor().\n    Build()\ndefer cache.StopJanitor()\n\nuser, found, err := cache.Get(123) \u002F\u002F triggers loader on miss\n```\n\n## Capacity Sizing\n\nBefore setting the cache capacity, estimate how many items fit in the memory budget:\n\n1. **Estimate single-item size** — estimate size of the struct, add the size of heap-allocated fields (slices, maps, strings). Include the key size. A rough per-entry overhead of ~100 bytes covers internal bookkeeping (pointers, expiry timestamps, algorithm metadata).\n2. **Ask the developer** how much memory is dedicated to this cache in production (e.g., 256 MB, 1 GB). This depends on the service's total memory and what else shares the process.\n3. **Compute capacity** — `capacity = memoryBudget \u002F estimatedItemSize`. Round down to leave headroom.\n\n```\nExample: *User struct ~500 bytes + string key ~50 bytes + overhead ~100 bytes = ~650 bytes\u002Fentry\n         256 MB budget → 256_000_000 \u002F 650 ≈ 393,000 items\n```\n\nIf the item size is unknown, ask the developer to measure it with a unit test that allocates N items and checks `runtime.ReadMemStats`. Guessing capacity without measuring leads to OOM or wasted memory.\n\n## Common Mistakes\n\n1. **Forgetting `WithJanitor()`** — without it, expired entries stay in memory until the algorithm evicts them. Always chain `.WithJanitor()` in the builder and `defer cache.StopJanitor()`.\n2. **Calling `SetMissing()` without missing cache config** — panics at runtime. Enable `WithMissingCache(algorithm, capacity)` or `WithMissingSharedCache()` in the builder first.\n3. **`WithoutLocking()` + `WithJanitor()`** — mutually exclusive, panics. `WithoutLocking()` is only safe for single-goroutine access without background cleanup.\n4. **Oversized cache** — a cache holding everything is a map with overhead. Size to your working set (typically 10-20% of total data). Monitor hit rate to validate.\n5. **Ignoring loader errors** — `Get()` returns `(zero, false, err)` on loader failure. Always check `err`, not just `found`.\n\n## Best Practices\n\n1. Always set TTL — unbounded caches serve stale data indefinitely because there is no signal to refresh\n2. Use `WithJitter(lambda, upperBound)` to spread expirations — without jitter, items created together expire together, causing thundering herd on the loader\n3. Monitor with `WithPrometheusMetrics(cacheName)` — hit rate below 80% usually means the cache is undersized or the algorithm is wrong for the workload\n4. Use `WithCopyOnRead(fn)` \u002F `WithCopyOnWrite(fn)` for mutable values — without copies, callers mutate cached objects and corrupt shared state\n\nFor advanced patterns (revalidation, sharding, missing cache, monitoring setup), see [Production Patterns](.\u002Freferences\u002Fproduction-patterns.md).\n\nFor the complete API surface, see [API Reference](.\u002Freferences\u002Fapi-reference.md).\n\nIf you encounter a bug or unexpected behavior in samber\u002Fhot, open an issue at \u003Chttps:\u002F\u002Fgithub.com\u002Fsamber\u002Fhot\u002Fissues>.\n\n## Cross-References\n\n- → See `samber\u002Fcc-skills-golang@golang-performance` skill for general caching strategy and when to use in-memory cache vs Redis vs CDN\n- → See `samber\u002Fcc-skills-golang@golang-observability` skill for Prometheus metrics integration and monitoring\n- → See `samber\u002Fcc-skills-golang@golang-database` skill for database query patterns that pair with cache loaders\n- → See `samber\u002Fcc-skills@promql-cli` skill for querying Prometheus cache metrics via CLI\n",{"name":5,"license":15,"metadata":24,"description":7,"allowed-tools":35,"compatibility":36,"user-invocable":37},{"author":25,"version":26,"openclaw":27},"samber","1.0.6",{"emoji":28,"install":29,"homepage":30,"requires":31,"skill-library-version":34},"🔥",[],"https:\u002F\u002Fgithub.com\u002Fsamber\u002Fcc-skills-golang",{"bins":32},[33],"go","0.13.0","Read Edit Write Glob Grep Bash(go:*) Bash(golangci-lint:*) Bash(git:*) Agent WebFetch mcp__context7__resolve-library-id mcp__context7__query-docs AskUserQuestion Bash(godig:*) Bash(gopls:*) LSP mcp__gopls__*","Designed for Claude Code or similar AI coding agents, and for projects using Golang.",true,"main","a93764baed707eda5a68d91e19e5719368e6335e","skills-backup\u002Fskills\u002Fgolang-samber-hot",0,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation","https:\u002F\u002Fgithub.com\u002FCCH-HQ","https:\u002F\u002Fclaude-code-hub.app\u002F","2026-11-09 20:50:54",{"source":8,"skillName":5,"commands":47,"prompt":57,"zipAvailable":37},[48,51,54],{"tool":49,"command":50},"npx","npx skills add CCH-HQ\u002Fcchp-automation --skill golang-samber-hot",{"tool":52,"command":53},"bunx","bunx skills add CCH-HQ\u002Fcchp-automation --skill golang-samber-hot",{"tool":55,"command":56},"pnpm","pnpm dlx skills add CCH-HQ\u002Fcchp-automation --skill golang-samber-hot","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-samber-hot\u002FSKILL.md",[59,65,69,73],{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"evals\u002Fevals.json","REFERENCE","参考文档",16674,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-samber-hot\u002Fevals\u002Fevals.json",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"references\u002Falgorithm-guide.md",8727,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-samber-hot\u002Freferences\u002Falgorithm-guide.md",{"path":70,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":71,"sourceHtmlUrl":72},"references\u002Fapi-reference.md",6350,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-samber-hot\u002Freferences\u002Fapi-reference.md",{"path":74,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Fproduction-patterns.md",6878,"https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fgolang-samber-hot\u002Freferences\u002Fproduction-patterns.md",[78,85,92,99,106,113],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M79B44RKSB6Z0GENGYFCCZYA","writing-skills","Use when creating new skills, editing existing skills, or verifying skills work before deployment","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwriting-skills\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M79B410BHDSNHZ7MKAYXWJHS","writing-plans","Use when you have a spec or requirements for a multi-step task, before touching code","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwriting-plans\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M79B3XK29MCD5HGD50YGYXQZ","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M79B3TFQEXXM2KK5V44H64DV","wayfinder","Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M79B3Q3WTMJDM6NNGG1X4NYK","verification-before-completion","Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fverification-before-completion\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":19},"01M79B3GW8YCKT7W489HKWFMNC","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","https:\u002F\u002Fgithub.com\u002FCCH-HQ\u002Fcchp-automation\u002Fblob\u002Fmain\u002Fskills-backup\u002Fskills\u002Fvercel-react-best-practices\u002FSKILL.md",[],[]]