Catalyst Cache

by catalystbyzoho9670b79d72feNo license2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 8 weeks ago

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 Catalyst Cache, an in-memory key-value store with TTL for temporary session data.

What it does: This skill explains how to work with Catalyst Cache, an in-memory key-value store for ephemeral session and temporary data. It covers obtaining a segment ID, loading the cache reference, storing values as strings with JSON serialization, and handling TTL behavior. It also documents gotchas such as update resetting TTL to 48 hours and delete returning null for missing keys.
When to use it: Use it for queries about Cache, cache segments or keys, TTL, in-memory storage, session or temporary data in Catalyst, or cache versus Data Store. It is meant for SDK operations like segment.get, segment.put, segment.delete and segment.update.
Requirements: Requires access to the Catalyst environment and, for MCP calls, the CatalystbyZoho MCP tools; a segment ID from MCP, the console, or .catalystrc; and the referenced cache-basics.md file. It ships no scripts.

How It Works

Before any MCP call, establish context once per session via the workspace readiness gate: ../catalyst-basics/references/preflight.md. It resolves and reconciles the org/project so CatalystbyZoho_List_All_Segments targets the right project.

Get Segment ID — Use MCP (CatalystbyZoho_List_All_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 — segment.update(key, value) without an expiry argument resets the TTL to 48 hours (the max), not the key's original TTL. Always pass the TTL explicitly (in hours) to preserve it: segment.update(key, value, ttlHours). segment.delete() returns null (not an error) if the key is missing.

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/claude-plugininskills/catalyst-cacheat commit9670b79

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/claude-plugin

Catalyst Zia

Catalyst Stratus

Catalyst Signals

Catalyst Pricing

Catalyst Nosql

Catalyst Datastore

More in Software Development

Playground

M5 Onboard

Cardputer Buddy

Dev

Dpop Adoption

Web Design Guidelines