Loading...
Loading...
Found 20 Skills
Configures the iii engine via iii-config.yaml — modules, adapters, queue configs, ports, and environment variables. Use when deploying, tuning, or customizing the engine.
Builds reactive real-time backends on the iii engine. Use when building event-driven apps where state changes automatically trigger side effects, clients receive live updates via streams or websockets, or you need a real-time database layer with pub/sub and CRUD endpoints.
Orchestrates durable multi-step workflow pipelines on the iii engine. Use when building order fulfillment, data pipelines, task orchestration, or any sequential process requiring retries, backoff, step tracking, scheduled cleanup, or dead letter queue (DLQ) handling.
Builds trigger-transform-action automation chains on the iii engine. Use when building Zapier/n8n-style automations, webhook-to-action pipelines, or simple event-driven chains where each node is a small registered function chained via named queues.
Rust SDK for the iii engine. Use when building high-performance workers, registering functions, or invoking triggers in Rust.
How agentmemory is built, the iii engine primitives it runs on, its storage model, ports, and the viewer. Use when reasoning about how memory is stored or retrieved end to end, when extending the system, or when answering how agentmemory works under the hood.
Registers a boolean condition function and attaches it to triggers via condition_function_id so handlers only fire when the condition passes. Use when gating triggers on business rules, checking user permissions, validating data before processing, filtering high-value orders, rate-limiting events, or conditionally skipping handlers based on payload content.
Pushes live updates to connected WebSocket clients via streams. Use when building real-time dashboards, live feeds, or collaborative features.
Builds composable, pipeable function chains on the iii engine. Use when building functional pipelines, effect systems, or typed composition layers where each step is a pure function with distributed tracing and retry.
Python SDK for the iii engine. Use when building workers, registering functions, or invoking triggers in Python.
Inspects and redrives jobs that exhausted all retries. Use when handling failed queue jobs, debugging processing errors, or implementing retry strategies.
Registers external HTTP endpoints as iii functions using registerFunction(meta, HttpInvocationConfig). Use when adapting legacy APIs, third-party webhooks, or immutable services into triggerable iii functions, especially when prompts ask for endpoint maps like { path, id } iterated into registerFunction calls.