# Technical Document Extraction: Configuration (.yaml)
## 1. Component Isolation
The image is a structured technical snippet representing a configuration file. It is divided into two primary regions:
* **Header:** A title bar identifying the content type.
* **Main Content Area:** A code block containing YAML-formatted configuration keys, comments, and descriptions.
---
## 2. Detailed Content Extraction
### Header
* **Text:** `Configuration (.yaml)`
* **Description:** This serves as the title for the data block, indicating that the following text follows YAML (YAML Ain't Markup Language) syntax.
### Main Content Area (YAML Transcription)
The following is a precise transcription of the text within the configuration block. Note that the arrow symbol (`↪`) indicates a line wrap from the original visual representation.
```yaml
# Prompt Templates: Control how observations of environment are shown
# ↪ to agent
system_template: |
First `system` message shown to agent
instance_template: |-
Instance prompt, contains task instance-specific content
next_step_template: |-
Format template of per-turn observation (Contains standard output
↪ from agent's action)
next_step_no_output_template: |-
```
---
## 3. Component Analysis and Flow
This document defines the structure of prompts used to interact with an AI agent. The flow follows a standard LLM (Large Language Model) interaction pattern:
1. **Commentary:** The top lines explain the purpose of the file: controlling how the environment's observations are presented to the agent.
2. **`system_template`**: Defines the high-level instructions or persona (the "system" message) that initializes the agent's behavior.
3. **`instance_template`**: Defines the specific task or problem the agent is currently assigned to solve.
4. **`next_step_template`**: Defines the structure for iterative feedback. It formats the results/observations resulting from the agent's previous actions.
5. **`next_step_no_output_template`**: A placeholder for handling scenarios where an agent's action results in no observable output.
---
## 4. Technical Metadata
* **Language:** English.
* **Format:** YAML.
* **Syntax Notations:**
* The pipe symbols (`|` and `|-`) are YAML block scalars used to handle multi-line strings.
* The `|-` specifically denotes a "strip" block scalar, which removes trailing newlines.
* **Visual Indicators:** The use of a monospaced font suggests this is intended to be read as source code or a configuration schema.
