catalyst-cache

该 Skill 面向 Zoho Catalyst 内存键值存储 Cache，说明如何获取 Segment ID、加载 references/cache-basics.md 查 SDK 操作，并强调值只能是字符串、TTL 以小时计且上限 48 小时、update 省略过期参数会重置为 48 小时、delete 只把值置为 null 等注意事项。

catalystbyzoho

热度 0.00

最近更新 2026-10-18 16:49:46

分类：开发依赖：读写文件 / MCP 服务 / 第三方 API应用场景：API 集成 / 调试排错

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add catalystbyzoho/agent-skills/catalyst-cache

Metadata

name: catalyst-cache
description: 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'.
metadata: {"version":"2.0.1"}

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