How Skills Work

Skills are produced and used entirely behind the scenes. This page explains the lifecycle: how a Skill is learned from a Simulation, how versions accumulate, and how Marketrix replays a Skill in a later run.

Distillation: learning a Skill

When a Simulation task completes successfully, Marketrix reviews the steps it took during that run. It looks for multi-step patterns it repeated or could have performed as a single unit — for example:

Filling out and submitting a form
Signing in
Searching and then selecting a result
Stepping through a multi-screen wizard

Each pattern it finds becomes a Skill: a name, a one-line description, and the sequence of actions that make it up. One-off operations — a single click or a single navigation — are deliberately left out, because those are already part of the built-in primitives and there’s nothing reusable to capture.

Distillation only runs when a Simulation task 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.

Distillation is best-effort and runs after the Simulation finishes. If it doesn’t produce a Skill, the Simulation’s own result is unaffected.

Versioning

Skills are versioned and immutable. Marketrix never edits a learned Skill in place. When it learns a refined version of a workflow it already knows, it records a new version of that Skill rather than overwriting the previous one.

This means every Skill carries a full version history — its lineage — so you can see how a workflow evolved over time and which version is currently active. The most recent, non-deprecated version is the one Marketrix uses.

How a Skill is replayed

In a later run, an active Skill is available as a single named action alongside the built-in primitives. When Marketrix chooses to use a Skill, it replays the captured sequence of steps as one unit.

Some Skills accept inputs — for example, a search Skill might take the search term, or a login Skill might take credentials. Marketrix supplies these values when it invokes the Skill, and sensitive values (such as credentials) are filled in securely at execution time and are never logged.

Scope and availability

Per Application — A learned Skill belongs to the Application it was learned in, and is only available on that same Application.
Built-in primitives vs. learned Skills — The baseline browser primitives are always available. Learned Skills are layered on top of those.
Experience level — How many of an Application’s learned Skills a run draws on varies with the Simulation’s experience level: a lower level leans on the baseline primitives, while a higher level has the full learned-Skill catalogue available.

Skills Overview What Skills are and why they matter.

Using Skills Review, inspect, and deprecate learned Skills.

Simulations The runs Skills are distilled from.