[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Produce a JSON document for a api specification.

[Assistant]
Approach:
1. Task: Create api specification in JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Optional bottom-line complexity API",
    "version": "1.0.0"
  },
  "paths": {
    "/traditional": {
      "get": {
        "summary": "Discussion then kind hair.",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Generate customer review data in XML format.

[Assistant]
Approach:
1. Task: Create customer review in XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-2575466</review_id>
<product_id>PROD-346187</product_id>
<user_id>320eb87e-12bd-44ab-bb47-6fec45bd5144</user_id>
<rating>1</rating>
<title>Possible modern last rate memory fight conference </title>
<content>Character walk loss rock me social gun.
Center choice either push. Push stop yourself.</content>
<date>2026-01-01</date>
<verified_purchase>False</verified_purchase>
<helpful_votes>26</helpful_votes>
</customer_review>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Produce a XML document for a customer review.

[Assistant]
Approach:
1. Task: Create customer review in XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-5832770</review_id>
<product_id>PROD-688379</product_id>
<user_id>d5e035fb-55b8-4fae-85aa-504fb2b837bd</user_id>
<rating>3</rating>
<title>Investment great beat fear step Democrat treat.</title>
<content>Near season take foot decade hold some meet.
Pretty season exist old turn consumer particularly star. Step receive unit different.</content>
<date>2026-01-02</date>
<verified_purchase>False</verified_purchase>
<helpful_votes>62</helpful_votes>
</customer_review>


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Output product listing as YAML.

[Assistant]
Approach:
1. Task: Create product listing in YAML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
product_id: PROD-141484
name: Managed bandwidth-monitored focus group
category: books
price: 751.35
currency: USD
stock: 108
is_available: true
rating: 2.94
reviews: 250
specs:
  weight_kg: 6.41
  dimensions: 15x82x35cm


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<news_article>
<article_id>ART-8221745</article_id>
<headline>Polarized zero administration support</headline>
<author>Maria Johnson</author>
<published>2026-01-03T08:37:58.870132</published>

Business

<content>Would movement white military what them cup. Available remember control staff. None mean hundred PM.
Improve wear produce price according. He method market computer TV strategy.
Body into language. Which other hear they look some option.</content>
<tags>environment</tags>
<tags>name</tags>
<tags>receive</tags>
<tags>happen</tags>
<tags>join</tags>
<views>46852</views>
<shares>763</shares>
</news_article>

[Assistant]
Approach:
1. Task: Convert news article from XML to JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "article_id": "ART-8221745",
  "headline": "Polarized zero administration support",
  "author": "Maria Johnson",
  "published": "2026-01-03T08:37:58.870132",
  "section": "Business",
  "content": "Would movement white military what them cup. Available remember control staff. None mean hundred PM.\nImprove wear produce price according. He method market computer TV strategy.\nBody into language. Which other hear they look some option.",
  "tags": [
    "environment",
    "name",
    "receive",
    "happen",
    "join"
  ],
  "views": 46852,
  "shares": 763
}


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Create a XML representation of customer review.

[Assistant]
Approach:
1. Task: Create customer review in XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-3836429</review_id>
<product_id>PROD-852988</product_id>
<user_id>39a3d2bd-fb84-4dfc-9cb6-45bd3ebddca0</user_id>
<rating>2</rating>
<title>Report thus get describe identify.</title>
<content>Or dog never any center population. Program it they Republican over step. Who television finish true game.
List catch candidate west research. Meeting many imagine.</content>
<date>2026-01-01</date>
<verified_purchase>False</verified_purchase>
<helpful_votes>23</helpful_votes>
</customer_review>


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Transform this XML data into JSON format:
<?xml version="1.0" encoding="UTF-8"?>
<social_media_post>
<post_id>POST-58559815</post_id>
<platform>instagram</platform>
<user_id>0fae79ab-dabb-47f5-823b-f22743181c7c</user_id>
<username>ortizkristina</username>
<content>Speech can sea play. Season near story animal remain.
Off present vote wall. Society know family build. Certain thing live rise.</content>
<timestamp>2026-01-07T13:51:26.463560</timestamp>
<hashtags>#once</hashtags>
<hashtags>#it</hashtags>
<hashtags>#rich</hashtags>
<hashtags>#keep</hashtags>
<engagement>
<likes>248</likes>
<shares>32</shares>
<comments>161</comments>
</engagement>
</social_media_post>

[Assistant]
Approach:
1. Task: Convert social media post from XML to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "post_id": "POST-58559815",
  "platform": "instagram",
  "user_id": "0fae79ab-dabb-47f5-823b-f22743181c7c",
  "username": "ortizkristina",
  "content": "Speech can sea play. Season near story animal remain.\nOff present vote wall. Society know family build. Certain thing live rise.",
  "timestamp": "2026-01-07T13:51:26.463560",
  "hashtags": [
    "#once",
    "#it",
    "#rich",
    "#keep"
  ],
  "engagement": {
    "likes": 248,
    "shares": 32,
    "comments": 161
  }
}


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Produce a XML document for a news article.

[Assistant]
Approach:
1. Task: Create news article in XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<news_article>
<article_id>ART-9178511</article_id>
<headline>Fully-configurable secondary access</headline>
<author>Gabrielle Daugherty</author>
<published>2026-01-05T07:34:40.744934</published>

Tech

<content>Lawyer might home mouth end so science. Hope attention strong public teach person beautiful though. Really decision land evening year.
Just role ground discover. Five stand writer floor.</content>
<tags>maybe</tags>
<tags>glass</tags>
<tags>election</tags>
<tags>moment</tags>
<views>24250</views>
<shares>778</shares>
</news_article>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "post_id": "POST-15490463",
  "platform": "instagram",
  "user_id": "dcf0c28f-6ad6-4153-873b-0cd39fa73a46",
  "username": "allenjames",
  "content": "Eight television free focus window leave. Education Democrat past music mother able. Fund season represent when analysis movement.\nEverything over rich serious forget. Fire particular western.",
  "timestamp": "2026-01-07T13:51:27.338072",
  "hashtags": [
    "#left",
    "#long",
    "#instead",
    "#budget"
  ],
  "engagement": {
    "likes": 85,
    "shares": 112,
    "comments": 292
  }
}

[Assistant]
Approach:
1. Task: Convert social media post from JSON to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<social_media_post>
<post_id>POST-15490463</post_id>
<platform>instagram</platform>
<user_id>dcf0c28f-6ad6-4153-873b-0cd39fa73a46</user_id>
<username>allenjames</username>
<content>Eight television free focus window leave. Education Democrat past music mother able. Fund season represent when analysis movement.
Everything over rich serious forget. Fire particular western.</content>
<timestamp>2026-01-07T13:51:27.338072</timestamp>
<hashtags>#left</hashtags>
<hashtags>#long</hashtags>
<hashtags>#instead</hashtags>
<hashtags>#budget</hashtags>
<engagement>
<likes>85</likes>
<shares>112</shares>
<comments>292</comments>
</engagement>
</social_media_post>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Produce a XML document for a course syllabus.

[Assistant]
Approach:
1. Task: Create course syllabus in XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<course_syllabus>
<course_id>CRS-6204</course_id>
WOR378
<title>Multi-channeled bi-directional implementation 101</title>
<instructor>Charlene Houston</instructor>
<credits>4</credits>
<term>Spring 2023</term>
<schedule>
<week>1</week>
<topic>under</topic>
</schedule>
<schedule>
<week>2</week>
<topic>trade</topic>
</schedule>
<schedule>
<week>3</week>
<topic>good</topic>
</schedule>
<schedule>
<week>4</week>
<topic>grow</topic>
</schedule>
<schedule>
<week>5</week>
<topic>ability</topic>
</schedule>
<schedule>
<week>6</week>
<topic>experience</topic>
</schedule>
<schedule>
<week>7</week>
<topic>offer</topic>
</schedule>
<schedule>
<week>8</week>
<topic>account</topic>
</schedule>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
</course_syllabus>


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Synchronized holistic archive API</title>
<version>1.0.0</version>
</info>
<paths>
</policy>
<get>
<summary>Red reason present loss yeah run.</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//policy>
</paths>
</api_specification>

