# Creating Multi-Step Workflows with Claude Skills: A Practical Guide
> Learn to build multi step workflows with Claude skills. This guide explains how to define sequences, reference scripts, and load documentation for powerful automation. Get started today!
- Repository: [Composio/awesome-claude-skills](https://github.com/composiohq/awesome-claude-skills)
- Tags: how-to-guide
- Published: 2026-07-27
---
**Multi-step workflows in Claude skills are defined in the [`SKILL.md`](https://github.com/ComposioHQ/awesome-claude-skills/blob/main/SKILL.md) front-matter and body, using hierarchical step sequences that reference executable scripts in the `scripts/` directory and load contextual documentation from `references/` on demand.**
The awesome-claude-skills repository provides a structured framework for building complex automation chains. A skill is treated as a self-contained package that tells Claude when to activate, what resources to use, and how to carry out tasks. Creating multi-step workflows involves structuring your [`SKILL.md`](https://github.com/ComposioHQ/awesome-claude-skills/blob/main/SKILL.md) with procedural logic while offloading deterministic actions to scripts, enabling sophisticated automation that remains maintainable and token-efficient.
## Anatomy of a Multi-Step Skill Package
According to the source code in [`skill-creator/SKILL.md`](https://github.com/ComposioHQ/awesome-claude-skills/blob/main/skill-creator/SKILL.md), a workflow-ready skill consists of four core components:
| Component | Purpose | Content Type |
|-----------|---------|--------------|
| [`SKILL.md`](https://github.com/ComposioHQ/awesome-claude-skills/blob/main/SKILL.md) | Metadata + high-level procedural guide with workflow definitions | Markdown with YAML front-matter |
| `scripts/` | Deterministic, executable code for concrete actions | Python, Bash, or other executable scripts |
| `references/` | Large documentation loaded on-demand (API specs, schemas) | Markdown technical documents |
| `assets/` | Static files for final output generation | Templates, images, fonts |
When Claude activates a skill, it first processes the [`SKILL.md`](https://github.com/ComposioHQ/awesome-claude-skills/blob/main/SKILL.md) metadata and workflow section, then progressively loads scripts and references as specific steps require them.
## Structuring Workflows in SKILL.md
Multi-step logic lives primarily in the [`SKILL.md`](https://github.com/ComposioHQ/awesome-claude-skills/blob/main/SKILL.md) file. As documented in [`skill-creator/SKILL.md`](https://github.com/ComposioHQ/awesome-claude-skills/blob/main/skill-creator/SKILL.md) (lines 20-22), the repository supports "Specialized workflows – Multi-step procedures" through hierarchical headings and enumerated steps.
Each workflow step can:
- **Describe the intent** – A concise sentence Claude uses to decide the next action
- **Reference a script** – Point to files in `scripts/` for deterministic processing
- **Load a reference** – Pull from `references/` when extensive context is needed
A typical workflow structure follows this pattern:
```markdown
---
name: data-processor
description: Processes raw data through validation and transformation.
---
## Workflow
1. **Validate Input** – Claude checks file format using `scripts/validate.py`.
2. **Extract Data** – Claude runs `scripts/extract.py` to parse content.
3. **Transform** – Claude loads `references/transform_rules.md` and applies `scripts/transform.py`.
4. **Generate Report** – Claude uses `scripts/generate_report.py` with templates from `assets/`.
```
## Progressive Disclosure for Token Efficiency
The architecture implements **progressive disclosure** to manage context windows efficiently. As noted in [`skill-creator/SKILL.md`](https://github.com/ComposioHQ/awesome-claude-skills/blob/main/skill-creator/SKILL.md) (lines 77-84), Claude first sees only the front-matter, then the body of [`SKILL.md`](https://github.com/ComposioHQ/awesome-claude-skills/blob/main/SKILL.md), and finally loads scripts or references on demand.
This approach:
- Keeps the initial token budget minimal by deferring large reference documents until needed
- Allows workflows to branch conditionally based on intermediate results
- Maintains clarity by separating high-level logic from implementation details
## Implementing Workflow Steps with Scripts
Scripts in the `scripts/` directory handle deterministic, executable actions. Consider this example from an image enhancement workflow that adjusts brightness as Step 2:
```python
#!/usr/bin/env python3
# scripts/adjust_brightness.py
import sys
from PIL import Image, ImageEnhance
def adjust_brightness(image_path: str, factor: float, out_path: str):
img = Image.open(image_path)
enhancer = ImageEnhance.Brightness(img)
img_enhanced = enhancer.enhance(factor)
img_enhanced.save(out_path)
print(f"Brightness adjusted by {factor}; saved to {out_path}")
if __name__ == "__main__":
if len(sys.argv) != 4:
print("Usage: adjust_brightness.py