Catalyst By Zoho

Catalyst by Zoho — Skill Index

This is the routing layer. Load the most specific matching skill — do not answer from this file alone.

Philosophy

• Prefer MCP over asking. If CatalystbyZoho_* tools are available, use them. Never ask the user to copy IDs from the console.
• Default to Development. Always target the Development environment unless the user explicitly says "production" or "deploy to prod".
• "Build an app" means Slate + Function by default. When a user says "build an app", "create an app", or "make a simple app" without specifying backend-only, the default output is a Slate frontend + Advanced I/O function backend. Do NOT build only a function and call it an app. If the user's intent is clearly backend-only (e.g. "build an API", "write a function"), skip Slate.
• Prefer Functions over AppSail for simple HTTP. Functions are cheaper (per-invocation billing), simpler to deploy, and require no infrastructure management. Reach for AppSail only when the use case genuinely requires a persistent process, or a custom runtime.
• Show cost before building. For any new infrastructure (functions, AppSail, Stratus buckets), load catalyst-pricing and give a brief estimate before writing code. Most small projects stay within free tier — say so when true.
• Recommend the current service, not the deprecated one. File Store → Stratus. Event Listeners → Signals. Cron → Job Scheduling. Never mention the deprecated name in generated code or config.
• Warn before the region bites. Circuits and Integration Functions do not work in most data centers. Check the user's DC before suggesting them.

How It Works

1. Pre-flight — Check that .catalystrc and catalyst.json exist. If missing, use MCP to get org/project IDs and run catalyst init --org <orgId> -p <projectId> -ni. Never use interactive catalyst init.
2. MCP check — Look for CatalystbyZoho_* tools. If available, use MCP to fetch org/project IDs instead of asking the user.
3. Route — Match the query to the most specific service in the routing table below.
4. Load lazily — Read ONLY the single reference file needed for the current step. Do NOT preload multiple skills upfront. For "build an app" requests: (a) assume Slate frontend + AIO function unless the user says backend-only, (b) sketch the architecture briefly and confirm with the user before building, (c) then load one reference file per service as you write each part — catalyst-slate for the frontend, catalyst-functions for the backend.
5. Cost check — Only load catalyst-pricing if the user specifically asks about cost, or if the plan includes AppSail, Stratus, or other paid-tier services. Skip for basic Functions + DataStore projects (likely free tier).
6. Answer — Provide code examples using the user's platform (Node.js, Python, Java, Web, or Mobile).

Triggers

Use this skill for queries containing: Catalyst, zcatalyst, AppSail, Data Store, ZCQL, Cache, Stratus, Slate, NoSQL, Zia Services, QuickML, API Gateway, Connections, Zoho MCP, CatalystbyZoho, catalyst init, catalyst deploy, catalyst serve, zcatalyst-sdk-node, catalyst-config.json, Catalyst pricing, "build on Zoho's platform", or "deploy to Catalyst". Do NOT use for generic Zoho CRM questions unless Catalyst is the target.

Pre-flight gate (project-mutating tasks only)

Step 1 — MCP check (do this before anything else for infrastructure tasks): Look for CatalystbyZoho_* tools in your tool list.

• If present — use MCP to fetch org/project IDs. Never ask the user to copy IDs from the console. How to call MCP tools correctly:

1. ZohoMCP_getSchema takes query_params, NOT body: `` ZohoMCP_getSchema({ query_params: { tool_name: "CatalystbyZoho_List_All_Projects" } }) ``
2. Always call ZohoMCP_getSchema first for any CatalystbyZoho_* tool — never guess the argument shape. Many tools require path_variables (e.g. project_id) that are invisible without the schema.
3. ZohoMCP_executeTool takes a body with this shape: `` ZohoMCP_executeTool({ body: { tool_name: "CatalystbyZoho_List_All_Functions", arguments: { path_variables: { project_id: "31594000000127002" }, headers: {}, body: {} } }}) ``
4. Tools with no required path variables (e.g. List_All_Organizations, List_All_Projects) can be called with arguments: {}.

• If NOT present and the task creates resources, writes files, deploys, or reads project IDs — HARD STOP. Do NOT write any code or create any files. Tell the user: > "Zoho MCP needs to be connected before I can work with your Catalyst project. Load the catalyst-zoho-mcp skill to set it up — it takes under a minute." Do not proceed until CatalystbyZoho_* tools are visible.

This gate applies only when the task writes Catalyst project files, deploys, reads project/environment IDs, or performs MCP project operations. Skip it for informational questions (pricing, architecture advice, service selection, "what is Catalyst?", install help, SDK usage, or any question that doesn't require an initialized project).

For project-mutating tasks: verify `.catalystrc` and `catalyst.json` exist in the working directory.

• If missing → use MCP tools to get the org ID and project ID, then run: ``bash catalyst init --org <orgId> -p <projectId> -ni ` **Never ask the user to run catalyst init interactively. Never create .catalystrc or catalyst.json yourself — they must be generated by the CLI.** **Note:** NI mode can only link an existing project. If no project exists yet, tell the user to create one in the Catalyst console, then come back — you'll link it with catalyst init -ni`.

Catalyst at a Glance

New to Catalyst? Here's what each service does in one line:

Skill Routing Table