[Assistant]
Approach:
1. Task: Convert api specification from XML to JSON
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Synchronized holistic archive API",
    "version": "1.0.0"
  },
  "paths": {
    "/policy": {
      "get": {
        "summary": "Red reason present loss yeah run.",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Produce a TOML document for a news article.

[Assistant]
Approach:
1. Task: Create news article in TOML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
article_id = "ART-4067367"
headline = "Polarized human-resource adapter"
author = "Kristin Larson"
published = "2026-01-07T00:05:34.405255"
section = "Business"
content = "Ahead effort author use. Unit together series provide arrive country off. Whether let thought down.\nEight audience power analysis. Age hope leader yeah without. Experience kitchen heart city."
tags = [ "program", "final", "computer", "live",]
views = 74807
shares = 3986


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Reformat the data below from JSON to XML:
{
  "assessment_id": "ASMT-554535",
  "student_id": "STU-693793",
  "course_id": "CRS-9992",
  "type": "exam",
  "date": "2026-01-03",
  "scores": [
    {
      "question": 1,
      "points_earned": 9,
      "points_possible": 10
    },
    {
      "question": 2,
      "points_earned": 6,
      "points_possible": 10
    },
    {
      "question": 3,
      "points_earned": 7,
      "points_possible": 10
    },
    {
      "question": 4,
      "points_earned": 6,
      "points_possible": 10
    },
    {
      "question": 5,
      "points_earned": 6,
      "points_possible": 10
    },
    {
      "question": 6,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 7,
      "points_earned": 4,
      "points_possible": 10
    },
    {
      "question": 8,
      "points_earned": 8,
      "points_possible": 10
    },
    {
      "question": 9,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 10,
      "points_earned": 3,
      "points_possible": 10
    }
  ],
  "total_score": 86,
  "percentage": 63.99,
  "grade": "B"
}

[Assistant]
Approach:
1. Task: Convert student assessment from JSON to XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<student_assessment>
<assessment_id>ASMT-554535</assessment_id>
<student_id>STU-693793</student_id>
<course_id>CRS-9992</course_id>
<type>exam</type>
<date>2026-01-03</date>
<scores>
<question>1</question>
<points_earned>9</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>2</question>
<points_earned>6</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>3</question>
<points_earned>7</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>4</question>
<points_earned>6</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>5</question>
<points_earned>6</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>6</question>
<points_earned>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>7</question>
<points_earned>4</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>8</question>
<points_earned>8</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>9</question>
<points_earned>2</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>10</question>
<points_earned>3</points_earned>
<points_possible>10</points_possible>
</scores>
<total_score>86</total_score>
<percentage>63.99</percentage>
<grade>B</grade>
</student_assessment>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Produce a XML document for a lab result.

[Assistant]
Approach:
1. Task: Create lab result in XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<lab_result>
<result_id>LAB-2309770</result_id>
<patient_mrn>MRN-380513</patient_mrn>
<order_date>2026-01-02</order_date>
<panel>CMP</panel>
<results>
<test>Glucose</test>
<value>62.8</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>141.2</value>
<unit>mg/dL</unit>
<flag>high</flag>
</results>
<results>
<test>WBC</test>
<value>75.4</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
<results>
<test>Glucose</test>
<value>174.6</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
<results>
<test>Glucose</test>
<value>170.1</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
</lab_result>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Convert the following JSON to XML:
{
  "total_score": 96,
  "percentage": 61.11,
  "student_id": "STU-785727"
}

[Assistant]
Approach:
1. Task: Convert student assessment from JSON to XML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<student_assessment>
<total_score>96</total_score>
<percentage>61.11</percentage>
<student_id>STU-785727</student_id>
</student_assessment>


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Create a JSON representation of news article.

[Assistant]
Approach:
1. Task: Create news article in JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "article_id": "ART-9178511",
  "headline": "Fully-configurable secondary access",
  "author": "Gabrielle Daugherty",
  "published": "2026-01-05T07:34:40.744934",
  "section": "Tech",
  "content": "Lawyer might home mouth end so science. Hope attention strong public teach person beautiful though. Really decision land evening year.\nJust role ground discover. Five stand writer floor.",
  "tags": [
    "maybe",
    "glass",
    "election",
    "moment"
  ],
  "views": 24250,
  "shares": 778
}


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Convert the following JSON to XML:
{
  "paper_id": "arXiv:2024.49729",
  "title": "Optimized fault-tolerant monitoring",
  "authors": [
    {
      "name": "Ashley Hubbard",
      "affiliation": "Mcdonald-White",
      "email": "jenniferlong@example.net"
    },
    {
      "name": "Erica Marshall",
      "affiliation": "Calderon-Dalton",
      "email": "adouglas@example.org"
    },
    {
      "name": "Mercedes Campbell",
      "affiliation": "Davis-Lynch",
      "email": "yharris@example.org"
    }
  ],
  "abstract": "Relate make read game soldier new. Agree south attorney one century drive draw.\nReduce head tax certainly offer deal. Sister station adult seat wear.",
  "keywords": [
    "gas",
    "understand",
    "everything",
    "miss"
  ],
  "publication": {
    "venue": "Cell",
    "year": 2024,
    "doi": "10.3465/hMKF"
  },
  "citations": 65,
  "funding_source": "Parsons Inc"
}

[Assistant]
Approach:
1. Task: Convert research paper from JSON to XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<paper_id>arXiv:2024.49729</paper_id>
<title>Optimized fault-tolerant monitoring</title>
<authors>
<name>Ashley Hubbard</name>
<affiliation>Mcdonald-White</affiliation>
<email>jenniferlong@example.net</email>
</authors>
<authors>
<name>Erica Marshall</name>
<affiliation>Calderon-Dalton</affiliation>
<email>adouglas@example.org</email>
</authors>
<authors>
<name>Mercedes Campbell</name>
<affiliation>Davis-Lynch</affiliation>
<email>yharris@example.org</email>
</authors>
<abstract>Relate make read game soldier new. Agree south attorney one century drive draw.
Reduce head tax certainly offer deal. Sister station adult seat wear.</abstract>
<keywords>gas</keywords>
<keywords>understand</keywords>
<keywords>everything</keywords>
<keywords>miss</keywords>
<publication>
<venue>Cell</venue>
<year>2024</year>
<doi>10.3465/hMKF</doi>
</publication>
<citations>65</citations>
<funding_source>Parsons Inc</funding_source>
</research_paper>


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User]
Transform this TOML data into YAML format:
rx_id = "RX-1795504"
patient_mrn = "MRN-355763"
prescriber = "Henry Padilla"
date = "2026-01-01"
[[medications]]
name = "Metformin"
dosage = "20mg"
frequency = "daily"
quantity = 90

[Assistant]
Approach:
1. Task: Convert prescription from TOML to YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
rx_id: RX-1795504
patient_mrn: MRN-355763
prescriber: Henry Padilla
date: '2026-01-01'
medications:
- name: Metformin
  dosage: 20mg
  frequency: daily
  quantity: 90


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Convert the following JSON to XML:
{
  "result_id": "LAB-8093004",
  "patient_mrn": "MRN-777027",
  "order_date": "2026-01-05",
  "panel": "CMP",
  "results": [
    {
      "test": "Glucose",
      "value": 140.2,
      "unit": "mg/dL",
      "flag": "low"
    },
    {
      "test": "Hemoglobin",
      "value": 96.3,
      "unit": "g/dL",
      "flag": "normal"
    },
    {
      "test": "Glucose",
      "value": 185.0,
      "unit": "g/dL",
      "flag": "high"
    },
    {
      "test": "Glucose",
      "value": 139.7,
      "unit": "g/dL",
      "flag": "low"
    }
  ]
}

[Assistant]
Approach:
1. Task: Convert lab result from JSON to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<lab_result>
<result_id>LAB-8093004</result_id>
<patient_mrn>MRN-777027</patient_mrn>
<order_date>2026-01-05</order_date>
<panel>CMP</panel>
<results>
<test>Glucose</test>
<value>140.2</value>
<unit>mg/dL</unit>
<flag>low</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>96.3</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Glucose</test>
<value>185.0</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Glucose</test>
<value>139.7</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
</lab_result>


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Convert the following CSV to JSON:
abstract,authors,citations,date,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,rating,title,user_id,verified_purchase
,,,2026-01-02,,,,,,,2,Nature prepare style hit cell feeling start societ,ccea0611-b57c-4ee0-9ab6-48c5cb4c2b4c,False
Accept ahead sport prevent. Picture tend military million prevent.,"[{""name"": ""Christopher Lloyd"", ""affiliation"": ""Gillespie, Trevino and Oneill"", ""email"": ""sheila83@ex",27,,None,"[""religious"", ""little"", ""herself"", ""court""]",arXiv:2021.64445,10.1337/Rytb,Nature,2020,,Assimilated national migration,,
Charge would cut major his which. Know trip third career analysis style anything notice.,"[{""name"": ""Tina Salas"", ""affiliation"": ""Miranda-Kramer"", ""email"": ""rachel93@example.net""}, {""name"": ",96,,Peterson-Chaney,"[""around"", ""improve"", ""people"", ""bed"", ""buy""]",arXiv:2023.61918,10.7893/Zaiy,Science,2024,,Multi-lateral transitional contingency,,
"Great wind quite nation. Case the thought company.
List leave let past none investment sing. Under f","[{""name"": ""Jamie Nolan"", ""affiliation"": ""Ballard, Wolf and Mills"", ""email"": ""taylorantonio@example.c",135,,Johnson Inc,"[""continue"", ""fight"", ""bit"", ""finally"", ""line""]",arXiv:2022.92534,10.6882/gcBb,Cell,2022,,Re-engineered stable definition,,
Range light born represent thing stand house. Stock investment reality street a. Move let maybe natu,"[{""name"": ""Lori Cruz"", ""affiliation"": ""Smith PLC"", ""email"": ""jeremybailey@example.org""}, {""name"": ""A",38,,None,"[""central"", ""affect"", ""part""]",arXiv:2024.62990,10.8384/EZzH,Cell,2022,,Open-source well-modulated Graphical User Interface,,

[Assistant]
Approach:
1. Task: Convert customer review from CSV to JSON
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "verified_purchase": false,
  "rating": 2,
  "date": "2026-01-02",
  "user_id": "ccea0611-b57c-4ee0-9ab6-48c5cb4c2b4c",
  "title": "Nature prepare style hit cell feeling start societ"
}


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Generate customer review data in CSV format.

[Assistant]
Approach:
1. Task: Create customer review in CSV
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
abstract,authors,citations,date,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,rating,title,user_id,verified_purchase
,,,2026-01-02,,,,,,,2,Nature prepare style hit cell feeling start societ,ccea0611-b57c-4ee0-9ab6-48c5cb4c2b4c,False
Show poor recently box form between. Them actually hear teacher energy stock. Wear gas how push argu,"[{""name"": ""Jennifer Hobbs"", ""affiliation"": ""Tucker Ltd"", ""email"": ""jacoblyons@example.org""}, {""name""",435,,None,"[""school"", ""suggest"", ""travel"", ""of""]",arXiv:2021.89149,10.5093/hvUq,Science,2021,,Focused object-oriented intranet,,
Without success middle. Green usually smile top. Offer front business why.,"[{""name"": ""James Mann"", ""affiliation"": ""Gilmore-Romero"", ""email"": ""colleen02@example.net""}, {""name"":",177,,None,"[""may"", ""language"", ""his"", ""officer"", ""now""]",arXiv:2020.63591,10.6408/hwDM,Cell,2023,,Up-sized secondary challenge,,


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "note_id": "CN-2804449",
  "patient": {
    "mrn": "MRN-394213",
    "age": 73,
    "gender": "F"
  },
  "encounter_date": "2026-01-04",
  "chief_complaint": "fever",
  "vitals": {
    "bp": "162/64",
    "hr": 70,
    "temp_f": 102.7
  },
  "assessment": [
    {
      "problem": "hypertension",
      "icd10": "K44"
    }
  ]
}

[Assistant]
Approach:
1. Task: Convert clinical note from JSON to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<clinical_note>
<note_id>CN-2804449</note_id>
<patient>
<mrn>MRN-394213</mrn>
<age>73</age>
<gender>F</gender>
</patient>
<encounter_date>2026-01-04</encounter_date>
<chief_complaint>fever</chief_complaint>
<vitals>
<bp>162/64</bp>

70

<temp_f>102.7</temp_f>
</vitals>
<assessment>
<problem>hypertension</problem>
<icd10>K44</icd10>
</assessment>
</clinical_note>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Reformat the data below from CSV to XML:
content,engagement_comments,engagement_likes,engagement_shares,hashtags,platform,post_id,timestamp,user_id,username
Eight television free focus window leave. Education Democrat past music mother able. Fund season rep,292,85,112,"[""#left"", ""#long"", ""#instead"", ""#budget""]",instagram,POST-15490463,2026-01-07T13:51:27.338072,dcf0c28f-6ad6-4153-873b-0cd39fa73a46,allenjames
"Thus able save machine now none. Relationship place add drop rich. House investment gas course.
Spac",368,7398,620,"[""#light"", ""#establish"", ""#whole""]",facebook,POST-18225843,2026-01-07T13:51:27.341153,552ff2f9-4f36-402a-9619-212b7a976c8a,patrickguerrero
Receive growth thousand lawyer. Without what build they find while. Relationship cost garden remembe,16,7607,797,"[""#attack"", ""#certainly"", ""#begin""]",instagram,POST-87286174,2026-01-07T13:51:27.341562,77dba8fd-6f18-49d3-9611-65b65abe03b7,kylelopez
"Keep not case room door choice. They operation ever that certain year.
Gun believe once. Upon provid",207,2673,328,"[""#player"", ""#ready"", ""#peace""]",twitter,POST-40881964,2026-01-07T13:51:27.341882,73b5fd6d-db20-4d37-a725-b427120c5c33,ytaylor
Board affect prepare suddenly spend. Hotel voice interest can. Inside matter tough ask politics nor ,211,7421,913,"[""#city"", ""#activity"", ""#whom""]",twitter,POST-72695378,2026-01-07T13:51:27.342163,d2e361b6-7113-4700-bf33-e925a99f46a2,ymiller

[Assistant]
Approach:
1. Task: Convert social media post from CSV to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<social_media_post>
<post_id>POST-15490463</post_id>
<platform>instagram</platform>
<user_id>dcf0c28f-6ad6-4153-873b-0cd39fa73a46</user_id>
<username>allenjames</username>
<content>Eight television free focus window leave. Education Democrat past music mother able. Fund season represent when analysis movement.
Everything over rich serious forget. Fire particular western.</content>
<timestamp>2026-01-07T13:51:27.338072</timestamp>
<hashtags>#left</hashtags>
<hashtags>#long</hashtags>
<hashtags>#instead</hashtags>
<hashtags>#budget</hashtags>
<engagement>
<likes>85</likes>
<shares>112</shares>
<comments>292</comments>
</engagement>
</social_media_post>


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Generate contract data in TOML format.

[Assistant]
Approach:
1. Task: Create contract in TOML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
contract_id = "CTR-299234"
effective_date = "2026-01-06"
term_months = 46
value = 506357
status = "pending"
[[parties]]
name = "Murphy, Hawkins and Mckenzie"
role = "party_a"

[[parties]]
name = "Collins-Miller"
role = "party_b"


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User]
Transform this YAML data into CSV format:
assessment_id: ASMT-871992
student_id: STU-916232
course_id: CRS-5865
type: quiz
date: '2026-01-05'
scores:
- question: 1
  points_earned: 1
  points_possible: 10
- question: 2
  points_earned: 6
  points_possible: 10
- question: 3
  points_earned: 10
  points_possible: 10
- question: 4
  points_earned: 2
  points_possible: 10
- question: 5
  points_earned: 5
  points_possible: 10
- question: 6
  points_earned: 5
  points_possible: 10
- question: 7
  points_earned: 0
  points_possible: 10
- question: 8
  points_earned: 7
  points_possible: 10
- question: 9
  points_earned: 2
  points_possible: 10
- question: 10
  points_earned: 4
  points_possible: 10
- question: 11
  points_earned: 5
  points_possible: 10
total_score: 83
percentage: 70.57
grade: B

[Assistant]
Approach:
1. Task: Convert student assessment from YAML to CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
assessment_id,code,course_id,credits,date,grade,grading_final,grading_homework,grading_midterm,instructor,percentage,schedule,scores,student_id,term,title,total_score,type
ASMT-871992,,CRS-5865,,2026-01-05,B,,,,,70.57,,"[{""question"": 1, ""points_earned"": 1, ""points_possible"": 10}, {""question"": 2, ""points_earned"": 6, ""po",STU-916232,,,83,quiz
,PXS273,CRS-9842,3,,,40,30,30,Nathan Diaz,,"[{""week"": 1, ""topic"": ""pay""}, {""week"": 2, ""topic"": ""a""}, {""week"": 3, ""topic"": ""rather""}, {""week"": 4,",,,Spring 2024,Enterprise-wide methodical methodology 101,,
,NYK472,CRS-9479,4,,,40,30,30,Joshua Ward,,"[{""week"": 1, ""topic"": ""believe""}, {""week"": 2, ""topic"": ""this""}, {""week"": 3, ""topic"": ""her""}, {""week""",,,Fall 2024,Digitized web-enabled website 101,,
,GHY107,CRS-5836,4,,,40,30,30,Lisa Miller,,"[{""week"": 1, ""topic"": ""nature""}, {""week"": 2, ""topic"": ""on""}, {""week"": 3, ""topic"": ""budget""}, {""week""",,,Fall 2022,Centralized client-server architecture 101,,
,WDQ343,CRS-6302,3,,,40,30,30,Aaron Hill,,"[{""week"": 1, ""topic"": ""move""}, {""week"": 2, ""topic"": ""drive""}, {""week"": 3, ""topic"": ""water""}, {""week""",,,Spring 2023,Public-key cohesive secured line 101,,


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Output customer review as XML.

[Assistant]
Approach:
1. Task: Create customer review in XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-2971879</review_id>
<product_id>PROD-601177</product_id>
<user_id>49ec79ac-cc63-409f-8812-a70c492b6835</user_id>
<rating>3</rating>
<title>Safe everything country understand subject.</title>
<content>Explain among above role speech. Hear law enjoy. Lose building fall everything million.
East choose however class dark test good contain. Indicate worker mean hot.</content>
<date>2026-01-06</date>
<verified_purchase>True</verified_purchase>
<helpful_votes>67</helpful_votes>
</customer_review>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Reformat the data below from JSON to XML:
{
  "period": "February 2020",
  "total_revenue": 2337421,
  "units_sold": 23839,
  "channels": [
    {
      "name": "retail",
      "revenue": 3840938,
      "growth": 18.52
    },
    {
      "name": "wholesale",
      "revenue": 1512471,
      "growth": 13.02
    }
  ],
  "top_products": [
    {
      "sku": "SKU-1744",
      "sales": 276633
    },
    {
      "sku": "SKU-5145",
      "sales": 26445
    },
    {
      "sku": "SKU-9218",
      "sales": 412054
    }
  ]
}

[Assistant]
Approach:
1. Task: Convert sales analytics from JSON to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<sales_analytics>
<period>February 2020</period>
<total_revenue>2337421</total_revenue>
<units_sold>23839</units_sold>
<channels>
<name>retail</name>
<revenue>3840938</revenue>
<growth>18.52</growth>
</channels>
<channels>
<name>wholesale</name>
<revenue>1512471</revenue>
<growth>13.02</growth>
</channels>
<top_products>
<sku>SKU-1744</sku>
<sales>276633</sales>
</top_products>
<top_products>
<sku>SKU-5145</sku>
<sales>26445</sales>
</top_products>
<top_products>
<sku>SKU-9218</sku>
<sales>412054</sales>
</top_products>
</sales_analytics>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Output lab result as XML.

[Assistant]
Approach:
1. Task: Create lab result in XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<lab_result>
<result_id>LAB-4827299</result_id>
<patient_mrn>MRN-871984</patient_mrn>
<order_date>2026-01-06</order_date>
<panel>Lipid</panel>
<results>
<test>WBC</test>
<value>156.4</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>WBC</test>
<value>186.0</value>
<unit>mg/dL</unit>
<flag>low</flag>
</results>
<results>
<test>WBC</test>
<value>134.8</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>WBC</test>
<value>64.1</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
</lab_result>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Face-to-face zero administration application API",
    "version": "1.0.0"
  },
  "paths": {
    "/peace": {
      "get": {
        "summary": "Feel piece low way effort action bag.",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param2",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}

[Assistant]
Approach:
1. Task: Convert api specification from JSON to XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Face-to-face zero administration application API</title>
<version>1.0.0</version>
</info>
<paths>
</peace>
<get>
<summary>Feel piece low way effort action bag.</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<parameters>
<name>param1</name>
<in>query</in>
<type>string</type>
</parameters>
<parameters>
<name>param2</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//peace>
</paths>
</api_specification>


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Create a JSON representation of course syllabus.

[Assistant]
Approach:
1. Task: Create course syllabus in JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "course_id": "CRS-9456",
  "code": "KDS432",
  "title": "Multi-channeled local complexity 101",
  "instructor": "Kenneth Rogers",
  "credits": 3,
  "term": "Fall 2020",
  "schedule": [
    {
      "week": 1,
      "topic": "activity"
    },
    {
      "week": 2,
      "topic": "foot"
    },
    {
      "week": 3,
      "topic": "reason"
    },
    {
      "week": 4,
      "topic": "rule"
    },
    {
      "week": 5,
      "topic": "paper"
    },
    {
      "week": 6,
      "topic": "current"
    },
    {
      "week": 7,
      "topic": "scene"
    },
    {
      "week": 8,
      "topic": "later"
    },
    {
      "week": 9,
      "topic": "choice"
    },
    {
      "week": 10,
      "topic": "box"
    }
  ],
  "grading": {
    "homework": 30,
    "midterm": 30,
    "final": 40
  }
}


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Output news article as JSON.

[Assistant]
Approach:
1. Task: Create news article in JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "article_id": "ART-5347545",
  "headline": "Triple-buffered zero administration algorithm",
  "author": "Martha Brown",
  "published": "2026-01-05T16:28:34.342789",
  "section": "Sports",
  "content": "Have fall sing then fast research break. Bar ready eye medical school might recognize. Nice sometimes impact point white.\nTake many this never ever trip. Specific call according. We argue person federal central each.",
  "tags": [
    "line",
    "true",
    "compare",
    "for"
  ],
  "views": 96946,
  "shares": 1479
}


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Output course syllabus as TOML.

[Assistant]
Approach:
1. Task: Create course syllabus in TOML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
course_id = "CRS-5570"
code = "ZMD258"
title = "Mandatory leadingedge superstructure 101"
instructor = "Gregory Dunn"
credits = 3
term = "Spring 2021"
[[schedule]]
week = 1
topic = "guess"

[[schedule]]
week = 2
topic = "forget"

[[schedule]]
week = 3
topic = "technology"

[[schedule]]
week = 4
topic = "nothing"

[[schedule]]
week = 5
topic = "sea"

[[schedule]]
week = 6
topic = "other"

[[schedule]]
week = 7
topic = "new"

[[schedule]]
week = 8
topic = "report"

[[schedule]]
week = 9
topic = "guy"

[[schedule]]
week = 10
topic = "can"

[[schedule]]
week = 11
topic = "inside"

[grading]
homework = 30
midterm = 30
final = 40


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Create a CSV representation of prescription.

[Assistant]
Approach:
1. Task: Create prescription in CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
date,medications,patient_mrn,prescriber,rx_id
2026-01-01,"[{""name"": ""Lisinopril"", ""dosage"": ""20mg"", ""frequency"": ""TID"", ""quantity"": 60}, {""name"": ""Metformin"",",MRN-615844,Brian Erickson,RX-5973418
2026-01-04,"[{""name"": ""Atorvastatin"", ""dosage"": ""5mg"", ""frequency"": ""daily"", ""quantity"": 60}]",MRN-217960,Christopher Aguirre,RX-2027791
2026-01-04,"[{""name"": ""Lisinopril"", ""dosage"": ""20mg"", ""frequency"": ""BID"", ""quantity"": 30}]",MRN-735709,Candace Moss,RX-1363951


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<contract>
<contract_id>CTR-313579</contract_id>
<parties>
<name>Roberts, Newton and Ortiz</name>
<role>party_a</role>
</parties>
<parties>
<name>Garcia PLC</name>
<role>party_b</role>
</parties>
<effective_date>2026-01-01</effective_date>
<term_months>55</term_months>
<value>108642</value>
<status>active</status>
</contract>

[Assistant]
Approach:
1. Task: Convert contract from XML to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "contract_id": "CTR-313579",
  "parties": [
    {
      "name": "Roberts, Newton and Ortiz",
      "role": "party_a"
    },
    {
      "name": "Garcia PLC",
      "role": "party_b"
    }
  ],
  "effective_date": "2026-01-01",
  "term_months": 55,
  "value": 108642,
  "status": "active"
}


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Produce a TOML document for a contract.

[Assistant]
Approach:
1. Task: Create contract in TOML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
contract_id = "CTR-464030"
effective_date = "2026-01-06"
term_months = 35
value = 994957
status = "active"
[[parties]]
name = "Morales, Williams and Williams"
role = "party_a"

[[parties]]
name = "Ward-Miller"
role = "party_b"


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<info>
<title>Object-based multimedia secured line API</title>
<version>1.0.0</version>
</info>
<openapi>3.0.0</openapi>
<paths>
</party>
<get>
<summary>Discussion partner stay wear again.</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<parameters>
<name>param1</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//party>
</paths>
</api_specification>

[Assistant]
Approach:
1. Task: Convert api specification from XML to JSON
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "info": {
    "title": "Object-based multimedia secured line API",
    "version": "1.0.0"
  },
  "openapi": "3.0.0",
  "paths": {
    "/party": {
      "get": {
        "summary": "Discussion partner stay wear again.",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this TOML data into XML format:
experiment_id = "EXP-956799"
title = "Effect of town on start"
conclusion = "significant"
[[results]]
metric = "efficacy"
baseline = 84.98
endpoint = 18.54
p_value = 0.3765

[[results]]
metric = "safety"
baseline = 50.71
endpoint = 79.49
p_value = 0.1783

[[results]]
metric = "safety"
baseline = 22.25
endpoint = 81.5
p_value = 0.0959

[[results]]
metric = "efficacy"
baseline = 53.32
endpoint = 58.41
p_value = 0.1807

[methodology]
design = "RCT"
sample_size = 962
duration_days = 355

[Assistant]
Approach:
1. Task: Convert experiment result from TOML to XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<experiment_result>
<experiment_id>EXP-956799</experiment_id>
<title>Effect of town on start</title>
<methodology>
<design>RCT</design>
<sample_size>962</sample_size>
<duration_days>355</duration_days>
</methodology>
<results>
<metric>efficacy</metric>
<baseline>84.98</baseline>
<endpoint>18.54</endpoint>
<p_value>0.3765</p_value>
</results>
<results>
<metric>safety</metric>
<baseline>50.71</baseline>
<endpoint>79.49</endpoint>
<p_value>0.1783</p_value>
</results>
<results>
<metric>safety</metric>
<baseline>22.25</baseline>
<endpoint>81.5</endpoint>
<p_value>0.0959</p_value>
</results>
<results>
<metric>efficacy</metric>
<baseline>53.32</baseline>
<endpoint>58.41</endpoint>
<p_value>0.1807</p_value>
</results>
<conclusion>significant</conclusion>
</experiment_result>


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Generate error log data in CSV format.

[Assistant]
Approach:
1. Task: Create error log in CSV
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
abstract,authors,citations,context_request_id,context_user_id,error_id,funding_source,keywords,level,paper_id,publication_doi,publication_venue,publication_year,service,stack_trace,title
,,,7878bb2d-6319-4d97-8924-bd0357b0788d,fe05329e-c851-4258-9b5b-a5822613303b,d3f1548e-3d70-475b-a25a-df504add1be1,,,WARNING,,,,,approachService,"[""at level.py:451"", ""at science.py:176"", ""at art.py:498"", ""at success.py:287""]",
Maintain actually building any professional. Participant which relationship do.,"[{""name"": ""Traci White"", ""affiliation"": ""Scott, Curry and Hernandez"", ""email"": ""alexjordan@example.o",94,,,,None,"[""until"", ""behind"", ""ok"", ""put""]",,arXiv:2020.92507,10.4038/PWOx,Science,2022,,,Self-enabling web-enabled capacity
People itself already couple property huge hear. Camera would couple project thus control tend.,"[{""name"": ""Dr. David Smith"", ""affiliation"": ""Romero, Cruz and Montoya"", ""email"": ""marynunez@example.",340,,,,None,"[""serve"", ""collection"", ""fear""]",,arXiv:2023.71084,10.4443/ZiSL,Cell,2022,,,Synergized upward-trending implementation
Range foreign wife. Sure camera return ten deep detail. Enter skin long travel next determine.,"[{""name"": ""Leslie Ramos"", ""affiliation"": ""Collins, Strickland and Bennett"", ""email"": ""robert66@examp",161,,,,None,"[""avoid"", ""director"", ""everybody""]",,arXiv:2020.64953,10.2629/OAyN,Cell,2020,,,Stand-alone intermediate ability


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Generate transaction record data in CSV format.

[Assistant]
Approach:
1. Task: Create transaction record in CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
customer_id,items,payment_method,subtotal,tax,timestamp,total,txn_id
ea7970e3-49c7-4d3a-bbe0-6c539dc6c3d3,"[{""sku"": ""SKU-22630"", ""qty"": 3, ""price"": 89.97}]",apple_pay,468.67,148.91,2026-01-07T13:51:25.620781,792.01,TXN-85338602
78b51b42-a2be-43a2-9454-6b50242d9c2d,"[{""sku"": ""SKU-30772"", ""qty"": 1, ""price"": 433.94}, {""sku"": ""SKU-13007"", ""qty"": 3, ""price"": 423.0}, {""",paypal,211.21,173.17,2026-01-07T13:51:25.621593,223.82,TXN-79561512
579478ee-8bb7-4b9b-97da-940734632127,"[{""sku"": ""SKU-46280"", ""qty"": 2, ""price"": 432.15}]",paypal,1492.88,12.2,2026-01-07T13:51:25.621664,199.6,TXN-91528573


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User]
Convert the following YAML to CSV:
product_id: PROD-842353
name: Synergistic bottom-line conglomeration
category: books
price: 609.49
currency: USD
stock: 399
is_available: true
rating: 1.05
reviews: 570
specs:
  weight_kg: 25.04
  dimensions: 30x19x82cm

[Assistant]
Approach:
1. Task: Convert product listing from YAML to CSV
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
category,currency,is_available,name,price,product_id,rating,reviews,specs_dimensions,specs_weight_kg,stock
books,USD,True,Synergistic bottom-line conglomeration,609.49,PROD-842353,1.05,570,30x19x82cm,25.04,399
books,USD,True,Streamlined even-keeled support,550.44,PROD-248653,4.03,512,27x88x63cm,12.76,898
electronics,USD,True,User-centric explicit capacity,460.36,PROD-502929,1.34,122,94x22x84cm,46.39,564
books,USD,True,Robust multimedia Graphic Interface,267.69,PROD-103100,4.94,360,14x29x27cm,3.82,398


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Output contract as XML.

[Assistant]
Approach:
1. Task: Create contract in XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<contract>
<contract_id>CTR-291572</contract_id>
<parties>
<name>Smith and Sons</name>
<role>party_a</role>
</parties>
<parties>
<name>Avila-Campbell</name>
<role>party_b</role>
</parties>
<effective_date>2026-01-03</effective_date>
<term_months>47</term_months>
<value>297446</value>
<status>pending</status>
</contract>


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User]
Transform this JSON data into TOML format:
{
  "section": "Politics",
  "tags": [
    "machine",
    "fund",
    "station",
    "our"
  ],
  "published": "2026-01-05T17:58:55.100855",
  "views": 86295
}

[Assistant]
Approach:
1. Task: Convert news article from JSON to TOML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
section = "Politics"
tags = [ "machine", "fund", "station", "our",]
published = "2026-01-05T17:58:55.100855"
views = 86295


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "rx_id": "RX-3684509",
  "patient_mrn": "MRN-644382",
  "prescriber": "Chelsea Henson",
  "date": "2026-01-04",
  "medications": [
    {
      "name": "Atorvastatin",
      "dosage": "10mg",
      "frequency": "BID",
      "quantity": 60
    },
    {
      "name": "Metformin",
      "dosage": "20mg",
      "frequency": "daily",
      "quantity": 60
    },
    {
      "name": "Metformin",
      "dosage": "10mg",
      "frequency": "TID",
      "quantity": 60
    }
  ]
}

[Assistant]
Approach:
1. Task: Convert prescription from JSON to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<prescription>
<rx_id>RX-3684509</rx_id>
<patient_mrn>MRN-644382</patient_mrn>
<prescriber>Chelsea Henson</prescriber>
<date>2026-01-04</date>
<medications>
<name>Atorvastatin</name>
<dosage>10mg</dosage>
<frequency>BID</frequency>
<quantity>60</quantity>
</medications>
<medications>
<name>Metformin</name>
<dosage>20mg</dosage>
<frequency>daily</frequency>
<quantity>60</quantity>
</medications>
<medications>
<name>Metformin</name>
<dosage>10mg</dosage>
<frequency>TID</frequency>
<quantity>60</quantity>
</medications>
</prescription>


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Generate lab result data in CSV format.

[Assistant]
Approach:
1. Task: Create lab result in CSV
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
order_date,panel,patient_mrn,result_id,results
2026-01-02,CBC,MRN-135092,LAB-9224780,"[{""test"": ""Hemoglobin"", ""value"": 129.6, ""unit"": ""g/dL"", ""flag"": ""low""}, {""test"": ""Hemoglobin"", ""valu"
2026-01-06,CMP,MRN-209213,LAB-3202698,"[{""test"": ""Glucose"", ""value"": 99.2, ""unit"": ""g/dL"", ""flag"": ""low""}, {""test"": ""Glucose"", ""value"": 101"
2026-01-02,Lipid,MRN-586634,LAB-9158332,"[{""test"": ""WBC"", ""value"": 83.9, ""unit"": ""mg/dL"", ""flag"": ""normal""}, {""test"": ""WBC"", ""value"": 176.6, "
2026-01-04,CMP,MRN-885800,LAB-1109442,"[{""test"": ""Hemoglobin"", ""value"": 95.3, ""unit"": ""g/dL"", ""flag"": ""low""}, {""test"": ""Glucose"", ""value"": "
2026-01-01,CMP,MRN-998957,LAB-1688991,"[{""test"": ""Hemoglobin"", ""value"": 150.3, ""unit"": ""mg/dL"", ""flag"": ""low""}, {""test"": ""WBC"", ""value"": 50"


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Reformat the data below from JSON to XML:
{
  "article_id": "ART-8668047",
  "headline": "Seamless local alliance",
  "author": "Alyssa Moore",
  "published": "2026-01-02T06:22:52.413807",
  "section": "Business",
  "content": "Billion up year window similar. Oil two resource next. If this tough pattern.\nRule year push international.\nReceive charge movie remember hear theory stuff explain. Century animal decide everyone direction rather. Month property rock environment fine such hand remain.",
  "tags": [
    "traditional",
    "wish",
    "little",
    "inside",
    "year"
  ],
  "views": 55093,
  "shares": 3713
}

[Assistant]
Approach:
1. Task: Convert news article from JSON to XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<news_article>
<article_id>ART-8668047</article_id>
<headline>Seamless local alliance</headline>
<author>Alyssa Moore</author>
<published>2026-01-02T06:22:52.413807</published>

Business

<content>Billion up year window similar. Oil two resource next. If this tough pattern.
Rule year push international.
Receive charge movie remember hear theory stuff explain. Century animal decide everyone direction rather. Month property rock environment fine such hand remain.</content>
<tags>traditional</tags>
<tags>wish</tags>
<tags>little</tags>
<tags>inside</tags>
<tags>year</tags>
<views>55093</views>
<shares>3713</shares>
</news_article>


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Produce a CSV document for a clinical note.

[Assistant]
Approach:
1. Task: Create clinical note in CSV
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
assessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f
"[{""problem"": ""hypertension"", ""icd10"": ""K99""}]",chest pain,2026-01-02,CN-9595817,32,F,MRN-972408,102/103,113,102.5
"[{""problem"": ""hypertension"", ""icd10"": ""J69""}, {""problem"": ""hypertension"", ""icd10"": ""J29""}]",fever,2026-01-02,CN-4219593,77,M,MRN-157175,141/89,118,102.9
"[{""problem"": ""diabetes"", ""icd10"": ""K83""}, {""problem"": ""diabetes"", ""icd10"": ""I98""}, {""problem"": ""hype",headache,2026-01-04,CN-8116673,64,F,MRN-988441,122/63,93,97.3


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Generate customer review data in TOML format.

[Assistant]
Approach:
1. Task: Create customer review in TOML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
date = "2026-01-05"
title = "Teach why painting per short."
rating = 4


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-1369973</review_id>
<product_id>PROD-861575</product_id>
<user_id>a55bb48c-5dcb-464a-b952-9d377a4cb9c4</user_id>
<rating>1</rating>
<title>Relationship job find one allow law through.</title>
<content>Now decide senior fact big window yourself. Difference appear seat coach rather once politics. Modern always able physical Republican best draw land.</content>
<date>2026-01-02</date>
<verified_purchase>True</verified_purchase>
<helpful_votes>8</helpful_votes>
</customer_review>

[Assistant]
Approach:
1. Task: Convert customer review from XML to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "review_id": "REV-1369973",
  "product_id": "PROD-861575",
  "user_id": "a55bb48c-5dcb-464a-b952-9d377a4cb9c4",
  "rating": 1,
  "title": "Relationship job find one allow law through.",
  "content": "Now decide senior fact big window yourself. Difference appear seat coach rather once politics. Modern always able physical Republican best draw land.",
  "date": "2026-01-02",
  "verified_purchase": true,
  "helpful_votes": 8
}


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Generate course syllabus data in TOML format.

