Agent Skills › oomol-lab/open-flow › open-flow

open-flow

GitHub

用于创建、检查、编辑、运行和发布持久化 Open Flow 工作流，以及将 n8n 工作流转换为 Open Flow。专注于工作流操作而非底层实现修改。

packages/open-flow/skills/open-flow/SKILL.md oomol-lab/open-flow

Trigger Scenarios

创建工作流检查工作流状态编辑工作流节点运行工作流测试发布工作流到生产环境将 n8n 工作流转换为 Open Flow

Install

npx skills add oomol-lab/open-flow --skill open-flow -g -y

More Options

Non-standard path

npx skills add https://github.com/oomol-lab/open-flow/tree/main/packages/open-flow/skills/open-flow -g -y

Use without installing

npx skills use oomol-lab/open-flow@open-flow

指定 Agent (Claude Code)

npx skills add oomol-lab/open-flow --skill open-flow -a claude-code -g -y

安装 repo 全部 skill

npx skills add oomol-lab/open-flow --all -g -y

预览 repo 内 skill

npx skills add oomol-lab/open-flow --list

SKILL.md

Frontmatter

{
    "name": "open-flow",
    "description": "Create, inspect, edit, check, run, and publish persistent Open Flow workflows through an existing Server, or assess and convert n8n workflows to Open Flow. Use for workflow operations, not changes to the Open Flow implementation."
}

Open Flow

Use  to operate the selected deployment. Consult the references relevant to the task:

Flow capabilities and examples: inspect, edit, connect, validate, run and publish; import/export workflow templates; online entries and Flow enable/disable; concurrency and Run diagnostics.
n8n conversion: represent collections, branches, provider operations and state while preserving source behavior.

Keep generated Flow and node names short enough to scan on the canvas. Aim for 2–4 English words or 4–8 Chinese characters, using the user's language unless the workflow has an established naming language. Name a Flow by its main purpose and a node by its action and object, such as AI Trend Digest, Fetch trends, Verify sources, or 发布文章. Keep only qualifiers needed to distinguish similar nodes. Put detailed behavior in descriptions; avoid sentences, repeated workflow context, and obscure abbreviations. Preserve names explicitly supplied by the user, and do not rename unrelated existing nodes.

Run commands from this repository's root. The development CLI connects to the existing local Server by default, using OPEN_FLOW_PORT (default 3001) and OPEN_FLOW_TOKEN, or the token generated by bun run dev. It reads the root .env. If the local Server has not been started, report that prerequisite. Do not start or reconfigure a Server merely to perform a Flow operation.

To select another Server, the user must provide both OPEN_FLOW_URL and OPEN_FLOW_TOKEN in the environment. Never read, print, or copy credential files into prompts or command arguments. Connector and LLM configuration stay on the Server; do not duplicate them in the CLI.

Keep the requested boundary: editing a Draft does not authorize a Run, publication, or enabling automatic execution. Inspecting an entry does not by itself authorize invoking it. For edits, report the Flow and Revision, verification result, and unresolved configuration. For a publication, report the Publication and available online entries. For a query, report the observed online state.