Stats
Actions
Tags
From catalyst-by-zoho
In-memory key-value store with TTL for ephemeral session and temporary data on Catalyst. Handles segment operations, string-only values, and TTL gotchas.
How this skill is triggered — by the user, by Claude, or both
Slash command
/catalyst-by-zoho:catalyst-cacheThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
1. **Get Segment ID** — Use MCP (`CatalystbyZoho_List_Cache_Segments`) if available; otherwise retrieve it from the console or `.catalystrc`.
CatalystbyZoho_List_Cache_Segments) if available; otherwise retrieve it from the console or .catalystrc.references/cache-basics.md — for SDK operations, TTL limits (48 hr max), and the segment.delete() / segment.update() gotchas.JSON.stringify before put and JSON.parse after get.segment.update() resets TTL to the new value, not adds to existing. segment.delete() returns null (not an error) if the key is missing.Use this skill for: "Cache", "cache segment", "cache key", "cache value", "TTL", "in-memory store", segment.get, segment.put, segment.delete, "session data", "temporary data Catalyst", "cache vs Data Store", or "48-hour cache".
| Reference | Load when the query is about… |
|---|---|
references/cache-basics.md | SDK operations (get, put, delete, update), Segment ID, 48hr TTL max, string-only values, segment.delete() null gotcha, segment.update() TTL gotcha |
npx claudepluginhub catalystbyzoho/claude-plugin --plugin catalyst-by-zohoIn-memory key-value store with TTL for ephemeral session and temporary data on Catalyst. Handles segment operations, string-only values, and TTL gotchas.
Provides a KV cache (slm_cache_get/set) to avoid re-reading files, query results, or tool outputs within a session. Standard cache-aside pattern with TTL support.
Provisions and configures Render Key Value (Redis-compatible Valkey 8) instances for caching, session storage, and job queues. Use for Redis/Valkey setups, maxmemory policies, ipAllowList, and internal/external connections.