[Assistant]
Approach:
1. Task: Create course syllabus in TOML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
course_id = "CRS-9279"
code = "WQT213"
title = "Ameliorated 3rdgeneration groupware 101"
instructor = "Mariah Wilson"
credits = 3
term = "Fall 2020"
[[schedule]]
week = 1
topic = "together"

[[schedule]]
week = 2
topic = "statement"

[[schedule]]
week = 3
topic = "these"

[[schedule]]
week = 4
topic = "American"

[[schedule]]
week = 5
topic = "read"

[[schedule]]
week = 6
topic = "age"

[[schedule]]
week = 7
topic = "course"

[grading]
homework = 30
midterm = 30
final = 40


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Produce a YAML document for a clinical note.

[Assistant]
Approach:
1. Task: Create clinical note in YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
note_id: CN-9595817
patient:
  mrn: MRN-972408
  age: 32
  gender: F
encounter_date: '2026-01-02'
chief_complaint: chest pain
vitals:
  bp: 102/103
  hr: 113
  temp_f: 102.5
assessment:
- problem: hypertension
  icd10: K99


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User]
Reformat the data below from TOML to YAML:
error_id = "69ef512f-ddd4-415a-b99a-51e8f50d151c"
timestamp = "2026-01-07T13:51:25.644182"
level = "WARNING"
service = "fillService"
message = "Minute heart focus arrive."
stack_trace = [ "at administration.py:211", "at lawyer.py:276", "at discussion.py:115",]

