argent-create-flow

Record and replay MCP tool call sequences as YAML flow files.

34|2|Updated Aug 16, 2025
One-click install
npx skills add https://github.com/FilenCloudDienste/filen-ts --skill argent-create-flow-filenclouddienste
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: argent-create-flow
Source: https://github.com/FilenCloudDienste/filen-ts/tree/main/.claude/skills/argent-create-flow
Command: npx skills add https://github.com/FilenCloudDienste/filen-ts --skill argent-create-flow-filenclouddienste

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of repeating multi-step UI/tool interactions by letting you capture a working sequence once and replay it later, reducing error-prone rework and drift.

Core Features & Use Cases

  • Record reusable sequences: Capture a scripted flow of MCP tool calls into a YAML file stored under .argent/flows/ as you execute each step live.
  • Replay with safety gates: Re-run flows later with flow-execute, including prerequisite handling that prompts for confirmation before executing.
  • Build transparent step logic: Insert human-readable echo labels and use step results (including screenshots) to validate and debug.
  • Use case: When you need to build a consistent simulator routine—such as navigating to a specific app state by launching the app and performing taps/swipes—record it once and replay it whenever the workflow is needed again.

Quick Start

Start recording a flow with a name and execution prerequisite, add steps by executing each MCP tool call live, then finish recording and replay it by flow name when you need to repeat the same actions.

Frequently Asked Questions about argent-create-flow

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

FAQPage Schema
How do I record and replay multi-step tool flows for UI automation?

Recording tool flows involves executing MCP tool calls live to capture a scripted sequence into a YAML file stored under .argent/flows/. You replay the saved flow later to reliably repeat complex simulator interactions with consistent state management.

What is the best way to automate repeating complex simulator interactions consistently?

The best way to automate repeating simulator interactions is recording a working sequence of MCP tool calls once into a YAML flow file, then replaying it whenever needed to reduce error-prone rework and drift.

How do I add safety gates or prerequisite checks before replaying an automated workflow?

You add safety gates by using optional prerequisite acknowledgment handling during flow-execute, which prompts for confirmation before executing the replay. This ensures safe re-runs of saved automation sequences.

Can I insert human-readable labels and screenshots to debug a recorded workflow?

Yes, you can insert human-readable echo labels into your step logic and use step results including screenshots to validate and debug the recorded flow during both recording and replay.

Do I need a specific file format to store and discover recorded automation sequences?

Yes, you need YAML frontmatter for flow discovery. Recorded sequences are saved as YAML files under the .argent/flows/ directory to enable reliable storage and subsequent replay.

Why does replaying tool orchestration flows reduce errors compared to manual execution?

Replaying recorded flows reduces errors because capturing a working sequence once eliminates manual rework and drift. The saved YAML flow file ensures multi-step interactions execute with consistent state management every time.