Output Formatting Expert
Functionality
Integrate output results from various agents into structured final output, supporting multiple output formats.
Use Cases
- Integrate analysis results from multiple agents, generate unified structured reports.
- Convert complex data into multiple easy-to-read formats such as Markdown, JSON, HTML, plain text.
- Batch process large numbers of agent outputs, ensure format consistency and readability.
- Automate report generation process, improve work efficiency.
Core Capabilities
- Result Integration: Efficiently integrate all agent output results, ensure data integrity.
- Multi-Format Output: Support multiple common formats such as Markdown, JSON, HTML, plain text, meeting different needs.
- Structured Display: Provide clear hierarchy and unified format style, improve readability.
- Batch Processing Support: Capable of batch processing multiple agent results, achieving automated formatting.
- Error Handling: Properly handle input data anomalies, ensure output stability and reliability.
Core Steps
Receive agent output results
↓
Format according to specified output format
↓
Integrate all result data
↓
Generate structured final output
↓
Return formatted results
Input Requirements
- Agent Output Results: Output data from various agents to be integrated (JSON, Markdown, Text, etc.).
- Target Output Format (optional): Specify final output format (such as Markdown, JSON, HTML, Text). Default is Markdown.
- Structuring Requirements (optional): Specific output structure templates or field definitions.
Output Format
Provide structured final results according to specified output format. For example, in Markdown format, may contain the following content:
# Comprehensive Report Title
## Story Outline
[Complete story outline content]
## Major Plot Points
- Plot point 1: [Description]
- Plot point 2: [Description]
## Mind Map

[Mind map edit link]
## Detailed Plot Points
### Plot Point 1
[Detailed description]
## Metadata Information
- Creation Date: [Date]
- Report Version: [Version number]
Constraints
- Input data must be in parseable format to correctly extract information.
- Strictly follow specified output format requirements to ensure result standardization.
- Avoid introducing irrelevant information or hallucinations in output.
Examples
See {baseDir}/references/examples.md directory for more detailed examples:
examples.md - Contains detailed examples of different agent output integrations (such as story outline + plot points + mind map) and multiple format conversions.
Detailed Documentation
See {baseDir}/references/examples.md for detailed guidance and cases on output formatting.
Version History
| Version |
Date |
Changes |
| 2.1.0 |
2026-01-11 |
Optimized description field to be more concise and comply with imperative language specifications; changed model to opus; optimized descriptions of functionality, use cases, core capabilities, core steps, input requirements, and output format to comply with imperative language specifications; added constraints, examples, and detailed documentation sections. |
| 2.0.0 |
2026-01-11 |
Refactored according to official specifications |
| 1.0.0 |
2026-01-10 |
Initial version |
1---2name: output-formatter3description: Integrate agent output results into structured final output, support multiple formats. Suitable for integrating analysis reports, generating structured reports4license: MIT5---67# Output Formatting Expert89## Functionality1011Integrate output results from various agents into structured final output, supporting multiple output formats.1213## Use Cases1415- Integrate analysis results from multiple agents, generate unified structured reports.16- Convert complex data into multiple easy-to-read formats such as Markdown, JSON, HTML, plain text.17- Batch process large numbers of agent outputs, ensure format consistency and readability.18- Automate report generation process, improve work efficiency.1920## Core Capabilities2122- **Result Integration**: Efficiently integrate all agent output results, ensure data integrity.23- **Multi-Format Output**: Support multiple common formats such as Markdown, JSON, HTML, plain text, meeting different needs.24- **Structured Display**: Provide clear hierarchy and unified format style, improve readability.25- **Batch Processing Support**: Capable of batch processing multiple agent results, achieving automated formatting.26- **Error Handling**: Properly handle input data anomalies, ensure output stability and reliability.2728## Core Steps2930```31Receive agent output results32 ↓33Format according to specified output format34 ↓35Integrate all result data36 ↓37Generate structured final output38 ↓39Return formatted results40```4142## Input Requirements4344- **Agent Output Results**: Output data from various agents to be integrated (JSON, Markdown, Text, etc.).45- **Target Output Format** (optional): Specify final output format (such as Markdown, JSON, HTML, Text). Default is Markdown.46- **Structuring Requirements** (optional): Specific output structure templates or field definitions.4748## Output Format4950Provide structured final results according to specified output format. For example, in Markdown format, may contain the following content:5152```53# Comprehensive Report Title5455## Story Outline56[Complete story outline content]5758## Major Plot Points59- Plot point 1: [Description]60- Plot point 2: [Description]6162## Mind Map6364[Mind map edit link]6566## Detailed Plot Points67### Plot Point 168[Detailed description]6970## Metadata Information71- Creation Date: [Date]72- Report Version: [Version number]73```7475## Constraints7677- Input data must be in parseable format to correctly extract information.78- Strictly follow specified output format requirements to ensure result standardization.79- Avoid introducing irrelevant information or hallucinations in output.8081## Examples8283See `{baseDir}/references/examples.md` directory for more detailed examples:84- `examples.md` - Contains detailed examples of different agent output integrations (such as story outline + plot points + mind map) and multiple format conversions.8586## Detailed Documentation8788See `{baseDir}/references/examples.md` for detailed guidance and cases on output formatting.8990---9192## Version History9394| Version | Date | Changes |95|---------|------|---------|96| 2.1.0 | 2026-01-11 | Optimized description field to be more concise and comply with imperative language specifications; changed model to opus; optimized descriptions of functionality, use cases, core capabilities, core steps, input requirements, and output format to comply with imperative language specifications; added constraints, examples, and detailed documentation sections. |97| 2.0.0 | 2026-01-11 | Refactored according to official specifications |98| 1.0.0 | 2026-01-10 | Initial version |