[context]
user_id = "29c6c678-1224-4e33-8bc1-e94776cd4eb2"
request_id = "42e054d1-48f9-4a1c-ad7b-82ed505d6250"

[Assistant]
Approach:
1. Task: Convert error log from TOML to YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
error_id: 69ef512f-ddd4-415a-b99a-51e8f50d151c
timestamp: '2026-01-07T13:51:25.644182'
level: WARNING
service: fillService
message: Minute heart focus arrive.
stack_trace:
- at administration.py:211
- at lawyer.py:276
- at discussion.py:115
context:
  user_id: 29c6c678-1224-4e33-8bc1-e94776cd4eb2
  request_id: 42e054d1-48f9-4a1c-ad7b-82ed505d6250


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Create a XML representation of financial report.

[Assistant]
Approach:
1. Task: Create financial report in XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<financial_report>
<company>Becker-Martinez</company>
<ticker>QZXR</ticker>
<quarter>Q4 2021</quarter>
<revenue>48919598</revenue>
<expenses>50274851</expenses>
<net_income>7284021</net_income>
<eps>2.39</eps>
<metrics>
<profit_margin>17.0</profit_margin>
<roe>10.6</roe>
</metrics>
</financial_report>


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<prescription>
<rx_id>RX-9442688</rx_id>
<patient_mrn>MRN-277514</patient_mrn>
<prescriber>Timothy Goodman</prescriber>
<date>2026-01-04</date>
<medications>
<name>Metformin</name>
<dosage>20mg</dosage>
<frequency>TID</frequency>
<quantity>30</quantity>
</medications>
<medications>
<name>Metformin</name>
<dosage>5mg</dosage>
<frequency>BID</frequency>
<quantity>30</quantity>
</medications>
<medications>
<name>Lisinopril</name>
<dosage>5mg</dosage>
<frequency>TID</frequency>
<quantity>30</quantity>
</medications>
</prescription>

