evolve-lite:synthesize-skill

Skill Synthesizer

Overview

This skill reads a saved trajectory and produces a reusable agent skill — a SKILL.md plus any supporting scripts — that captures the successful workflow the session discovered. The output goes to .evolve/skills/<skill-name>/ (canonical, evolve-managed). Future sessions on the same project can then invoke the skill directly instead of re-deriving the workflow.

This is the executable counterpart to the learn skill's free-text guidelines: learn writes Markdown the next agent has to read and decide what to do; synthesize-skill writes a skill the next agent can simply call.

When To Use

Use this skill when a trajectory captured:

• A non-trivial workflow that succeeded after trial-and-error (the eventual happy path is worth promoting from free-text advice to an invocable artifact).
• A reusable script or command sequence the model wrote during the session — particularly one the agent had to reconstruct over multiple attempts.
• An environment-specific workaround (a missing system tool, a permissions wrinkle, a fallback pipeline) that future sessions in the same project will hit.

Skip this skill — and let learn cover the case with a guideline alone — when:

• The successful path was a single trivial command.
• The workflow embeds secrets, tokens, or one-off user inputs that can't be safely generalized.
• A skill with the same trigger already exists in .evolve/skills/ (use learn's guideline path to refine the existing skill instead of creating a duplicate).

Workflow

Step 0: Locate the Trajectory

This skill runs in a forked context. You cannot see the parent conversation directly — read the trajectory the parent passed in via args or via the Run evolve-lite:synthesize-skill on <path> instruction.

The trajectory path is either:

• supplied directly as args to the skill invocation, or
• stated in the parent's invocation message as The saved trajectory path is: <path> — take everything after the colon, strip surrounding whitespace and quotes.