Describe your automation task in plain English. Get a complete, ready-to-use OpenClaw workflow β with a SKILL.md file, step-by-step instructions, agent assignment, tool selection, cron schedule and install commands β generated instantly in your browser.
The OpenClaw Workflow Generator converts a plain-English description of an automation task into a complete, ready-to-install OpenClaw workflow. It generates the SKILL.md file (with correct YAML frontmatter, step-by-step instructions, tool usage and output expectations), a workflow JSON (with trigger, agent assignment, model, tools and cron schedule) and the exact shell commands to install and activate the skill β all in your browser, no server involved.
OpenClaw skills are the primary way to give your AI agent persistent, reusable workflows. Instead of repeating long prompt instructions every session, you define a skill once and OpenClaw automatically activates it whenever a user message matches the skill description. [web:45]
Scrape competitor prices daily, compare to yesterday's data, write a diff summary and email it β cron-triggered at 7 AM.
Send /research [topic] in Telegram β the agent searches the web, summarizes findings and replies with a markdown report.
Daily cron reads open GitHub issues, drafts contextual replies based on project docs, saves them for review.
Every morning, gather top news from RSS feeds and web search, summarize into a Telegram-friendly briefing.
Watch a download folder, categorize new files by type, move to organized folders and write a weekly activity report.
Monitor brand mentions, score sentiment, flag urgent items and push a digest to Discord every 4 hours.
A SKILL.md is the definition file for an OpenClaw skill. It sits inside a folder at ~/.openclaw/skills/skill-name/SKILL.md and has two parts: [web:45]
name and description fields. OpenClaw reads only these two fields to decide when the skill is activated. The description must be clear and comprehensive β it is the skill's "activation trigger".The generated SKILL.md follows the official OpenClaw skill design patterns β keeping reference material in separate references/ files, using high/medium/low freedom levels per step, and following the sequential workflow format. [web:45]
mkdir -p ~/.openclaw/skills/your-skill-namecp SKILL.md ~/.openclaw/skills/your-skill-name/openclaw.jsonopenclawname and description fields β OpenClaw reads these to decide when the skill activates. The body contains step-by-step workflow instructions loaded only after the skill triggers. Skills live at ~/.openclaw/skills/ or inside your workspace's skills/ folder.openclaw.json using a cron expression. The best pattern is to combine both: the cron job sends a trigger prompt, and that prompt activates the skill to run the full workflow. This way the workflow is also usable on-demand.~/.openclaw/skills/your-skill-name/ and place the SKILL.md inside it. OpenClaw snapshots eligible skills when a new session starts β so start a fresh session after installing. For cron-triggered workflows, also add the cron entry from the generated install commands to your openclaw.json under the cron section, then run openclaw doctor --fix.