argent-create-flow

Record, polish, and replay reusable Argent flow YAML files for device UI automation.

Updated Aug 29, 2026
One-click install
npx skills add https://github.com/Seyamalam/pstu_final --skill argent-create-flow-seyamalam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: argent-create-flow
Source: https://github.com/Seyamalam/pstu_final/tree/main/.agents/skills/argent-create-flow
Command: npx skills add https://github.com/Seyamalam/pstu_final --skill argent-create-flow-seyamalam

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually repeating multi-step device interactions is error-prone and cannot be replayed deterministically. This Skill captures live device walkthroughs as replayable Argent flow YAML files with stable selectors, verified navigation gates, and audited reliability. ## Core Features & Use Cases - Live flow recording: Start a recorder, capture taps, typing, waits, and navigation checks one verified step at a time, then finish and polish the YAML. - Selector discipline and auditing: Enforce stable id/text selectors, run blocking audits for raw coordinates, role-only selectors, device ids, and weak gates before replay. - Replay and repair: Replay flows end to end, diagnose failures by class, and correct the smallest justified unit with a two-cycle correction limit. - Use Case: Record a sign-in-to-settings path on an iOS simulator once, polish it into an e2e flow with identity and idle gates, then replay it in CI via argent flow run on every build. ## Quick Start Ask the assistant to record a new Argent flow that launches your app, walks through the target screens, and replays the saved YAML end to end.

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 a reusable UI automation flow on iOS or Android?▼

Start flow-start-recording before launching the app, record a plain restart-app as the first action so it converts to a launch step, then record each tap and await-ui-element check live. Finish with flow-finish-recording, polish the YAML, and replay it end to end.

What is the difference between an e2e flow and a fragment in Argent?▼

An e2e flow has a literal launch step as its first non-echo step and controls process start. A fragment has no leading launch and must declare a precise executionPrerequisite describing the required UI, account, and platform state.

When should I use argent-create-flow versus argent-qa-flows?▼

Use argent-create-flow for recording and replaying repeatable device paths, profiling, or A/B comparisons. For saved QA test cases, tickets, or acceptance criteria, load argent-qa-flows first, which adds deterministic setup, acceptance evidence, and a two-pass proof requirement.

Why does my recorded flow keep raw coordinates instead of selectors?▼

The recorder keeps a raw point when it cannot derive an id, text, or role from the pre-tap tree, often because the tree source is unavailable. Run the coordinate fallback gate: restore the tree source, test candidate selectors in a scratch fragment, and re-record the tap.

Can Argent flows run on Chromium or Vega devices?▼

Yes, with platform limits. Chromium boots one instance per launch step and rejects pinch and rotate, while Vega uses tv-remote and raw keyboard tools instead of touch directives. Chromium flows are recorded as fragments with the launch added during polish.

What should I do when flow replay fails?▼

Classify the failure first: hard failure, environment error, silent misfire, partial divergence, or acceptance failure. Capture a screenshot and describe output, diagnose the first divergence, correct the smallest justified unit, and stop after two unsuccessful correction cycles.