argent-create-flow

Name: argent-create-flow
Author: software-mansion

1.8kstars51forks

How to install argent-create-flow?

software-mansion/argent/argent-create-flow

$npx -y skills add software-mansion/argent --skill argent-create-flow

Installs into the current project.

Summary

Record a reusable flow (scripted sequence of MCP tool calls) that can be replayed later with a single command. Use when the user asks to create, record, or build a flow, or to script a sequence of device actions. Also used proactively, without an explicit request, when a multi-st

Files · 1

View on GitHub

SKILL.md

1	## Overview
2
3	A flow is a sequence of steps saved to a `.yaml` file in the `.argent/flows/` directory. Each recorded step is executed live as you add it, so you verify it works before it becomes part of the flow. Replay a finished flow with `flow-execute`, or — for an e2e flow — headlessly with `argent flow run <name>`.
4
5	Flows store no device id: the runner binds a device (the single booted one, or pass `device`/`platform`). A recorded coordinate `gesture-tap` is captured as a portable `tap: { selector }` step whenever the tapped element has stable text/identifier.
6
7	Two flow types
8
9	- e2e — begins with a `launch:` step, which starts that app from scratch (terminate + relaunch), so the flow controls its own start state. No `executionPrerequisite`. May `run:` other flows, and (on iOS/Android) may itself be a `run:` target — when nested, its `launch` runs inline, restarting the app for that sub-scenario. Chromium is the exception: the runner boots one Electron app per run (the top-level flow's), so a nested chromium e2e flow's `launch` can't boot its own instance and fails the run — keep chromium e2e flows top-level. Record one by adding a `restart-app` of the app under test as the first step — it is captured as the `launch` step.
10	- fragment — doesn't begin with a launch; runs against the device's current state. May declare an `executionPrerequisite` (a documented entry-state contract). Invoked from other flows via a `run:` step, or directly by you at any time.
11
12	Both run via `argent flow run <name>` — a fragment simply runs against whatever is on screen (its prerequisite is printed as a reminder). Only e2e flows are meaningful CI/suite entries, since only they give a deterministic verdict from a clean start.
13
14	### Step directives
15
16	Beyond raw `tool:` steps and `echo:`, flows support declarative directives interpreted by the runner (they are not agent-callable tools). Every directive hard-stops the flow on failure; later steps are reported `skip`.
17
18	\| Directive \| YAML \| Meaning \|
19	\| ------------ \| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- \| --------------------------------------------------------------------------------------------------------------------------------------------------------------- \|
20	\| `launch` \| `- launch: com.acme.app` or `- launch: { ios: …, android: … }` \| start the app from scratch (terminate + relaunch) and wait until ready \|
21	\| `tap` \| `- tap: Login`, `- tap: { x: 0.5, y: 0.57 }`, `- tap: { on: Login, times: 2 }`, `- tap: { on: { x: 0.5, y: 0.57 }, times: 2 }` \| tap by selector (auto-waits) or raw point; `times` (2 = double-tap) needs the target nested under `on:` — a selector or a point (`{ x, y, times }` is rejected) \|
22	\| `long-press` \| `- long-press: Row 3`, `- long-press: { x: 0.5, y: 0.6 }`, `- long-press: { on: <sel>, duration: 1200 }`, `- long-press: { on: { x: 0.5, y: 0.6 }, duration: 1200 }` \| press and hold an element or raw point (default 800ms; Chromium: mouse press-hold); `duration` needs the target nested under `on:` — a selector or a point \|
23	\| `type` \| `- type: { into: email, text: "a@b.com" }` \| focus a field, type, then press Enter to submit + dismiss the keyboard \|
24	\| `scroll-to` \| `- scroll-to: "Order #1234"` (scrolls down) or `- scroll-to: { target: …, direction: right, within: … }` \| momentum-free scroll until the target is visible \|
25	\| `await` \| `- await: { visible: Home }`

People who liked this also viewed

6 picks

Type

argent-create-flow

1.8kstars51forks

View on GitHub

How to install argent-create-flow?

software-mansion/argent/argent-create-flow

$npx -y skills add software-mansion/argent --skill argent-create-flow

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	## Overview
2
3	A flow is a sequence of steps saved to a `.yaml` file in the `.argent/flows/` directory. Each recorded step is executed live as you add it, so you verify it works before it becomes part of the flow. Replay a finished flow with `flow-execute`, or — for an e2e flow — headlessly with `argent flow run <name>`.
4
5	Flows store no device id: the runner binds a device (the single booted one, or pass `device`/`platform`). A recorded coordinate `gesture-tap` is captured as a portable `tap: { selector }` step whenever the tapped element has stable text/identifier.
6
7	Two flow types
8
9	- e2e — begins with a `launch:` step, which starts that app from scratch (terminate + relaunch), so the flow controls its own start state. No `executionPrerequisite`. May `run:` other flows, and (on iOS/Android) may itself be a `run:` target — when nested, its `launch` runs inline, restarting the app for that sub-scenario. Chromium is the exception: the runner boots one Electron app per run (the top-level flow's), so a nested chromium e2e flow's `launch` can't boot its own instance and fails the run — keep chromium e2e flows top-level. Record one by adding a `restart-app` of the app under test as the first step — it is captured as the `launch` step.
10	- fragment — doesn't begin with a launch; runs against the device's current state. May declare an `executionPrerequisite` (a documented entry-state contract). Invoked from other flows via a `run:` step, or directly by you at any time.
11
12	Both run via `argent flow run <name>` — a fragment simply runs against whatever is on screen (its prerequisite is printed as a reminder). Only e2e flows are meaningful CI/suite entries, since only they give a deterministic verdict from a clean start.
13
14	### Step directives
15
16	Beyond raw `tool:` steps and `echo:`, flows support declarative directives interpreted by the runner (they are not agent-callable tools). Every directive hard-stops the flow on failure; later steps are reported `skip`.
17
18	\| Directive \| YAML \| Meaning \|
19	\| ------------ \| -------------------------------------------------------------------------------------------------------------------------------------------------------------------- \| --------------------------------------------------------------------------------------------------------------------------------------------------------------- \|
20	\| `launch` \| `- launch: com.acme.app` or `- launch: { ios: …, android: … }` \| start the app from scratch (terminate + relaunch) and wait until ready \|
21	\| `tap` \| `- tap: Login`, `- tap: { x: 0.5, y: 0.57 }`, `- tap: { on: Login, times: 2 }`, `- tap: { on: { x: 0.5, y: 0.57 }, times: 2 }` \| tap by selector (auto-waits) or raw point; `times` (2 = double-tap) needs the target nested under `on:` — a selector or a point (`{ x, y, times }` is rejected) \|
22	\| `long-press` \| `- long-press: Row 3`, `- long-press: { x: 0.5, y: 0.6 }`, `- long-press: { on: <sel>, duration: 1200 }`, `- long-press: { on: { x: 0.5, y: 0.6 }, duration: 1200 }` \| press and hold an element or raw point (default 800ms; Chromium: mouse press-hold); `duration` needs the target nested under `on:` — a selector or a point \|
23	\| `type` \| `- type: { into: email, text: "a@b.com" }` \| focus a field, type, then press Enter to submit + dismiss the keyboard \|
24	\| `scroll-to` \| `- scroll-to: "Order #1234"` (scrolls down) or `- scroll-to: { target: …, direction: right, within: … }` \| momentum-free scroll until the target is visible \|
25	\| `await` \| `- await: { visible: Home }`

People who liked this also viewed

6 picks

Type