ClaudeSuperPower

catalyst-functions

Skill

Catalyst serverless functions — all 7 types (Basic I/O, Advanced I/O, Event, Cron, Job, Integration, Browser Logic), handler signatures, catalyst-config.json, Security Rules, API Gateway routing, file uploads, busboy, Express middleware, environment variables, function URL, and function testing. Req

Install

git clone https://github.com/catalystbyzoho/claude-plugin.git ~/.claude/skills/catalyst-functions

What is catalyst-functions?

Catalyst serverless functions — all 7 types (Basic I/O, Advanced I/O, Event, Cron, Job, Integration, Browser Logic), handler signatures, catalyst-config.json, Security Rules, API Gateway routing, file uploads, busboy, Express middleware, environment variables, function URL, and function testing. Requires MCP connection — check for the ZohoMCP_* meta-tools before any operation. Trigger on 'write a function', 'catalyst function', 'API Gateway', 'Security Rules', 'function not found', 'function returns 401', 'busboy', 'middleware', 'function URL', 'environment variable in function', 'duplicate CORS headers', 'CORS error in browser', 'Access-Control-Allow-Origin multiple values', 'function URL 404', 'execute suffix', 'function timeout', 'function hangs', or any function type question. Do NOT use for persistent servers, long-running processes, or Docker deployments — use catalyst-appsail instead.

What this can do

Capabilities declared in this component's own frontmatter — not inferred.

Inherit all session tools

Declares no tool restrictions — inherits every session tool

~226 tokens of context used while enabled, before you invoke anything

Documentation

README · ~3 min read

How It Works

  1. Pre-flight (once per session). Confirm the ZohoMCP_* meta-tools (ZohoMCP_getSchema, ZohoMCP_executeTool, ZohoMCP_listTools, ZohoMCP_getFeatures) are present in the tool list — that is the "MCP connected" signal (the CatalystbyZoho_* names never appear as tools). Then complete the canonical readiness gate → ../catalyst-basics/references/preflight.md. It establishes/verifies org/project and scaffolds a missing project via catalyst init --org <orgId> -p <projectId> -ni (never interactive; NI mode links an existing project — if none exists, the user must create one in the console first). Then add functions non-interactively:

    catalyst functions:add --name <name> --type <type> --stack <stack> -ni
    # e.g. catalyst functions:add --name api --type aio --stack node20 -ni
    
  2. Identify the function type — Basic I/O for simple request/response, Advanced I/O for raw HTTP control, Event for trigger-based (triggered by Signals; Event Listeners is deprecated), Job for scheduled (via Job Scheduling — prefer over the legacy Cron type for new projects), Integration for Zoho service events, Browser Logic for Puppeteer.

  3. Load references/functions-basics.md — for the matching handler signature, catalyst-config.json keys, SDK init pattern, and CORS setup.

  4. Load references/functions-advanced.md — for file uploads (busboy), streaming responses, error handling, or chaining functions.

  5. Load references/api-gateway.md — for routing rules, rate limiting, or gateway-level CORS.

Reviews

Log in to leave a review.

No reviews yet — be the first.

Explore related

Other things in this space — across every part of the ecosystem, not just skills.