langflow

Translate natural-language requests into otto__langflow tool calls for LangFlow flows.

Updated May 25, 2026
One-click install
npx skills add https://github.com/cmetech/otto-cli --skill langflow-cmetech
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: langflow
Source: https://github.com/cmetech/otto-cli/tree/main/src/resources/extensions/otto/skills/langflow
Command: npx skills add https://github.com/cmetech/otto-cli --skill langflow-cmetech

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Translate natural-language LangFlow requests into observable otto__langflow tool calls to drive LangFlow flows.

Core Features & Use Cases

  • Convert user intents into otto__langflow actions (build_flow, list_flows, show_flow, import_flow, export_flow, delete_flow, run_flow, status).
  • Orchestrate end-to-end LangFlow workflows from plain language descriptions in a terminal context.
  • Use cases include creating a new flow from a description, inspecting an existing flow, importing/exporting flows, and running a flow with input data.

Quick Start

Create a LangFlow flow from a description and run it with sample input.

Frequently Asked Questions about langflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build and run LangFlow workflows from natural language descriptions?

LangFlow workflows can be built and run by translating plain language requests into actionable tool calls. This maps user intents directly to operations like build_flow and run_flow, allowing you to create and execute flows without manual CLI syntax.

Can I manage LangFlow imports and exports through a command line interface?

Yes, you can manage LangFlow imports and exports through a command line interface. Natural language requests are translated into import_flow and export_flow actions, enabling you to transfer flow configurations seamlessly across different project contexts.

What happens if my LangFlow instance is not connected when I try to run a command?

If LangFlow is not connected, the system provides safe fallbacks. Instead of failing, it gracefully handles the missing connection when attempting to map intents to LangFlow actions like listing, showing, or deleting flows.

How do I list and inspect existing LangFlow flows in my project?

To inspect existing LangFlow flows, you can issue a natural language request that triggers the list_flows and show_flow actions. This translates your intent into observable tool calls, returning the specific flow details without requiring exact CLI arguments.

Does this approach support deleting and checking the status of LangFlow flows?

Yes, deleting and checking status are fully supported. Natural language requests are mapped to the delete_flow and status actions, allowing you to manage flow lifecycles and verify system connectivity directly from plain language descriptions.

What is the best way to orchestrate end-to-end LangFlow automation from a terminal?

The best way to orchestrate LangFlow automation is by using natural language to drive terminal-based workflows. This converts your plain text intents into observable tool calls, mapping actions like building, running, and managing flows across diverse project contexts.