智能体工作流

catalyst-by-zoho

catalystbyzoho/…t-skills

Expert coding assistant for Catalyst by Zoho — Zoho's full-stack cloud platform. Use for any question about Catalyst services, CLI, SDKs, architecture, pricing, or Zoho MCP tool-based infrastructure management.

  • 1089 次安装
  • 70 星标
  • 收录于

安装命令

npx skills add https://github.com/catalystbyzoho/agent-skills --skill catalyst-by-zoho

SKILL.md

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

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