[Assistant]
Approach:
1. Task: Convert prescription from XML to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "rx_id": "RX-9442688",
  "patient_mrn": "MRN-277514",
  "prescriber": "Timothy Goodman",
  "date": "2026-01-04",
  "medications": [
    {
      "name": "Metformin",
      "dosage": "20mg",
      "frequency": "TID",
      "quantity": 30
    },
    {
      "name": "Metformin",
      "dosage": "5mg",
      "frequency": "BID",
      "quantity": 30
    },
    {
      "name": "Lisinopril",
      "dosage": "5mg",
      "frequency": "TID",
      "quantity": 30
    }
  ]
}


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Generate api specification data in YAML format.

[Assistant]
Approach:
1. Task: Create api specification in YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
openapi: 3.0.0
info:
  title: Pre-emptive interactive encryption API
  version: 1.0.0
paths:
  /air:
    get:
      summary: Final democratic whatever event director guy.
      parameters:
      - name: param0
        in: query
        type: string
      responses:
        '200':
          description: Success
        '400':
          description: Bad Request


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Reformat the data below from JSON to XML:
{
  "contract_id": "CTR-143990",
  "parties": [
    {
      "name": "Brady Inc",
      "role": "party_a"
    },
    {
      "name": "Gonzalez, Coleman and Sanchez",
      "role": "party_b"
    }
  ],
  "effective_date": "2026-01-02",
  "term_months": 32,
  "value": 452000,
  "status": "active"
}

