← Back to Skills Marketplace
tommot2

Workflow Builder Lite

by TommoT2 · GitHub ↗ · v2.0.0 · MIT-0
cross-platform ✓ Security Clean
253
Downloads
0
Stars
1
Active Installs
11
Versions
Install in OpenClaw
/install workflow-builder-lite
Description
Build and execute multi-step workflows with conditional logic. Chain API calls, agent actions, and shell commands into sequences with if/else branching. Pers...
README (SKILL.md)

Workflow Builder Lite v2.0

Install: clawhub install workflow-builder-lite

Plan, save, and execute multi-step workflows with conditional logic.

Language

Detect from user's message language. Default: English.

How It Works

Build — Natural Language

User: "Lag en workflow: hent vær → hvis regn → send meg melding"

Agent:

Workflow: weather-alert
1. ⛅ Hent vær (web_fetch wttr.in/Oslo?format=j1)
2. 🔀 Sjekk: Er det regn?
   → Ja: 3. 📨 Send melding "Ta paraply!"
   → Nei: Stop

Godkjent? (ja/nei/rediger)

Build — Step by Step

"Legg til steg: hent data fra API X" "Legg til betingelse: hvis status != 200, stopp" "Slett steg 2"

Save — Persist to File

When user approves a workflow, save to memory/workflows/{name}.md:

# Workflow: {name}

## Steps
1. [type] description
2. [type] description
   → condition: if X then step 3, else stop

## Created
YYYY-MM-DDTHH:mm+ZZ:ZZ

## Last Run
Never

Execute — With Confirmation

When user says "kjør workflow {name}":

  1. Load workflow from file
  2. Show steps to user
  3. Ask: "Kjør denne workflowen? Y/N"
  4. Execute step by step
  5. Report progress after each step

Step types and how to execute:

Type Execution Method Requires Confirmation
API call web_fetch or agent built-in HTTP No (after workflow approval)
Agent action Built-in tools (message, browser, etc.) No (after workflow approval)
Shell command exec tool Yes — show command, ask each time
File write write tool Yes — show content, ask each time

Shell/file steps require per-step confirmation. Show the exact command/content and wait for Y/N.

Progress

Running: weather-alert
  [✅] Step 1: Hent vær — 15°C, delvis skyet
  [⏭️] Step 2: Sjekk regn — nei
  [⬜] Step 3: (skipped)
Done. No rain today.

Quick Commands

User says Action
"lag workflow" Start building
"vis workflows" List saved workflows
"kjør {name}" Execute saved workflow
"rediger {name}" Modify steps

Guidelines for Agent

  1. Save workflows to filesmemory/workflows/ for reuse
  2. Confirm shell/file steps — always ask before executing
  3. Report after each step — keep user informed
  4. Support conditional branching — if/else based on step results
  5. Auto-create memory/workflows/ if it doesn't exist

What This Skill Does NOT Do

  • Does NOT execute shell commands without user confirmation
  • Does NOT write files without user confirmation
  • Does NOT modify MEMORY.md, HEARTBEAT.md, or other skill files
  • Does NOT require external dependencies

More by TommoT2

  • smart-api-connector — Connect to any REST API without code
  • context-brief — Persistent context survival across sessions
  • cross-check — Auto-detect and verify assumptions

Install the full suite:

clawhub install workflow-builder-lite smart-api-connector context-brief cross-check
Usage Guidance
This skill appears to do what it claims, but take these precautions before installing or using it: - Review any saved workflow file in memory/workflows/ before running — approved workflows can trigger API calls and agent actions without additional confirmation. - Be cautious embedding secrets or credentials in workflow steps or API-call parameters; prefer using secure connectors or prompts. - For workflows that interact with external systems, test in a safe environment first. - If you want extra safety, modify the workflow or agent settings to require confirmation for API/agent-action steps as well (the SKILL.md currently only mandates confirmation for shell/file steps).
Capability Assessment
Purpose & Capability
The name/description match the SKILL.md: it builds, persists, and executes multi-step workflows including API calls, agent actions, and shell/file steps. The skill declares no environment variables, binaries, or installs — which is reasonable for an instruction-only orchestration tool.
Instruction Scope
Instructions are explicit about saving workflows to memory/workflows/{name}.md, auto-creating that directory, and executing steps. Shell commands and file writes require per-step confirmation, but API calls and agent actions are allowed to run without per-step confirmation once the workflow itself is approved — this is coherent for automation but means approved workflows may trigger external requests or agent-side actions without additional prompts.
Install Mechanism
There is no install spec and no code files; this is the lowest-risk model for static analysis (nothing is written to disk by an installer).
Credentials
The skill declares no required environment variables, credentials, or config paths. That matches the described functionality (it relies on the agent's existing tools rather than external secrets).
Persistence & Privilege
The skill persists workflows under memory/workflows/ and will auto-create that directory. always:false and no global config changes are requested. The SKILL.md asserts it won't modify other skill files, but as an instruction-only skill this is a behavioral guideline rather than an enforceable constraint.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install workflow-builder-lite
  3. After installation, invoke the skill by name or use /workflow-builder-lite
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v2.0.0
Exec steps with confirmation, persistent workflows to files, simplified build/execute flow.
v1.7.0
Removed internal contradictions: clarified no file writes (was showing 'save to file' example), defined exact tool scope (message/browser/web_fetch only), removed duplicate Limitations section, explicit out-of-scope note for file I/O
v1.6.2
Install command now inline for visibility
v1.6.1
Added standalone install command
v1.6.0
Security: Removed cron integration (contradicted session-only claim). Removed agent step examples that implied undeclared integrations. Clarified limitations.
v1.5.0
Security v3: Removed all file persistence. Workflows are session-only. Removed exec steps (shell commands not supported). Removed run logs, workflow JSON files, and storage paths. Pure planning/simulation tool.
v1.4.0
Security: removed USER.md access and memory/ file storage. Workflows are session-only.
v1.3.0
Security: added exec step safety restrictions (dry run first, no secrets, destructive commands blocked, user confirmation required). Added provenance/homepage. Updated description with safety mention.
v1.2.0
Security: replaced npx clawhub@latest with clawhub install.
v1.1.0
Added cross-promotion: recommends smart-api-connector, setup-doctor, tommo-skill-guard.
v1.0.0
Initial release: Build multi-step workflows with conditional logic. Natural language workflow creation, 5 step types (api/agent/exec/condition/delay), branching, dry run, saved workflows, run logging. Free: 3 workflows, 5 steps max. Pro: unlimited + cron + nested workflows.
Metadata
Slug workflow-builder-lite
Version 2.0.0
License MIT-0
All-time Installs 1
Active Installs 1
Total Versions 11
Frequently Asked Questions

What is Workflow Builder Lite?

Build and execute multi-step workflows with conditional logic. Chain API calls, agent actions, and shell commands into sequences with if/else branching. Pers... It is an AI Agent Skill for Claude Code / OpenClaw, with 253 downloads so far.

How do I install Workflow Builder Lite?

Run "/install workflow-builder-lite" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Workflow Builder Lite free?

Yes, Workflow Builder Lite is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Workflow Builder Lite support?

Workflow Builder Lite is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Workflow Builder Lite?

It is built and maintained by TommoT2 (@tommot2); the current version is v2.0.0.

💬 Comments