Catalyst Cache

catalystbyzoho/agent-skills/skills/catalyst-cache

by catalystbyzoho69e5df0514d6091eb7fb399106d1a43298f83b33No license66 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated today

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

Instructions onlySoftware Development

AI-generated overview

Guides use of the Catalyst Cache in-memory key-value store, covering SDK operations, TTL limits and known gotchas.

What it does: This skill explains how to work with Catalyst Cache, an in-memory key-value store with TTL for ephemeral session and temporary data. It walks through getting a segment ID, loading the cache-basics reference for SDK operations, storing string-only values with JSON serialization, and the 48-hour TTL maximum. It also documents two gotchas: segment.update() without an expiry resets TTL to 48 hours, and segment.delete() sets the value to null rather than removing the key.
When to use it: Use it when a task involves Catalyst Cache segments, cache keys or values, TTL settings, session or temporary data, or choosing between cache and Data Store. It is also relevant when debugging cache behavior such as unexpected TTL changes or null values after delete.
Requirements: Requires the Catalyst environment and its cache SDK; an MCP tool for listing cache segments is used if available, otherwise the segment ID comes from the console or .catalystrc. No scripts are shipped; it is instructions plus one reference document.

How It Works

Get Segment ID — Use MCP (CatalystbyZoho_List_Cache_Segments) if available; otherwise retrieve it from the console or .catalystrc.
Load references/cache-basics.md — for SDK operations, TTL limits (48 hr max), and the segment.delete() / segment.update() gotchas.
String values only — All cache values are strings. Always JSON.stringify before put and JSON.parse after get.
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

Source and attribution

Source:catalystbyzoho/agent-skillsinskills/catalyst-cacheat commit69e5df0

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal

Catalyst Cache

How It Works

Triggers

References

Source and attribution

More from catalystbyzoho/agent-skills

Catalyst Zoho Mcp

Catalyst Stratus

Catalyst Signals

Catalyst Pricing

Catalyst Nosql

Catalyst Datastore

More in Software Development

Playground

M5 Onboard

Cardputer Buddy

Web Design Guidelines

Vercel React Native Skills

Vercel React Best Practices