[Assistant]
Approach:
1. Task: Convert contract from JSON to XML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<contract>
<contract_id>CTR-143990</contract_id>
<parties>
<name>Brady Inc</name>
<role>party_a</role>
</parties>
<parties>
<name>Gonzalez, Coleman and Sanchez</name>
<role>party_b</role>
</parties>
<effective_date>2026-01-02</effective_date>
<term_months>32</term_months>
<value>452000</value>
<status>active</status>
</contract>


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Create a XML representation of experiment result.

[Assistant]
Approach:
1. Task: Create experiment result in XML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<experiment_result>
<title>Effect of main on stand</title>
<results>
<metric>efficacy</metric>
<baseline>50.39</baseline>
<endpoint>61.09</endpoint>
<p_value>0.3936</p_value>
</results>
<results>
<metric>safety</metric>
<baseline>99.02</baseline>
<endpoint>82.38</endpoint>
<p_value>0.0752</p_value>
</results>
<results>
<metric>efficacy</metric>
<baseline>94.16</baseline>
<endpoint>58.56</endpoint>
<p_value>0.1239</p_value>
</results>
<results>
<metric>safety</metric>
<baseline>41.74</baseline>
<endpoint>45.99</endpoint>
<p_value>0.0661</p_value>
</results>
<experiment_id>EXP-681166</experiment_id>
<methodology>
<design>RCT</design>
<sample_size>875</sample_size>
<duration_days>212</duration_days>
</methodology>
<conclusion>non-significant</conclusion>
</experiment_result>


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Output student assessment as JSON.

[Assistant]
Approach:
1. Task: Create student assessment in JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "assessment_id": "ASMT-893180",
  "student_id": "STU-881633",
  "course_id": "CRS-6394",
  "type": "quiz",
  "date": "2026-01-03",
  "scores": [
    {
      "question": 1,
      "points_earned": 10,
      "points_possible": 10
    },
    {
      "question": 2,
      "points_earned": 8,
      "points_possible": 10
    },
    {
      "question": 3,
      "points_earned": 10,
      "points_possible": 10
    },
    {
      "question": 4,
      "points_earned": 6,
      "points_possible": 10
    },
    {
      "question": 5,
      "points_earned": 4,
      "points_possible": 10
    },
    {
      "question": 6,
      "points_earned": 6,
      "points_possible": 10
    },
    {
      "question": 7,
      "points_earned": 0,
      "points_possible": 10
    },
    {
      "question": 8,
      "points_earned": 10,
      "points_possible": 10
    },
    {
      "question": 9,
      "points_earned": 5,
      "points_possible": 10
    }
  ],
  "total_score": 98,
  "percentage": 73.06,
  "grade": "A"
}


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Produce a JSON document for a customer review.

[Assistant]
Approach:
1. Task: Create customer review in JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "review_id": "REV-7250124",
  "product_id": "PROD-375265",
  "user_id": "48302d32-0445-4405-afc6-604ef6300782",
  "rating": 1,
  "title": "Very responsibility coach economy sea public you.",
  "content": "Chair painting shake city kind good though. Find reality water support key.\nFly party couple production fight. Live attention anyone her traditional. I room blood condition research fund model.",
  "date": "2026-01-03",
  "verified_purchase": true,
  "helpful_votes": 78
}


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Transform this XML data into JSON format:
<?xml version="1.0" encoding="UTF-8"?>
<error_log>
<error_id>6b141850-4372-44c1-8cf7-fc47780a5017</error_id>
<timestamp>2026-01-07T13:51:26.727039</timestamp>
<level>WARNING</level>
<service>fullService</service>
<message>Simply human maintain sport.</message>
<stack_trace>at environmental.py:351</stack_trace>
<stack_trace>at develop.py:28</stack_trace>
<stack_trace>at send.py:431</stack_trace>
<context>
<user_id>fad7b695-3fb8-4313-ad8d-c2b1d4034196</user_id>
<request_id>2ca5c81e-d6c8-42a4-9e09-9715e928fe91</request_id>
</context>
</error_log>

[Assistant]
Approach:
1. Task: Convert error log from XML to JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "error_id": "6b141850-4372-44c1-8cf7-fc47780a5017",
  "timestamp": "2026-01-07T13:51:26.727039",
  "level": "WARNING",
  "service": "fullService",
  "message": "Simply human maintain sport.",
  "stack_trace": [
    "at environmental.py:351",
    "at develop.py:28",
    "at send.py:431"
  ],
  "context": {
    "user_id": "fad7b695-3fb8-4313-ad8d-c2b1d4034196",
    "request_id": "2ca5c81e-d6c8-42a4-9e09-9715e928fe91"
  }
}


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Generate course syllabus data in JSON format.

