Skip to content

catalyst-cache

Catalyst Cache — in-memory key-value store with TTL for ephemeral session and temporary data. Trigger on 'Cache', 'cache segment', 'cache key', 'TTL', 'segment.put', 'segment.get', or 'temporary data Catalyst'.

1,047
installs
0 up / 0 down, score 0.00
votes
69
repo stars
Updated
less than a month ago
In the catalog since
26 Oct 2026
From
catalystbyzoho/agent-skills
Backend & APIs
Get it through your agent npx skills add catalystbyzoho/agent-skills@catalyst-cache

Skill instructions

Rendered from the published SKILL.md, 17 lines.

How It Works

  1. Get Segment ID — Use MCP (CatalystbyZoho_List_Cache_Segments) if available; otherwise retrieve it from the console or .catalystrc.
  2. Load references/cache-basics.md — for SDK operations, TTL limits (48 hr max), and the segment.delete() / segment.update() gotchas.
  3. String values only — All cache values are strings. Always JSON.stringify before put and JSON.parse after get.
  4. TTL behavior — TTL is in HOURS (max 48), not seconds. segment.update() called WITHOUT an expiry argument silently resets the key's TTL to the 48-hour maximum (a 1-hour key becomes a 48-hour key). segment.delete() does not remove the key — it sets cache_value to null and the key persists; a later getValue() returns null with HTTP 200 and never throws.

Triggers

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".

References

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