by banmu123
Lightweight AI-native workflow builder for individuals and small teams — describe your idea in natural language, get a runnable workflow on a visual canvas, publish it as an API. One-command Docker self-hosting. Open-source alternative to Dify / n8n.
# Add to your Claude Code skills
git clone https://github.com/banmu123/LoomFlowLast scanned: 9/2/2026
{
"issues": [],
"status": "PASSED",
"scannedAt": "2026-09-02T08:27:48.881Z",
"npmAuditRan": false,
"pipAuditRan": true,
"promptInjectionRan": true
}LoomFlow is an open-source ai agents skill for AI coding assistants such as Claude Code, Codex CLI, and ChatGPT, built by banmu123. Lightweight AI-native workflow builder for individuals and small teams — describe your idea in natural language, get a runnable workflow on a visual canvas, publish it as an API. One-command Docker self-hosting. Open-source alternative to Dify / n8n. It has 209 GitHub stars.
Yes. LoomFlow passed SkillsLLM's automated security scan — a dependency vulnerability audit plus prompt-injection heuristics — with no high-severity issues. You can read the full report in the Security Report section on this page.
Clone the repository with "git clone https://github.com/banmu123/LoomFlow" and add it to your Claude Code skills directory (see the Installation section above).
LoomFlow is primarily written in TypeScript. It is open-source under banmu123 on GitHub, so you can review or fork the full source.
Yes. SkillsLLM lists many other AI Agents skills you can browse and compare side by side. Open the AI Agents category from the badge at the top of this page, or use the Related Skills and comparison links further down to weigh LoomFlow against similar tools.
No comments yet. Be the first to share your thoughts!
⚠️ Third-Party Software Notice
This skill is third-party open-source software developed and hosted independently on GitHub. SkillsLLM is an informational directory and does not control or maintain the underlying repository.
Any security checks, ratings, or warnings displayed by SkillsLLM are automated and limited in scope. They do not constitute a security certification or guarantee that the software is safe, error-free, or free from malicious code, vulnerabilities, compromised dependencies, or prompt-injection risks.
Review the source code, permissions, dependencies, and configuration before installing or running any third-party skill. Use is at your own risk. To the maximum extent permitted by applicable law, SkillsLLM is not liable for losses arising from third-party software.
English | 中文
A lightweight AI workflow builder for individuals and small teams.
An AI-native workflow runtime with built-in evaluation, evolution, and quality gates.
Describe your idea in natural language → generate a runnable workflow → customize it on a visual canvas → publish it as an API.
Everyone should be able to create their own AI automation flows.