[Assistant]
Approach:
1. Task: Create course syllabus in JSON
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "course_id": "CRS-6873",
  "code": "GDK183",
  "title": "Grass-roots 24/7 emulation 101",
  "instructor": "Melinda Thompson",
  "credits": 3,
  "term": "Fall 2020",
  "schedule": [
    {
      "week": 1,
      "topic": "girl"
    },
    {
      "week": 2,
      "topic": "explain"
    },
    {
      "week": 3,
      "topic": "center"
    },
    {
      "week": 4,
      "topic": "almost"
    },
    {
      "week": 5,
      "topic": "property"
    },
    {
      "week": 6,
      "topic": "call"
    },
    {
      "week": 7,
      "topic": "bad"
    },
    {
      "week": 8,
      "topic": "study"
    },
    {
      "week": 9,
      "topic": "campaign"
    },
    {
      "week": 10,
      "topic": "performance"
    },
    {
      "week": 11,
      "topic": "sport"
    }
  ],
  "grading": {
    "homework": 30,
    "midterm": 30,
    "final": 40
  }
}


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Generate contract data in CSV format.

[Assistant]
Approach:
1. Task: Create contract in CSV
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
contract_id,effective_date,parties,status,term_months,value
CTR-926700,2026-01-04,"[{""name"": ""Kelly-Jackson"", ""role"": ""party_a""}, {""name"": ""Ramos, Hampton and Hartman"", ""role"": ""party",pending,36,178791
CTR-152149,2026-01-06,"[{""name"": ""Diaz, Phillips and Flores"", ""role"": ""party_a""}, {""name"": ""Huang, Hernandez and Gibson"", """,pending,32,98801
CTR-434049,2026-01-06,"[{""name"": ""Morgan, Moran and Phillips"", ""role"": ""party_a""}, {""name"": ""Gardner, Miller and Weber"", ""r",executed,44,289948
CTR-573790,2026-01-06,"[{""name"": ""Salazar Group"", ""role"": ""party_a""}, {""name"": ""Haynes, Smith and Randolph"", ""role"": ""party",pending,53,488317


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User]
Transform this CSV data into TOML format:
abstract,authors,citations,funding_source,keywords,order_date,panel,paper_id,publication_doi,publication_venue,publication_year,results,title
,,,,,2026-01-05,Lipid,,,,,"[{""test"": ""Hemoglobin"", ""value"": 95.5, ""unit"": ""g/dL"", ""flag"": ""low""}, {""test"": ""Hemoglobin"", ""value",
Story at idea minute under boy enough. Information decision Democrat approach rather north computer.,"[{""name"": ""Miss Courtney Howard"", ""affiliation"": ""Graham Ltd"", ""email"": ""alan83@example.com""}, {""nam",203,None,"[""attack"", ""power"", ""especially""]",,,arXiv:2022.74336,10.1216/made,Science,2024,,Balanced high-level function
Know sing black matter husband low fall. Worker fire explain step although manage. Truth sport somet,"[{""name"": ""Margaret Shaw"", ""affiliation"": ""Bartlett LLC"", ""email"": ""rtaylor@example.org""}, {""name"": ",174,Cole PLC,"[""Congress"", ""board"", ""air"", ""account"", ""recently""]",,,arXiv:2024.51320,10.9291/hfYq,Nature,2024,,Inverse radical protocol

[Assistant]
Approach:
1. Task: Convert lab result from CSV to TOML
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
order_date = "2026-01-05"
panel = "Lipid"
[[results]]
test = "Hemoglobin"
value = 95.5
unit = "g/dL"
flag = "low"

[[results]]
test = "Hemoglobin"
value = 52.7
unit = "mg/dL"
flag = "high"

[[results]]
test = "Glucose"
value = 142.9
unit = "mg/dL"
flag = "low"

[[results]]
test = "Glucose"
value = 146.5
unit = "mg/dL"
flag = "high"


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Output customer review as CSV.

[Assistant]
Approach:
1. Task: Create customer review in CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
category,content,currency,date,helpful_votes,is_available,name,price,product_id,rating,review_id,reviews,specs_dimensions,specs_weight_kg,stock,title,user_id,verified_purchase
,"Explain among above role speech. Hear law enjoy. Lose building fall everything million.
East choose ",,2026-01-06,67,,,,PROD-601177,3,REV-2971879,,,,,Safe everything country understand subject.,49ec79ac-cc63-409f-8812-a70c492b6835,True
books,,USD,,,True,Virtual systemic artificial intelligence,461.95,PROD-845120,4.27,,554,71x75x17cm,21.94,416,,,
books,,USD,,,True,Profit-focused asymmetric methodology,167.66,PROD-848049,2.31,,135,28x12x36cm,5.16,200,,,
clothing,,USD,,,True,Visionary context-sensitive moratorium,37.28,PROD-307786,3.15,,199,28x58x82cm,36.29,111,,,
clothing,,USD,,,True,Configurable responsive adapter,608.27,PROD-489988,1.82,,588,50x97x89cm,7.39,121,,,


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User]
Reformat the data below from XML to CSV:
<?xml version="1.0" encoding="UTF-8"?>
<financial_report>
<company>Eaton, Mccarty and Lopez</company>
<ticker>OWKB</ticker>
<quarter>Q3 2021</quarter>
<revenue>46227283</revenue>
<expenses>75330506</expenses>
<net_income>13309525</net_income>
<eps>4.82</eps>
<metrics>
<profit_margin>29.61</profit_margin>
<roe>8.93</roe>
</metrics>
</financial_report>

[Assistant]
Approach:
1. Task: Convert financial report from XML to CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
company,eps,expenses,metrics_profit_margin,metrics_roe,net_income,quarter,revenue,ticker
"Eaton, Mccarty and Lopez",4.82,75330506,29.61,8.93,13309525,Q3 2021,46227283,OWKB
Sanchez Inc,4.74,58441411,29.83,5.08,65126,Q3 2021,37226250,PRWM
Lewis Group,6.85,73441672,21.63,10.87,3637568,Q1 2020,69694011,MCOL
Sanders PLC,4.65,44335230,16.26,24.04,11730886,Q1 2020,9836497,MUVK


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Produce a TOML document for a experiment result.

[Assistant]
Approach:
1. Task: Create experiment result in TOML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
experiment_id = "EXP-942720"
title = "Effect of edge on when"
conclusion = "non-significant"
[[results]]
metric = "safety"
baseline = 79.64
endpoint = 26.86
p_value = 0.2863

[[results]]
metric = "safety"
baseline = 55.57
endpoint = 59.78
p_value = 0.1705

[[results]]
metric = "efficacy"
baseline = 30.69
endpoint = 27.4
p_value = 0.1116

[[results]]
metric = "efficacy"
baseline = 32.07
endpoint = 35.79
p_value = 0.1946

[methodology]
design = "cohort"
sample_size = 645
duration_days = 54


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User]
Reformat the data below from JSON to CSV:
{
  "assessment_id": "ASMT-350362",
  "student_id": "STU-421536",
  "course_id": "CRS-1231",
  "type": "exam",
  "date": "2026-01-01",
  "scores": [
    {
      "question": 1,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 2,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 3,
      "points_earned": 8,
      "points_possible": 10
    },
    {
      "question": 4,
      "points_earned": 8,
      "points_possible": 10
    },
    {
      "question": 5,
      "points_earned": 8,
      "points_possible": 10
    },
    {
      "question": 6,
      "points_earned": 6,
      "points_possible": 10
    },
    {
      "question": 7,
      "points_earned": 5,
      "points_possible": 10
    },
    {
      "question": 8,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 9,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 10,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 11,
      "points_earned": 9,
      "points_possible": 10
    }
  ],
  "total_score": 51,
  "percentage": 80.6,
  "grade": "A"
}

[Assistant]
Approach:
1. Task: Convert student assessment from JSON to CSV
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
assessment_id,code,course_id,credits,date,grade,grading_final,grading_homework,grading_midterm,instructor,percentage,schedule,scores,student_id,term,title,total_score,type
ASMT-350362,,CRS-1231,,2026-01-01,A,,,,,80.6,,"[{""question"": 1, ""points_earned"": 2, ""points_possible"": 10}, {""question"": 2, ""points_earned"": 1, ""po",STU-421536,,,51,exam
,MUR356,CRS-1621,3,,,40,30,30,Carolyn Boyer DDS,,"[{""week"": 1, ""topic"": ""resource""}, {""week"": 2, ""topic"": ""prepare""}, {""week"": 3, ""topic"": ""pattern""},",,,Fall 2024,Intuitive 4thgeneration function 101,,
,GFE164,CRS-8082,4,,,40,30,30,Cindy Fisher,,"[{""week"": 1, ""topic"": ""alone""}, {""week"": 2, ""topic"": ""when""}, {""week"": 3, ""topic"": ""response""}, {""we",,,Fall 2024,Public-key global algorithm 101,,
,ARS409,CRS-6275,4,,,40,30,30,Haley Miller,,"[{""week"": 1, ""topic"": ""choose""}, {""week"": 2, ""topic"": ""physical""}, {""week"": 3, ""topic"": ""do""}, {""wee",,,Spring 2024,Cross-group fault-tolerant Local Area Network 101,,
,NGK452,CRS-6394,4,,,40,30,30,Devin Bates,,"[{""week"": 1, ""topic"": ""imagine""}, {""week"": 2, ""topic"": ""church""}, {""week"": 3, ""topic"": ""land""}, {""we",,,Spring 2020,Compatible disintermediate contingency 101,,


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Transform this XML data into JSON format:
<?xml version="1.0" encoding="UTF-8"?>
<transaction_record>
<txn_id>TXN-60159725</txn_id>
<customer_id>13707a49-23b0-4133-8216-7e83986c9575</customer_id>
<timestamp>2026-01-07T13:51:27.689251</timestamp>
<items>
<sku>SKU-82899</sku>
<qty>5</qty>
<price>298.29</price>
</items>
<items>
<sku>SKU-51515</sku>
<qty>4</qty>
<price>343.78</price>
</items>
<items>
<sku>SKU-53336</sku>
<qty>3</qty>
<price>488.21</price>
</items>
<items>
<sku>SKU-52517</sku>
<qty>2</qty>
<price>291.79</price>
</items>
<subtotal>1914.1</subtotal>
<tax>175.88</tax>
<total>1360.6</total>
<payment_method>credit_card</payment_method>
</transaction_record>

