iii-cron
Schedule any registered function on a 6- or 7-field cron expression, with once-only execution across a fleet when backed by the redis adapter. Its whole surface is the `cron` trigger type.
What this skill does
# iii-cron
The `iii-cron` worker schedules a registered function to run on a recurring cron expression. It exposes no callable functions — its entire surface is one trigger type, `cron`, bound via `iii.registerTrigger({ type: 'cron', function_id, config })`. On every firing the engine builds an event payload, optionally evaluates a condition function, acquires a distributed lock through the configured adapter, and invokes the target function. Each firing reports `scheduled_time` vs. `actual_time` so drift and reentrancy are observable from inside the handler.
The schedule grammar is the seven-field cron dialect — `second minute hour day-of-month month day-of-week [year]` — where the year is optional and defaults to `*`. Both six- and seven-field forms work; the leading field is always seconds, so `0 */5 * * * *` fires every 5 minutes at second 0, not every 5 seconds.
Two adapters govern once-only execution: `kv` (default) takes a process-local lock and is single-instance only — on a multi-instance fleet every engine fires the same job (tunables `lock_ttl_ms`, `lock_index`); `redis` takes a distributed lock and is required for once-only firing across a fleet (tunable `redis_url`).
## When to Use
- A function should run periodically without standing up a separate scheduler process or a system crontab entry.
- You need once-only firing across a fleet — nightly cleanup, hourly reports, batch maintenance — paired with the `redis` adapter.
- A scheduled job should be conditionally skipped (holiday calendar, feature flag, weekend pause) via `condition_function_id` without threading the check through the handler.
## Boundaries
- No callable functions — never invoked through a `cron::*` id; everything flows through `iii.registerTrigger`.
- The default `kv` adapter only locks process-local; never rely on it for once-only jobs in a multi-instance deployment — use `redis`.
- Reading the leading field as minutes (the five-field crontab convention) schedules jobs 60x too often; always count fields and remember position 0 is seconds.
- For data-change or stream-change reactions use `iii-state` / `iii-stream`; `iii-cron` fires on the clock only.
## Reactive triggers
Bind a `cron` trigger when a handler should run on a recurring schedule. The handler runs server-side on a tokio task spawned by the engine; with the `redis` adapter it fires once across the fleet per scheduled run.
Reach for it when:
- You need recurring execution (cleanup, reports, maintenance) without an external scheduler.
- You want condition-gated firing: set `condition_function_id` and the engine evaluates it before each run, skipping the handler (and releasing the lock) on a falsy or erroring result.
### How to bind
1. Register a handler: `iii.registerFunction('jobs::cleanup-old-data', handler)`.
2. Register the trigger:
```typescript
iii.registerTrigger({
type: 'cron',
function_id: 'jobs::cleanup-old-data',
config: {
expression: '0 0 2 * * * *', // required. sec min hour dom month dow [year]; daily at 02:00:00.
// condition_function_id is also supported.
},
})
```
`expression` is required and must parse, or registration fails synchronously. Bind one `function_id` to several triggers with distinct ids to drive multiple schedules into one handler — the trigger id arrives as `job_id` in the event. The handler's return value is ignored.
For the firing event payload (`trigger`, `job_id`, `scheduled_time`, `actual_time`), call `iii get function info` on the trigger type or handler function id.
Related in Backend & APIs
jfrog
IncludedInteract with the JFrog Platform via the JFrog CLI and REST/GraphQL APIs. Use this skill when the user wants to manage Artifactory repositories, upload or download artifacts, manage builds, configure permissions, manage users and groups, work with access tokens, configure JFrog CLI servers, search artifacts, manage properties, set up replication, manage JFrog Projects, run security audits or scans, look up CVE details, query exposures scan results from JFrog Advanced Security, manage release bundles and lifecycle operations, aggregate or export platform data, or perform any JFrog Platform administration task. Also use when the user mentions jf, jfrog, artifactory, xray, distribution, evidence, apptrust, onemodel, graphql, workers, mission control, curation, advanced security, exposures, or any JFrog product name.
cupynumeric-migration-readiness
IncludedPre-migration readiness assessor for porting NumPy to cuPyNumeric. Use BEFORE substantial porting work begins when the user asks whether code will scale on GPU, whether they should migrate to cuPyNumeric, which NumPy patterns transfer cleanly, what must be refactored before porting, or mentions pre-port assessment, scaling analysis, or refactor planning. Inspect the user's source code, look up NumPy usage, cross-reference the cuPyNumeric API support manifest, and distinguish distributed-scaling-friendly patterns from blockers such as unsupported APIs, scalar synchronization, host round-trips, Python/object-heavy control flow, shape/data-dependent branching, and in-place mutation hazards. Produce a verdict of READY, LIGHT REFACTOR, SIGNIFICANT REFACTOR, or NOT RECOMMENDED, with concrete refactor pointers.
alibabacloud-data-agent-skill
IncludedInvoke Alibaba Cloud Apsara Data Agent for Analytics via CLI to perform natural language-driven data analysis on enterprise databases. Data Agent for Analytics is an intelligent data analysis agent developed by Alibaba Cloud Database team for enterprise users. It automatically completes requirement analysis, data understanding, analysis insights, and report generation based on natural language descriptions. This tool supports: discovering data resources (instances/databases/tables) managed in DMS, initiating query or deep analysis sessions, real-time progress tracking, and retrieving analysis conclusions and generated reports. Use this Skill when users need to query databases, analyze data trends, generate data reports, ask questions in natural language, or mention "Data Agent", "data analysis", "database query", "SQL analysis", "data insights".
token-optimizer
IncludedReduce OpenClaw token usage and API costs through smart model routing, heartbeat optimization, budget tracking, and native 2026.2.15 features (session pruning, bootstrap size limits, cache TTL alignment). Use when token costs are high, API rate limits are being hit, or hosting multiple agents at scale. The 4 executable scripts (context_optimizer, model_router, heartbeat_optimizer, token_tracker) are local-only — no network requests, no subprocess calls, no system modifications. Reference files (PROVIDERS.md, config-patches.json) document optional multi-provider strategies that require external API keys and network access if you choose to use them. See SECURITY.md for full breakdown.
resend-cli
IncludedUse this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
alibabacloud-odps-maxframe-coding
IncludedUse this skill for MaxFrame SDK development and documentation navigation on Alibaba Cloud MaxCompute (ODPS). Helps answer MaxFrame API, concept, official example, and supported pandas API questions; create data processing programs; read/write MaxCompute tables; debug jobs (remote or local); and build custom DPE runtime images. Trigger when users mention MaxFrame, MaxCompute with MaxFrame, ODPS table processing, DPE runtime, MaxFrame docs/examples, DataFrame/Tensor operations, or GPU runtime setup. Works for both English and Chinese queries about Alibaba Cloud data processing with MaxFrame.