Skip to main content

Workflows (Legacy)

Workflows are deprecated and kept only for projects that already have them. For new repeatable tasks, use Skills: the agent can pick a skill automatically, and you can run one manually with a / command.

A workflow is a Markdown file with a repeatable prompt. You add it to a request manually from the input field. Old global and project workflows are still useful as source material for migration, but you should not build new scenarios in this format.

Migrating a workflow to a skill​

  1. Create a new Skill from the new chat menu.
  2. Move the goal, steps, constraints, and result format from the workflow into SKILL.md.
  3. Give the skill a short unique name and a precise task description. The agent uses the description to decide when to apply the skill automatically.
  4. If the scenario should only work in a particular mode, specify the appropriate agent and make sure it has the tools it needs.
  5. Run the skill manually with /skill-name on a safe test task.
  6. Once the result matches the old workflow, remove the workflow from your active set, or keep it only during the transition.

Placeholders such as {goal} and {files} can usually be replaced with a plain instruction: the agent takes the goal and the attached files from the current request. If a value is mandatory, state directly in the skill that the agent must ask for it before starting.

What to move over​

From an old workflow you usually need:

  • the trigger condition and the expected result;
  • the order of actions;
  • constraints on files and commands;
  • verification criteria;
  • the format of the final answer.

Do not carry over outdated references to the Workflows interface or the #workflow command. For a manual run, use /skill-name.

How to verify the migration​

Run the old workflow and the new skill on the same small task. Compare the changed files, the checks performed, and the final answer. The skill itself does not expand the agent's permissions: the selected mode still has to support the required tools, and Edit Scope and the ignore files still limit access.

For more on creating and running skills, see Skills.

Reference for the old format​

In older Explyt versions, a workflow could be global or project-scoped. You created a Markdown file through the Workflows dialog, then added it to a request with #workflow or launched it from the panel. This information is only needed to support existing configurations.

The documentation does not state an exact removal date for the feature or a full list of differences between the formats. Before a bulk migration, keep a copy of the old files and test each skill on a real but safe task.