Skip to main content
skill CX Codex

catalyst-signals — Claude Code skill: Catalyst event bus

A skill for working with Catalyst Signals: set up publishers, rules, webhooks and dispatch policies from the console.

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add catalystbyzoho/agent-skills --skill catalyst-signals -a claude-code
Open on GitHub

What catalyst-signals does

Catalyst Signals is an event-driven platform that lets decoupled applications talk to each other almost instantly. The skill walks through the flow: a publisher emits an event, a rule with filters and transforms routes it to a target — a webhook, function or circuit. Everything is configured in the Catalyst console, and there is no programmatic interface for creating publishers or rules.

Inside sits references/signals-basics.md: publisher types (Zoho, Catalyst CloudScale, Custom), event schemas, the custom event REST API, targets, dispatch policies, retries and statuses. A security checklist covers the 500 requests-per-minute limit on the custom publisher REST API, separate URLs for Development and Production, and payload caps of 100KB for Zoho and 64KB for Custom events.

Activate Signals once per project before anything else: Console → your project → Signals → Start Exploring. Skip that and Publishers, Webhooks, Rules and Logs stay out of reach. One more thing to plan around: rules are locked in production, so all changes happen in Development and get deployed. A deployment holds at most 25 publishers.

What it helps with

  • connect two apps through an event bus without direct calls
  • filter and transform a payload before it reaches the target
  • pick between instant and batch dispatch for an event
  • attach a webhook or function as a rule target
  • trace a missing event through logs and statuses

Example prompts for the agent

  • Help me set up a Catalyst Signals publisher for a new event
  • Explain how a rule with a filter sends an event to a webhook
  • Which dispatch policy fits scheduled batch delivery?

How to install catalyst-signals

1Skills CLI (Vercel)

npx skills add catalystbyzoho/agent-skills --skill catalyst-signals -a claude-code

2Manually: put the files in place

~/.claude/skills/catalyst-signals/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/catalyst-signals/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about catalyst-signals

How do I install catalyst-signals in Claude?

Run npx skills add catalystbyzoho/agent-skills --skill catalyst-signals -a claude-code. The skill lands in ~/.claude/skills/catalyst-signals/SKILL.md.

What does catalyst-signals do?

It helps the agent work with the Catalyst Signals platform: publishers, events, rules, targets and dispatch policies. A basics reference and a security checklist come with it.

Do I need an SDK to use Signals?

No. It is a console-only service: publishers, rules and webhooks are created in the Catalyst UI. Code only matters on the target side, in the functions and circuits that receive events.

Source text

SKILL.md · Apache-2.0
---
name: catalyst-signals
description: "Catalyst Signals — event-driven architecture platform for near-instantaneous communication between decoupled applications. Supports Zoho publishers, Catalyst publishers, custom publishers, webhooks, functions, circuits, event filtering, transformation, batch/scheduled dispatch, and retry policies. Trigger on 'Signals', 'event bus', 'publisher', 'event-driven', 'webhook target', 'dispatch policy', 'event transformation', 'rule filter', or 'event ordering'. Console-only service — no SDK or programmatic API."
metadata:
  version: "2.0.1"
---

## Prerequisites

Before using Signals, activate it once per project in the console:
> Console → your project → **Signals** (left sidebar) → click **"Start Exploring"**

Skipping this step prevents access to Publishers, Webhooks, Rules, and Logs. This is a one-time activation per project.

---

## How It Works

1. **Console-Only Service — HARD STOP if user expects SDK/API.**
   Catalyst Signals is configured entirely through the Catalyst Console — there is NO SDK, REST API, or programmatic interface for creating publishers, rules, or webhooks. All setup is done via the console UI.
   - Publishers, events, webhooks, and rules are created in Console → Signals
   - Functions and Circuits are created separately in Console → Serverless, then selected as targets in Signals rules
   - The only code-level interaction is receiving events in target functions/circuits

