From edgedelta-workflows
Generate, validate, and customize EdgeDelta AI workflow configurations with 8 node types, 29 action types, and 5 templates. Use when users need to create, modify, or troubleshoot EdgeDelta workflows.
How this skill is triggered — by the user, by Claude, or both
Slash command
/edgedelta-workflows:edgedelta-workflowsThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Generate complete EdgeDelta workflow configurations — event-driven AI automation pipelines that connect monitors, external events, and schedules to AI teammates. Workflows are JSON DAGs with typed nodes (start, teammate, task, action, if-else, transform, set-state, note) executed on a distributed async engine.
Generate complete EdgeDelta workflow configurations — event-driven AI automation pipelines that connect monitors, external events, and schedules to AI teammates. Workflows are JSON DAGs with typed nodes (start, teammate, task, action, if-else, transform, set-state, note) executed on a distributed async engine.
Ask what initiates the workflow:
| Trigger | Start Node Config | When to Use |
|---|---|---|
| Manual / Monitor / Connector | "start": {} | Alert-driven, event-driven, or on-demand |
| Periodic (scheduled) | "start": { "periodicRun": { "schedule": { "cronExpression": "...", "timezone": "..." } } } | Recurring health checks, reports |
Match the user's scenario to a template from references/templates.md:
| Scenario | Template |
|---|---|
| Alert → investigate → notify | Template 1 (Monitor Alert → Email) |
| Scheduled check with branching | Template 2 (Daily Health Check) |
| Full incident response (multi-tool) | Template 3 (Jira + Slack + PagerDuty) |
| Code review automation | Template 4 (PR Review → Slack) |
| Periodic reporting | Template 5 (Capacity → Teams) |
| Custom / none match | Build from scratch using schema |
For each node, consult the appropriate reference:
references/workflow-schema.mdreferences/action-types.md — covers all 29 action types with complete JSON examplesreferences/templates.md — 5 production-tested starting pointsBefore returning the workflow, verify:
start node exists/^[a-zA-Z0-9_-]+$/note) is referenced in at least one linkagentId — built-in options: sre, devops-engineer, cloud-engineer, security-engineer, code-analyzer, issue-coordinatorrequired and match JSON Schema specslackSendMessage for slack-send-message){{{ }}} for JSON/HTML content (no escaping) and double braces {{ }} for plain values| Node | Purpose | Key Fields |
|---|---|---|
start | Entry point | periodicRun? (cron + timezone) |
teammate | AI agent with tools + memory | agentId, stepLevelPrompt, outputFormat, structuredOutput? |
task | Direct LLM call (no tools/memory) | prompt, outputFormat, structuredOutput? |
action | External integration | actionType + type-specific config (see action-types.md) |
if-else | Conditional branching | branches[] with path + condition (JS expressions) |
transform | Data transformation | steps[] with name + script (sandboxed JS) |
set-state | Persist key-value pairs | assignments[] with key + expression |
note | Documentation only | content |
All Handlebars templates and JS expressions access three variables:
| Variable | Contains | Example |
|---|---|---|
data | Workflow input (trigger payload or transformed data) | {{ data.severity }} |
nodes | Results from prior nodes, keyed by name | {{ nodes.investigate.summary }} |
state | Values set by set-state nodes | {{ state.incidentId }} |
Fork after investigation — one teammate node feeds multiple actions in parallel:
investigate → create-jira
investigate → notify-slack
investigate → page-oncall
Conditional escalation — branch based on teammate output:
investigate → check-severity → (critical) → page-oncall
→ (warning) → send-email
→ (info) → log-only
Data normalization pipeline — clean input before processing:
start → transform (normalize) → set-state (save context) → teammate
Multi-specialist chain — sequential teammate analysis:
sre-investigate → security-review → devops-remediation → notify
When generating a workflow, confirm the user has provided (or ask for):
grep -i "node type\|schema\|field\|required" references/workflow-schema.mdgrep -i "actionType\|slack\|jira\|pagerduty\|teams\|email" references/action-types.mdgrep -i "template\|use case\|trigger" references/templates.mdnpx claudepluginhub edgedelta/claude-code-plugins --plugin edgedelta-workflowsConfigures Rootly workflows for automated incident response, including triggers like incident_created, conditions like severity_gte, and actions like create_slack_channel or create_jira_ticket.
Covers durable execution platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) for production-grade workflow automation.
Guides workflow automation platforms (n8n, Temporal, Inngest, AWS Step Functions) and patterns for durable execution in AI agents and production workflows.