catalyst-signals

Name: catalyst-signals
Author: catalystbyzoho

16installs6forks

How to install catalyst-signals?

catalystbyzoho/agent-skills/catalyst-signals

$npx -y skills add catalystbyzoho/agent-skills --skill catalyst-signals

Installs into the current project.

Summary

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, a

Files · 1

View on GitHub

SKILL.md

1	## Prerequisites
2
3	Before using Signals, activate it once per project in the console:
4	> Console → your project → Signals (left sidebar) → click "Start Exploring"
5
6	Skipping this step prevents access to Publishers, Webhooks, Rules, and Logs. This is a one-time activation per project.
7
8	---
9
10	## How It Works
11
12	1. Console-Only Service — HARD STOP if user expects SDK/API.
13	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.
14	- Publishers, events, webhooks, and rules are created in Console → Signals
15	- Functions and Circuits are created separately in Console → Serverless, then selected as targets in Signals rules
16	- The only code-level interaction is receiving events in target functions/circuits
17
18	2. Understand the flow — Publisher → Event → Rule (with filters/transforms) → Target (Webhook/Function/Circuit)
19	3. Load `references/signals-basics.md` — for publishers (Zoho/Catalyst/Custom), events, rules, targets, dispatch policies, event statuses, and deployment gotchas
20	4. Key concepts:
21	- Publishers emit events when actions occur (3 types: Zoho, Catalyst CloudScale, Custom)
22	- Events are JSON payloads with auto-generated schemas (max 100KB for Zoho, 64KB for Custom)
23	- Rules connect publishers to targets with optional filters and payload transformations
24	- Targets receive events via Webhooks, Functions, or Circuits
25	- Dispatch Policy controls event delivery: One-Time (immediate), Scheduled (time-based), or Batching (count/size aggregation)
26
27	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.
28
29	## Security Checklist
30
31	- Custom publisher REST API rate limit: 500 requests per minute. Exceeding this locks the API URL for 60 seconds.
32	- Environment-specific REST API URLs: Custom event REST API URLs differ between Development and Production — update URLs when deploying.
33	- 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.
34	- 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).
35
36	## Triggers
37
38	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", "one-time dispatch", "scheduled dispatch", "batch dispatch", "event ordering", "retry policy", "TTL", "event status", "Signals logs", "Signals dashboard", "deploy Signals", or "Signals console".
39
40	## References
41
42	\| Reference \| Load when the query is about… \|
43	\|-----------\|-------------------------------\|
44	\| `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 \|

People who liked this also viewed

6 picks

Type

catalyst-signals

16installs6forks

View on GitHub

How to install catalyst-signals?

catalystbyzoho/agent-skills/catalyst-signals

$npx -y skills add catalystbyzoho/agent-skills --skill catalyst-signals

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Prerequisites
2
3	Before using Signals, activate it once per project in the console:
4	> Console → your project → Signals (left sidebar) → click "Start Exploring"
5
6	Skipping this step prevents access to Publishers, Webhooks, Rules, and Logs. This is a one-time activation per project.
7
8	---
9
10	## How It Works
11
12	1. Console-Only Service — HARD STOP if user expects SDK/API.
13	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.
14	- Publishers, events, webhooks, and rules are created in Console → Signals
15	- Functions and Circuits are created separately in Console → Serverless, then selected as targets in Signals rules
16	- The only code-level interaction is receiving events in target functions/circuits
17
18	2. Understand the flow — Publisher → Event → Rule (with filters/transforms) → Target (Webhook/Function/Circuit)
19	3. Load `references/signals-basics.md` — for publishers (Zoho/Catalyst/Custom), events, rules, targets, dispatch policies, event statuses, and deployment gotchas
20	4. Key concepts:
21	- Publishers emit events when actions occur (3 types: Zoho, Catalyst CloudScale, Custom)
22	- Events are JSON payloads with auto-generated schemas (max 100KB for Zoho, 64KB for Custom)
23	- Rules connect publishers to targets with optional filters and payload transformations
24	- Targets receive events via Webhooks, Functions, or Circuits
25	- Dispatch Policy controls event delivery: One-Time (immediate), Scheduled (time-based), or Batching (count/size aggregation)
26
27	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.
28
29	## Security Checklist
30
31	- Custom publisher REST API rate limit: 500 requests per minute. Exceeding this locks the API URL for 60 seconds.
32	- Environment-specific REST API URLs: Custom event REST API URLs differ between Development and Production — update URLs when deploying.
33	- 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.
34	- 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).
35
36	## Triggers
37
38	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", "one-time dispatch", "scheduled dispatch", "batch dispatch", "event ordering", "retry policy", "TTL", "event status", "Signals logs", "Signals dashboard", "deploy Signals", or "Signals console".
39
40	## References
41
42	\| Reference \| Load when the query is about… \|
43	\|-----------\|-------------------------------\|
44	\| `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 \|

People who liked this also viewed

6 picks

Type