// the find
refly-ai/refly
The first open-source agent skills builder. Define skills by vibe workflow, run on Claude Code, Cursor, Codex & more. Build Clawdbot 🦞· APIs for Lovable · Bots for Slack & Lark/Feishu · Skills are infrastructure, not prompts.
Refly is a visual workflow builder that compiles natural-language-described business logic into versioned, portable 'skills' — callable units that can be exported as Claude Code tools, REST APIs, or chat-platform webhooks. It sits between n8n (too trigger-only) and LangChain (too much boilerplate), targeting teams who want reusable, governed agent capabilities without writing framework glue code. The self-hosted stack is substantial: NestJS API, Redis, Postgres, a vector DB, MinIO, and a sandbox service.
The backend abstraction for vector search and object storage is genuinely clean — swappable LanceDB/Qdrant backends behind a typed interface means you're not locked to a specific vector DB when self-hosting. The intervenable runtime concept (pause, audit, re-steer mid-run) addresses a real gap that n8n and Dify ignore entirely. The module structure is well-separated with BullMQ processors offloading async work, and test coverage exists throughout rather than being bolted on late. The skill portability story is concrete — the CLI can publish a workflow as a CLAUDE.md-compatible tool or an MCP server, which is more than most workflow tools offer.
The license is 'ReflyAI Open Source License — Apache 2.0 with additional restrictions.' That is not open source; it is likely a business-source-style restriction preventing you from competing with them using their own code. Read it before building on this. The directory tree still has canvas, collab, knowledge, and drive modules from what was clearly a prior product — this is a pivot, not a greenfield skills builder, and that legacy surface area is dead weight you'd be maintaining. The `skill-package.service.spec.ts.bak` file (a disabled test renamed to avoid execution) is a small but telling sign of test discipline slipping under feature pressure. The 'describe your SOP in natural language and Refly compiles it to a deterministic skill in 3 minutes' claim is underspecified — there is no documentation of what the compiled DSL actually looks like or how it handles ambiguous intent.