2. **Understand the flow** — Publisher → Event → Rule (with filters/transforms) → Target (Webhook/Function/Circuit)
3. **Load `references/signals-basics.md`** — for publishers (Zoho/Catalyst/Custom), events, rules, targets, dispatch policies, event statuses, and deployment gotchas
4. **Key concepts:**
   - **Publishers** emit events when actions occur (3 types: Zoho, Catalyst CloudScale, Custom)
   - **Events** are JSON payloads with auto-generated schemas (max 100KB for Zoho, 64KB for Custom)
   - **Rules** connect publishers to targets with optional filters and payload transformations
   - **Targets** receive events via Webhooks, Functions, or Circuits
   - **Dispatch Policy** controls event delivery: **Instant** (default, immediate) or **Batch** (by count / size / schedule / attribute; TTL fixed at 24h). "One-Time Dispatch" is NOT a policy — it is the no-retry fallback delivery that fires when a Batch's conditions are never met before TTL expiry

5. **Deployment warning** — Rules are locked in production (enable/disable only). All rule changes must be made in Development and deployed. Max 25 publishers per deployment.

## Security Checklist

- **Custom publisher REST API rate limit**: 500 requests per minute. Exceeding this locks the API URL for 60 seconds.
- **Environment-specific REST API URLs**: Custom event REST API URLs differ between Development and Production — update URLs when deploying.
- **Function/Circuit targets inherit their own permissions**: If a function is the target, it runs with whatever scope it was configured with (user or admin). Signals does not override function-level permissions.
- **Event payload size limits**: Zoho publishers max 100KB per event (5MB for multi-event batch). Custom publishers max 64KB per event (256KB for up to 25 events).

## Triggers

Use this skill for: "Signals", "Catalyst event bus", "event-driven architecture", "publisher", "Zoho publisher", "Catalyst publisher", "custom publisher", "event schema", "rule", "event filter", "event transformation", "webhook target", "dispatch policy", "instant dispatch", "one-time dispatch", "scheduled dispatch", "batch dispatch", "event ordering", "retry policy", "TTL", "event status", "Signals logs", "Signals dashboard", "deploy Signals", or "Signals console".

## References

| Reference | Load when the query is about… |
|-----------|-------------------------------|
| `references/signals-basics.md` | Publishers (Zoho/Catalyst/Custom), events and schemas, custom event REST API, rules and filters, targets (webhooks/functions/circuits), dispatch policies (One-Time/Scheduled/Batching), event transformation, retry policies, event ordering, event statuses, logs, dashboard, deployment limits, production restrictions |

© catalystbyzoho · Apache-2.0 · catalystbyzoho/agent-skills

Similar skills

All skills for Backend and APIs →

From the same set15

catalyst-zoho-mcp This skill wires an AI agent to the Zoho Catalyst MCP server so tables, buckets and cache get created from plain chat instead of the console. CX Codex +1 1,000installs catalyst-slate Walks your agent through deploying a frontend to Catalyst Slate: scaffold the app, configure slate-config.toml, ship the build. Handy when React or Next.js needs to live on Catalyst. CX Codex +1 1,000installs catalyst-cache A skill that teaches the agent to use Catalyst Cache: store temporary values in segments, read them back, and respect the TTL. Handy for session data. CX Codex +1 997installs catalyst-stratus A skill for Catalyst Stratus object storage: file uploads, signed URLs, multipart upload. Useful when your project keeps files in Stratus. CX Codex +1 994installs catalyst-nosql A skill that tells the agent how to work with Catalyst NoSQL tables: build items with NoSQLItem, insert, fetch and update records. CX Codex +1 991installs catalyst-zia Wires Zia's pretrained APIs into your agent: OCR, face analytics, object detection, barcode reading and content moderation. Useful when you need image or text extraction without training a model. CX Codex +1 987installs catalyst-pricing Calculates Catalyst pricing, inspects free tier limits, and estimates function execution costs using GB-seconds. CX Codex +1 973installs catalyst-smartbrowz Teaches coding assistants to automate browsers and generate PDFs via Catalyst SmartBrowz. It guides Puppeteer, Playwright, and Selenium workflows in the Catalyst cloud. CX Codex +1 924installs

Project sponsors

Companies that keep this analytics open
Gold sponsor

Impressions, clicks and code copies — open statistics. We keep the numbers public for the same reason NeBlask itself is public. Become a sponsor