Skills Overview
Skills are reusable browser-automation routines that Marketrix learns on its own from completed Simulations. You don’t write Skills by hand; they surface on the Skills page so you can review, inspect, and manage them.
How a Skill is learned
Section titled “How a Skill is learned”When a Simulation run completes successfully, Marketrix reviews its steps for multi-step patterns it repeated or could have performed as one unit. Typical ones are submitting a form, signing in, searching and selecting a result, or stepping through a wizard. Each pattern becomes a Skill: a name, a one-line description, and the sequence of actions that make it up. One-off operations such as a single click or navigation are left out, because those are already built-in primitives.
Distillation only runs when a Simulation run meets all of these conditions:
- The task completed successfully (failed or stopped runs are not distilled).
- The run produced enough steps to be worth capturing — by default, at least three.
- The run explored your application. A Survey run answers a questionnaire page instead, so there is no product behavior in it to capture.
Distillation is best-effort and runs after the Simulation finishes. If it doesn’t produce a Skill, the Simulation’s own result is unaffected.
Versions
Section titled “Versions”Skills are versioned and immutable. When Marketrix learns a better way to perform a workflow it already knows, it records a new version rather than overwriting the old one. Every Skill carries its full version history. The most recent, non-deprecated version is the one Marketrix uses.
How a Skill is replayed
Section titled “How a Skill is replayed”In a later run, an active Skill is available as a single named action alongside the built-in browser primitives. Marketrix replays a workflow it already knows works instead of re-deriving it. Some Skills accept inputs — a search Skill might take the search term, a login Skill the credentials. Marketrix supplies these when it invokes the Skill, and sensitive values are filled in securely at execution time and never logged.
- Per Application — A Skill is available only on the Application it was learned in.
- Experience level — The Simulation’s experience level sets how many learned Skills a run draws on. A lower level leans on the baseline primitives; a higher level has the full learned-Skill catalogue available.