duroxide-node-orchestrations Skill

Source

• Creator: microsoft
• Repository: microsoft/duroxide-node
• Skill file: .agents/skills/duroxide-node-orchestrations/SKILL.md

What it does

Writing durable workflows in JavaScript using duroxide-node. Use when creating orchestrations, activities, writing tests, or when the user mentions generator workflows, yield patterns, or duroxide-node development.

Skill instructions

Duroxide-Node Orchestration Development Core Rule: Yield vs Await | Context | Syntax | Why | |---------|--------|-----| | Orchestrations | function + yield | Rust replay engine needs step-by-step control | | Activities | async function + await | Run once, result cached — no replay constraints | | Orchestration tracing | Direct call (no yield) | Fire-and-forget, delegates to Rust | javascript // ✅ Orchestration runtime.registerOrchestration('MyWorkflow', function (ctx, input) { ctx.traceInfo('starting'); // no yield const result = yield ctx.scheduleActivity('Work', input); // yield return result; }); // ✅ Activity runtime.registerActivity('Work', async (ctx, input) = { ctx.traceInfo(processing ${input}); // no yield const data = await fetch(input.url); // await is fine return data; }); Never use async function for orchestrations — async generators break the replay model. Orchestration Context API Scheduling (MUST yield) javascript function (ctx, input) { // Activity const result = yield