Agent Skills

catalyst-signals

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 program

Install

npx skills add https://github.com/catalystbyzoho/agent-skills --skill catalyst-signals
SKILL.md

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: One-Time (immediate), Scheduled (time-based), or Batching (count/size aggregation)
  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", "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

Related skills

entra-app-registrationmicrosoft606KGuides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.azure-messagingmicrosoft595KTroubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, servicentra-agent-idmicrosoft328KProvision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmi_path, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmi_path token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registsupabasesupabase298KUse when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, declarative schemas, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector); deb

Search skills and MCP servers

Fuzzy search across 23,137 skills and servers