[Assistant]
Approach:
1. Task: Convert transaction record from XML to JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "txn_id": "TXN-60159725",
  "customer_id": "13707a49-23b0-4133-8216-7e83986c9575",
  "timestamp": "2026-01-07T13:51:27.689251",
  "items": [
    {
      "sku": "SKU-82899",
      "qty": 5,
      "price": 298.29
    },
    {
      "sku": "SKU-51515",
      "qty": 4,
      "price": 343.78
    },
    {
      "sku": "SKU-53336",
      "qty": 3,
      "price": 488.21
    },
    {
      "sku": "SKU-52517",
      "qty": 2,
      "price": 291.79
    }
  ],
  "subtotal": 1914.1,
  "tax": 175.88,
  "total": 1360.6,
  "payment_method": "credit_card"
}


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User]
Convert the following JSON to TOML:
{
  "post_id": "POST-25055870",
  "platform": "twitter",
  "user_id": "28837af0-4898-41b2-8a38-faf0e2d7f431",
  "username": "khahn",
  "content": "Serve student science today general. Tell risk ball quickly technology.\nDrive because generation support gun message majority. Though do old.",
  "timestamp": "2026-01-07T13:51:27.403909",
  "hashtags": [
    "#conference",
    "#body"
  ],
  "engagement": {
    "likes": 9394,
    "shares": 444,
    "comments": 203
  }
}

[Assistant]
Approach:
1. Task: Convert social media post from JSON to TOML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
post_id = "POST-25055870"
platform = "twitter"
user_id = "28837af0-4898-41b2-8a38-faf0e2d7f431"
username = "khahn"
content = "Serve student science today general. Tell risk ball quickly technology.\nDrive because generation support gun message majority. Though do old."
timestamp = "2026-01-07T13:51:27.403909"
hashtags = [ "#conference", "#body",]

[engagement]
likes = 9394
shares = 444
comments = 203


[System] You are an expert in TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User] Create a TOML representation of api specification.

[Assistant]
Approach:
1. Task: Create api specification in TOML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: key=value syntax, [sections], proper types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
openapi = "3.0.0"

[info]
title = "Grass-roots 6thgeneration ability API"
version = "1.0.0"

[paths."/million".get]
summary = "About little above investment already magazine."
[[paths."/million".get.parameters]]
name = "param0"
in = "query"
type = "string"

[paths."/million".get.responses.200]
description = "Success"

[paths."/million".get.responses.400]
description = "Bad Request"


[System] You are an expert in XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "post_id": "POST-39452168",
  "platform": "twitter",
  "user_id": "ca270bc8-d443-4389-880a-6fc8dd3e9fa5",
  "username": "robertowens",
  "content": "With writer dinner any kitchen add well. Floor image speech charge rate manager vote. Worry involve benefit there nothing rock.\nFactor even apply how three box light.",
  "timestamp": "2026-01-07T13:51:25.425211",
  "hashtags": [
    "#training",
    "#Democrat",
    "#pattern",
    "#discover"
  ],
  "engagement": {
    "likes": 5319,
    "shares": 573,
    "comments": 283
  }
}

[Assistant]
Approach:
1. Task: Convert social media post from JSON to XML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: well-formed tags, proper nesting, escaped special chars
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
<?xml version="1.0" encoding="UTF-8"?>
<social_media_post>
<post_id>POST-39452168</post_id>
<platform>twitter</platform>
<user_id>ca270bc8-d443-4389-880a-6fc8dd3e9fa5</user_id>
<username>robertowens</username>
<content>With writer dinner any kitchen add well. Floor image speech charge rate manager vote. Worry involve benefit there nothing rock.
Factor even apply how three box light.</content>
<timestamp>2026-01-07T13:51:25.425211</timestamp>
<hashtags>#training</hashtags>
<hashtags>#Democrat</hashtags>
<hashtags>#pattern</hashtags>
<hashtags>#discover</hashtags>
<engagement>
<likes>5319</likes>
<shares>573</shares>
<comments>283</comments>
</engagement>
</social_media_post>


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User]
Transform this XML data into YAML format:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-1681251</review_id>
<product_id>PROD-380005</product_id>
<user_id>6ee75bbe-7aec-42b2-b8ce-db908c5fbc3a</user_id>
<rating>3</rating>
<title>Floor measure may hear dark at.</title>
<content>Us board wonder trouble. Up as inside party growth seat. College late direction amount best team.
Fish gas end appear mother assume. Anyone major game miss similar argue. Moment describe require.</content>
<date>2026-01-05</date>
<verified_purchase>True</verified_purchase>
<helpful_votes>21</helpful_votes>
</customer_review>

[Assistant]
Approach:
1. Task: Convert customer review from XML to YAML
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
review_id: REV-1681251
product_id: PROD-380005
user_id: 6ee75bbe-7aec-42b2-b8ce-db908c5fbc3a
rating: 3
title: Floor measure may hear dark at.
content: 'Us board wonder trouble. Up as inside party growth seat. College late direction
  amount best team.

  Fish gas end appear mother assume. Anyone major game miss similar argue. Moment
  describe require.'
date: '2026-01-05'
verified_purchase: true
helpful_votes: 21


[System] You are an expert in CSV format. Think step-by-step, then generate syntactically perfect CSV.

[User] Produce a CSV document for a news article.

[Assistant]
Approach:
1. Task: Create news article in CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
article_id,author,content,headline,published,section,shares,tags,views
ART-4067367,Kristin Larson,"Ahead effort author use. Unit together series provide arrive country off. Whether let thought down.
",Polarized human-resource adapter,2026-01-07T00:05:34.405255,Business,3986,"[""program"", ""final"", ""computer"", ""live""]",74807
ART-6110292,Amber Yu,Seem letter Republican onto game agree industry. Food ask unit they situation pay student. Business ,Decentralized hybrid migration,2026-01-02T19:52:11.838709,Tech,2541,"[""partner"", ""Republican"", ""himself"", ""debate""]",66671
ART-5126730,Jessica Thomas,"Short south whole reduce foot. Power finally security today administration list man.
Laugh bed so. W",Sharable full-range access,2026-01-03T22:30:49.386500,Business,3603,"[""report"", ""world"", ""dream"", ""mouth"", ""ok""]",33961
ART-8883929,Darlene Taylor,"Court perform right later eat history. Rise me detail decade son dog. Role gas base college her.
Mis",Upgradable secondary knowledge user,2026-01-07T04:02:20.823848,Business,3621,"[""professor"", ""prevent"", ""address"", ""less""]",58233


[System] You are an expert in YAML format. Think step-by-step, then generate syntactically perfect YAML.

[User] Generate student assessment data in YAML format.

[Assistant]
Approach:
1. Task: Create student assessment in YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
assessment_id: ASMT-879460
student_id: STU-948921
course_id: CRS-8763
type: quiz
date: '2026-01-03'
scores:
- question: 1
  points_earned: 1
  points_possible: 10
- question: 2
  points_earned: 4
  points_possible: 10
- question: 3
  points_earned: 7
  points_possible: 10
- question: 4
  points_earned: 3
  points_possible: 10
- question: 5
  points_earned: 5
  points_possible: 10
- question: 6
  points_earned: 2
  points_possible: 10
- question: 7
  points_earned: 6
  points_possible: 10
- question: 8
  points_earned: 9
  points_possible: 10
total_score: 83
percentage: 96.07
grade: B


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User] Create a JSON representation of clinical note.

[Assistant]
Approach:
1. Task: Create clinical note in JSON
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
{
  "note_id": "CN-5754690",
  "patient": {
    "mrn": "MRN-521303",
    "age": 32,
    "gender": "M"
  },
  "encounter_date": "2026-01-05",
  "chief_complaint": "fever",
  "vitals": {
    "bp": "101/104",
    "hr": 85,
    "temp_f": 99.3
  },
  "assessment": [
    {
      "problem": "diabetes",
      "icd10": "K80"
    }
  ]
}


[System] You are an expert in JSON format. Think step-by-step, then generate syntactically perfect JSON.

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<prescription>
<prescriber>Melinda Black</prescriber>
<date>2026-01-04</date>
<rx_id>RX-8618237</rx_id>
</prescription>

[Assistant]
Approach:
1. Task: Convert prescription from XML to JSON
2. Complexity: simple - 3-5 fields, minimal nesting
3. Format rules: proper braces/brackets, quoted keys, correct value types
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
{
  "prescriber": "Melinda Black",
  "date": "2026-01-04",
  "rx_id": "RX-8618237"
}