| LoomFlow | Dify | n8n | |
|---|---|---|---|
| Getting started | Natural language → runnable workflow, seconds to start | Templates / manual setup, enterprise-grade LLM app platform | Drag nodes manually, AI is just one of many node types |
| Positioning | Lightweight · individuals / small teams · AI-first | Heavy: RAG / knowledge bases / team collaboration / complex deployment | General automation, many node types |
| Deployment | One-command Docker self-hosting (1 GB RAM is enough) | Heavy | Moderate |
| Output | One-click publish as an authenticated HTTP API + share pages | App / workflow centric | Webhook / API |
In one sentence: Dify builds LLM app platforms for teams, n8n does general automation for everyone — LoomFlow turns "one sentence" into a runnable, publishable workflow for individuals and small teams. It doesn't chase comprehensiveness — it pursues a 30-second learning curve and a one-minute deployment.
Scope: LoomFlow is not an AI coach, a personal-growth app, or a coding-practice platform. It stays deliberately narrow — one pipeline: natural language → workflow → canvas → API. Anything that doesn't serve that loop is kept out of the core product.
No drag-and-drop required to start — just describe your process in plain language, and the AI generates an executable workflow directly onto the canvas:
You: "Build me a workflow: input a product name → AI generates selling-point copy → generates a promo video script"
AI: ✅ Generated a 4-node workflow (Start → LLM Copy → LLM Script → End), loaded to canvas
Then fine-tune visually and publish as an API.
Tinyflow canvas editor: drag nodes, connect flows, configure parameters. 12 node types (LLM / HTTP / Code / Template / Search / Excel / Loop / Human Confirm, etc.).
One-click publish a workflow as an HTTP endpoint — one global API Key calls all of your published workflows, with unlimited calls and call logs:
curl -X POST https://your-host/api/publish/{workflowId}/execute \
-H "Authorization: Bearer ffk_xxxxx" \
-H "Content-Type: application/json" \
-d '{"inputs": {"query": "..."}}'
The API Key is auto-generated on first publish and shown only once; when it expires, regenerate it on the API Keys page.
Generate a public link — recipients can view nodes, fill inputs, and run the workflow without signing in. Perfect for demos and delivery.
User management, usage statistics (trends), audit logs, API call logs.
Chinese/English one-click switch (framework supports any language).
App, data, and storage can all be deployed on your own server. Database can be switched to self-hosted PostgreSQL (see Deployment Manual).
NodeRegistry + NodeDefinition — a single source of truth for nodes. Custom nodes can be registered with one entry, with automated validation (executor binding, start/end singleton).
Record why a workflow is designed this way — decisions, problems, solutions, optimizations and usage. AI can summarize design intent, suggest notes from run history, and the canvas AI assistant answers "why did I choose X" from your notes.
Node-level execution trace after each run: per-node status, duration, model, tokens and errors in a timeline — see exactly where a workflow got stuck. The canvas AI assistant reads run history and answers "why did this run fail" with root cause and fix suggestions.
Chat with the canvas: ask about the current workflow, describe a change ("add a summarizer after search"), and the AI outputs a complete workflow JSON you apply to the canvas in one click.
Add any model (DeepSeek / Ark / any OpenAI-compatible endpoint) through the admin UI — no code changes:
Admin → Model Settings → Add Model
id: qwen-vl-max · provider: openai-compatible
base URL: https://... · api key: sk-...
capabilities: [text, vision] → ✅ instantly available everywhere
Workflows continuously improve — without manual intervention. The Evolution Engine automatically detects performance regressions and proposes optimizations:
Evolution Dashboard → Workflow Health (score, trend, bottlenecks)
→ AI Proposals (view diff, approve, reject)
→ Trigger Rules (create cron / metric / event triggers)
→ Regression Detection (baseline vs candidate, 5 metrics, severity policy)
→ Evolution History (timeline, before/after outcome, version diff)
flowchart TB
subgraph Client["Clients"]
Browser["Browser — Next.js frontend<br/>AI Chat / Canvas / Admin / Share"]
External["External systems<br/>curl / API consumers"]
end
subgraph App["LoomFlow App (Next.js)"]
UI["App Router pages<br/>Chat / Workflows / Admin / Share"]
API["API Routes<br/>auth / chat-ai / workflow-history / publish / api-key<br/>search-providers / nodes / schedules"]
Engine["Workflow engine<br/>FlowEngine + NodeRegistry + Executors"]
Registry["Registries<br/>Model Registry · Search Provider Registry"]
end
subgraph Data["Data layer"]
PostgREST["PostgREST"]
PG[("PostgreSQL<br/>conversations / workflow_history / workflow_versions<br/>user_api_keys / ai_models / search_providers<br/>node_definitions / audit_logs ···")]
end
subgraph ExternalSvc["External services"]
LLM["LLM Providers<br/>DeepSeek / any OpenAI-compatible endpoint"]
OSS["Object storage<br/>Aliyun OSS / S3-compatible"]
Search["Search Providers<br/>Tavily / Exa / Google"]
end
Browser --> UI
External -->|"Authorization: Bearer API Key"| API
UI --> API
API --> Engine
API --> Registry
API --> PostgREST --> PG
Engine --> LLM
Engine --> Search
API --> OSS
How it flows: describe a process in natural language → AI generates a workflow (validated & auto-repaired) → edit on the visual canvas → save as versioned history → publish a chosen version as a secured HTTP API (one global API key per user) → external systems call it with Authorization: Bearer <key>.
Docker self-hosted deployment:
flowchart LR
User["User"] -->|":5000"| App["loomflow app"]
App -->|"http://nginx:80/rest/v1"| Nginx["Nginx reverse proxy"]
Nginx --> PostgREST["PostgREST"]
PostgREST --> PG[("PostgreSQL 16<br/>volume: loomflow-pgdata")]
Mig["migration container<br/>idempotent SQL on every `up`"] -.-> PG
Includes PostgreSQL + PostgREST + Nginx — fully self-contained, no Supabase cloud required.
git clone https://github.com/banmu123/LoomFlow.git
cd LoomFlow
bash scripts/init-env.sh # one-time: creates .env with random passwords & JWT keys
docker compose up -d # auto-initializes database (tables + default admin)
After deployment, add your AI model in the UI (no env keys needed):
admin / 123456, change immediately)admin / 123456(⚠️ change after first login)docker compose logs -f loomflowdocker compose down — full guid