catalyst-job-scheduling
Catalyst Job Scheduling — job pools, immediate/background jobs, and crons (Periodic, OneTime, Calendar, CronExpression) executing Job functions, Webhooks, Circuits, AppSail. Trigger on 'job scheduling', 'job pool', 'jobpoolid', 'submit a job', 'immediate job', 'cron job', 'scheduled function', 'submitJob', 'createCron', 'retryinterval', 'timeofexecution', or errors 'not a job function', 'jobname must contain only alphanumeric'. Replaces deprecated Cron.
- Installs
- 534
- Last 24h
- +12
- Trending rank
- #7861
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/catalystbyzoho/agent-skills --skill catalyst-job-scheduling- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads catalyst-job-scheduling automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Catalyst Job Scheduling
Job Scheduling runs background work in three pieces: job pools (capacity containers), jobs (one execution each, submitted immediately via API/SDK/MCP), and crons (schedulers that submit jobs on a timetable). Every fact in this skill and its references is runtime-verified against a live Catalyst project (Aug 2026) unless marked otherwise.
Prerequisites
Before any operation, load references/job-scheduling-basics.md — it covers the five setup rules that cause most failures: job pool must exist first (no default), targets must be JOB-type functions, all time values in seconds, job_name limits, and function-vs-pool memory constraints.
How It Works
- Identify the target type: Job function (most common), Webhook (any HTTP URL), Circuit, or AppSail. Create/verify a matching-type job pool (Function pools size by
memoryMB; the others by concurrentnumber1–10). - One-off work → submit an immediate job (MCP
CatalystbyZoho_Create_Immediate_Jobor SDKjobScheduling().job().submitJob()). Recurring or delayed work → create a cron (CatalystbyZoho_Create_Cron_Jobor SDKcron().createCron()) choosing Periodic / OneTime / Calendar / CronExpression. Loadreferences/job-scheduling-basics.mdfor exact payloads for both paths. - Write the Job function handler
(jobRequest, context): initialize the SDK withcatalyst.initialize(context, { scope: 'admin' }), read inputs viajobRequest.getAllJobParams()(all values arrive as strings), and ALWAYS end withcontext.closeWithSuccess()orcloseWithFailure()— failure is what triggers the retry chain. - For retries, dynamic scheduling, webhook targets, or monitoring, load
references/job-scheduling-advanced.md— retry semantics (new job records linked byparent_job_id), firing behaviors (Periodic crons fire immediately on create AND update; past-dated OneTime fires instantly; OneTime auto-disables after firing), and observability traps (success/failure counters stay 0; dynamic crons are hidden from list APIs). - Verify by job records, not counters:
CatalystbyZoho_Get_Job_By_Idshowsjob_status(PENDING → RUNNING → SUCCESS | FAILURE),execution_time,dispatch_delay,response_code. Do not trust cronsuccess_count/failure_count— they stay 0.
Security Checklist
- Never log
jobRequest.getJobDetails()orgetJobMetaDetails()wholesale — at runtime theirheaderscontain live credentials (X-ZC-PROJECT-SECRET-KEY,X-ZC-Admin-Cred-Token). Extract only the fields you need. - Webhook-target jobs to your own project's function URLs carry those same credential headers; treat webhook receiver logs as sensitive.
- Job functions run with admin privileges — validate/whitelist anything you accept via
paramsbefore using it in queries. - Never store secrets in job
headers/params—Get_Job_By_Id/Get_Cron_Job_By_Id/List_All_Cronsreturn them in plaintext. Never paste a raw cron/job dump into chat, issues, or logs.
Hallucination Guards
- The SDK enum
CRON_TYPE.CALENDER("Calender") is misspelled and rejected by the server. Use the string'Calendar'. retry_intervalis NOT milliseconds. Seconds, 60–86400.15 * 60 * 1000is rejected.- Immediate jobs and scheduled jobs share the same 15-minute timeout;
context.getMaxExecutionTimeMs()returns the STRING"900000"(parseIntbefore math), whilegetRemainingExecutionTimeMs()returns a number.
Triggers
- "job scheduling", "job pool", "jobpool",
jobpool_id, "create a job pool" - "submit a job", "immediate job", "background job", "run this function as a job",
submitJob,Create_Immediate_Job - "cron", "cron job", "scheduled function", "schedule a function", "recurring job",
createCron,Create_Cron_Job,cron_expression,time_of_execution, "Periodic", "OneTime cron", "Calendar cron" - "retry a job",
number_of_retries,retry_interval,parent_job_id, "dunning", "billing schedule", "trial expiry job" pauseCron,resumeCron,runCron,deleteCron, "pause a cron", "trigger a cron manually",Submit_Cron_Job- Errors: "The given function is not a job function", "job_name must contain only alphanumeric and underscore", "job_name should be within 1-20 char length", "retry interval should be within 60s", "Delete all associated Pre-defined Crons before deleting Job Pool", "memory allocated for the Job Function is higher"
- "webhook job", "call a URL on schedule",
notify_url
References
| File | Load when the query is about… |
|---|---|
references/job-scheduling-basics.md | Core concepts, job pools, immediate jobs, all 4 cron types, MCP tool workflows, Node SDK calls, Job function handler template, CLI setup |
references/job-scheduling-advanced.md | Retry semantics, dynamic (in-code) cron creation, firing/timing behaviors, webhook-target jobs, notify_url, monitoring/observability, security guardrails, pool capacity rules |
FAQ
What does the catalyst-job-scheduling skill do?
Catalyst Job Scheduling — job pools, immediate/background jobs, and crons (Periodic, OneTime, Calendar, CronExpression) executing Job functions, Webhooks, Circuits, AppSail. Trigger on 'job scheduling', 'job pool', 'jobpoolid', 'submit a job', 'immediate job', 'cron job', 'scheduled function', 'submitJob', 'createCron', 'retryinterval', 'timeofexecution', or errors 'not a job function', 'jobname must contain only alphanumeric'. Replaces deprecated Cron.
How do I install catalyst-job-scheduling?
Run npx skills add https://github.com/catalystbyzoho/agent-skills --skill catalyst-job-scheduling in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/catalyst-job-scheduling/ (personal) or .claude/skills/catalyst-job-scheduling/ (project).
Which AI agents can use catalyst-job-scheduling?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is catalyst-job-scheduling safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains catalyst-job-scheduling?
It is published by catalystbyzoho in catalystbyzoho/agent-skills. It has 534 recorded installs.
More from catalystbyzoho/agent-skills
catalyst-by-zoho
catalystbyzoho/agent-skills
Expert coding assistant for Catalyst by Zoho — Zoho's full-stack serverless cloud platform. Use for any question about Catalyst services, CLI, SDKs, architecture, pricing, or Zoho MCP tool-based infrastructure management.
catalyst-basics
catalystbyzoho/agent-skills
Core Catalyst project setup — directory structure, environments, CLI commands, and all Catalyst IDs (Project ID, ZAID, Table ID, Segment ID, Org ID). Trigger on 'start a Catalyst project', 'what is .catalystrc', 'where do I find my Table ID', 'difference between Development and Production', or any Catalyst ID or CLI question.
catalyst-functions
catalystbyzoho/agent-skills
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 CatalystbyZoho 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.
catalyst-appsail
catalystbyzoho/agent-skills
Catalyst AppSail — persistent backend PaaS with managed runtimes (Node.js, Java, Python) and custom Docker containers. Trigger on 'AppSail', 'persistent server', 'Docker on Catalyst', 'XZOHOCATALYSTLISTENPORT', or 'long-running process on Catalyst'. Do NOT use for stateless request/response handlers, event-driven functions, or scheduled jobs — use catalyst-functions instead.
catalyst-sdk
catalystbyzoho/agent-skills
Catalyst SDKs — initialization patterns, service access, and method reference for Node.js, Web (browser), Python, Java, Android, iOS, and Flutter. Trigger on 'SDK', 'zcatalyst-sdk-node', 'Node.js SDK', 'Web SDK', 'Python SDK', 'Java SDK', 'Android SDK', 'iOS SDK', 'Flutter SDK', or 'initialize SDK'.
catalyst-datastore
catalystbyzoho/agent-skills
Catalyst Data Store — relational cloud database with ZCQL, CRUD operations, table permissions, and result pagination. Requires MCP connection — check for CatalystbyZoho tools before any operation. Trigger on 'Data Store', 'ZCQL', 'create table', 'executeZCQLQuery', 'table permissions', 'ROWID', 'boolean column', 'boolean always true', 'truthy string', 'boolean stored as string', or 'DataStore data types'. You MUST load this skill whenever writing code that reads or writes Data Store data — ZCQL result wrapping, boolean-as-string behavior, and App User permissions are non-obvious and cause silent bugs if skipped.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available