Skip to content
Development
Skill

/evolve-lite-save

Captures the current session's successful workflow and saves it as a reusable skill with SKILL.md and helper scripts

From plugin
altk-evolve
13733 skills12 commands

Claude Code

$ npx -y skills add AgentToolkit/altk-evolve --skill evolve-lite-save --agent claude-code

SKILL.md

evolve-lite-save.SKILL.md
name: evolve-lite:save
description: Captures the current session's successful workflow and saves it as a reusable skill with SKILL.md and helper scripts

Save Session as Skill

Overview

This skill analyzes your current successful session and generates a new reusable skill with:

  • **SKILL.md**: Comprehensive documentation with workflow steps, parameters, and examples
  • **Helper scripts**: Python scripts for any programmatic operations identified in the workflow

It extracts the workflow pattern from your conversation history (user requests, reasoning steps, tool calls, and responses) and creates parameterized files that can be invoked in future sessions.

Use this skill when you've completed a task successfully and want to save the workflow for future reuse.

When to Use

  • After completing a multi-step task successfully
  • When you've discovered a useful workflow pattern
  • When you want to standardize a process for future use
  • After solving a problem that might recur
  • When the workflow involves programmatic operations that could benefit from helper scripts

Workflow

Step 1: Review Current Session

Analyze the conversation history available in the current context, which includes:

  • **User messages**: All requests and questions from the user
  • **Assistant reasoning**: Thinking tags and decision-making process
  • **Tool calls**: All tools invoked with their arguments
  • **Tool responses**: Results and outcomes from each tool
  • **Final outcome**: The successful result achieved

**Action**: Review the entire conversation from start to current point

Step 2: Identify the Workflow Pattern

Extract the high-level workflow by:

1. **Identifying the goal**: What was the user trying to accomplish? 2. **Grouping related actions**: Which tool calls belong together as logical steps? 3. **Recognizing decision points**: Where did the workflow branch based on conditions? 4. **Noting error handling**: How were errors or edge cases handled? 5. **Extracting the sequence**: What is the step-by-step process?

**Example Pattern Recognition**:

User Goal: "Read a file and display its contents"

Workflow Pattern:
1. Attempt to read file at expected location
2. If access denied → check allowed directories
3. Search for file in allowed directories
4. Read file from correct location
5. Format and present results

Step 3: Identify Parameterizable Values

Apply **conservative parameterization** - only parameterize obvious session-specific values:

**Parameterize**:

  • Absolute file paths → `{file_path}` or `{directory}`
  • Specific file names → `{filename}`
  • User-specific data → `{data_value}`
  • Project-specific names → `{project_name}`
  • Workspace directories → `{workspace_dir}`

**Keep Unchanged**:

  • Tool names (e.g., `read_file`, `execute_command`)
  • General patterns and logic
  • Error handling approaches
  • Workflow structure

**Example**:

Original: "Read /home/user/projects/myapp/config.json"
Parameterized: "Read {project_dir}/{config_file}"

Step 4: Identify Script Opportunities

Analyze the workflow to determine if helper scripts would be beneficial:

**Generate scripts when the workflow includes**:

  • Data transformation or parsing (JSON, CSV, XML processing)
  • File operations (reading, writing, searching, filtering)
  • API calls or HTTP requests
  • Complex calculations or data analysis
  • Repetitive operations that could be automated
  • Integration with external tools or services

**Script Types to Consider**:

  • **Data processors**: Parse, transform, or validate data
  • **File handlers**: Read, write, or manipulate files
  • **API clients**: Interact with external services
  • **Validators**: Check inputs or outputs
  • **Formatters**: Convert data between formats

**Example**:

Workflow includes: Reading JSON file, extracting specific fields, formatting output
→ Generate: parse_and_format.py script

Step 5: Generate Skill Document

Create a new SKILL.md file with the following structure:

---
name: {skill-name}
description: {one-line description of what this skill does}
---

# {Skill Title}

## Overview

{Brief description of the skill's purpose and when to use it}

## Parameters

{List parameters the user needs to provide}

- **{param_name}**: {description and example}

## Workflow

### Step 1: {Step Name}

{What this step does}

**Action**: {Tool or approach to use}

**Example**:

{Example tool call or command}


{If helper script exists, reference it}
**Helper Script**: Use `scripts/{script_name}.py` for this operation

{Repeat for each step}

## Helper Scripts

{If scripts were generated, document them}

### {script_name}.py

**Purpose**: {What the script does}

**Usage**:
```bash
python3 .bob/skills/{skill-name}/scripts/{script_name}.py [arguments]

**Parameters**:

  • `{param}`: {description}

**Example**:

python3 .bob/skills/{skill-name}/scripts/parse_data.py input.json

Error Handling

{Common errors and how to handle them}

Examples

Example 1: {Use Case}

**Input**:

  • {param}: {value}

**Expected Output**: {What the user should see}

Notes

{Additional guidelines or context}


### Step 6: Generate Helper Scripts

For each identified script opportunity, create a Python script with:

**Script Template**:
```python
#!/usr/bin/env python3
"""
{Script description}

Usage:
    python3 {script_name}.py [arguments]

Arguments:
    {arg1}: {description}
    {arg2}: {description}
"""

import sys
import json
import argparse
from pathlib import Path


def main():
    """Main function implementing the script logic."""
    parser = argparse.ArgumentParser(description="{Script description}")
    parser.add_argument("{arg1}", help="{description}")
    parser.add_argument("{arg2}", help="{description}", nargs="?")

    args = parser.parse_args()

    # Implementation based on workflow pattern
    try:
        # Core logic here
        result = process_data(args.{arg1})
        print(json.dumps(result, indent=2))
    exc
Read more
@agenttoolkit
Ships withaltk-evolve

Evolve helps AI agents learn from experience. It turns past trajectories into reusable guidelines that help agents complete future tasks, without changing model weights.

Stars on GitHub

Momentum

stars in total
137
Star history of AgentToolkit/altk-evolve on GitHub, a chart by star-history.com

Other skills on altk-evolve.

More skills from other plugins.

brainstorming
Auto-invoked

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…

@obra@obraInstall Skill
ask-matt

ask-matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

skills2w309k
@mattpocock@mattpocockInstall Skill
accessibility
Auto-invoked

accessibility

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels,…

ecc2w293k
@affaan-m@affaan-mInstall Skill
compiler-commit

compiler-commit

Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits…

react5d252k
@facebook@facebookInstall Skill

Questions about evolve-lite-save.

Which coding agents can use evolve-lite-save?
evolve-lite-save installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.