server-processing_skill

Overview

This skill documents Kuroco server-side processing patterns focused on Smarty template plugins, webhook triggers, batch jobs, and external integrations. It collects practical plugin references, common Smarty syntax, and best practices for scheduling, error handling, and external API notifications. Use it to implement templated automation, scheduled data flows, and notification pipelines in Kuroco Headless CMS.

How this skill works

The skill inspects and catalogs available Smarty function, modifier, and block plugins and shows examples for variable assignment, loops, conditionals, string/file/API operations, and Vue integration. It also describes how to compose batch jobs and trigger templates that call internal APIs (api_internal), external APIs (api_request), sendmail/slack, write files, and invoke GitHub Actions. Examples include pagination-aware batch loops, pre/post trigger variables, and payload construction for notifications.

When to use it

• When you need to automate periodic jobs (CSV export, sync, reports) using Kuroco batch scheduling.
• When you must run template-based triggers on content create/update/delete or form submission events.
• When calling internal CMS APIs from templates to read/write content or paginate results.
• When integrating external services: Slack, email, GitHub Actions, or third-party APIs.
• When performing file operations (write_file, put_file, read_file) inside templates.

Best practices

• Schedule heavy jobs during low-load windows (night/early morning) and limit high-volume tasks to daily runs.
• Use pagination and chunked loops to avoid timeouts; respect pageInfo and page counts returned by api_internal.
• Implement error handling: check response.errors and notify via slack_send or send_mail, plus log messages.
• Serialize bodies/headers with json_encode for api_request and include proper auth headers for external services.
• Use rcms_auth for template-level permission checks and avoid exposing sensitive constants in templates.

Example use cases

• Daily CSV export: paginate content with api_internal, write files with write_file, upload with put_file, and notify via slack_post_message.
• Form submission trigger: send confirmation email (sendmail) and send Slack notification with inquiry details.
• Content update trigger: on publish, call GitHub Actions via api_request to run a deploy workflow and post status to Slack.
• Bulk synchronization: hourly batch that fetches external API data (api_request), upserts content via api_internal, and logs results.
• File ingestion: read_dir to iterate uploaded files, process contents, and move to storage with put_file.