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

[User] Generate financial report data in YAML format.

[Assistant]
Approach:
1. Task: Create financial report 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:
company: Nichols, Ferguson and Butler
ticker: NDVN
quarter: Q1 2022
revenue: 39470251
expenses: 26562838
net_income: 16784469
eps: 3.2
metrics:
  profit_margin: 27.93
  roe: 5.96


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

[User] Output clinical note as TOML.

[Assistant]
Approach:
1. Task: Create clinical note 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:
encounter_date = "2026-01-03"
note_id = "CN-2646438"

[patient]
mrn = "MRN-771263"
age = 41
gender = "M"


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

[User] Create a JSON representation of product listing.

[Assistant]
Approach:
1. Task: Create product listing 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:
{
  "product_id": "PROD-239354",
  "name": "User-centric tertiary contingency",
  "category": "electronics",
  "price": 998.51,
  "currency": "USD",
  "stock": 842,
  "is_available": true,
  "rating": 2.36,
  "reviews": 630,
  "specs": {
    "weight_kg": 0.61,
    "dimensions": "88x23x10cm"
  }
}


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

[User] Generate student assessment data in JSON format.

[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-996269",
  "student_id": "STU-878254",
  "course_id": "CRS-8988",
  "type": "exam",
  "date": "2026-01-03",
  "scores": [
    {
      "question": 1,
      "points_earned": 8,
      "points_possible": 10
    },
    {
      "question": 2,
      "points_earned": 0,
      "points_possible": 10
    },
    {
      "question": 3,
      "points_earned": 8,
      "points_possible": 10
    },
    {
      "question": 4,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 5,
      "points_earned": 7,
      "points_possible": 10
    },
    {
      "question": 6,
      "points_earned": 3,
      "points_possible": 10
    },
    {
      "question": 7,
      "points_earned": 9,
      "points_possible": 10
    },
    {
      "question": 8,
      "points_earned": 7,
      "points_possible": 10
    },
    {
      "question": 9,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 10,
      "points_earned": 3,
      "points_possible": 10
    }
  ],
  "total_score": 71,
  "percentage": 94.86,
  "grade": "B"
}


[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"?>
<contract>
<contract_id>CTR-464030</contract_id>
<parties>
<name>Morales, Williams and Williams</name>
<role>party_a</role>
</parties>
<parties>
<name>Ward-Miller</name>
<role>party_b</role>
</parties>
<effective_date>2026-01-06</effective_date>
<term_months>35</term_months>
<value>994957</value>
<status>active</status>
</contract>

[Assistant]
Approach:
1. Task: Convert contract 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:
{
  "contract_id": "CTR-464030",
  "parties": [
    {
      "name": "Morales, Williams and Williams",
      "role": "party_a"
    },
    {
      "name": "Ward-Miller",
      "role": "party_b"
    }
  ],
  "effective_date": "2026-01-06",
  "term_months": 35,
  "value": 994957,
  "status": "active"
}


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

[User] Create a TOML representation of customer review.

[Assistant]
Approach:
1. Task: Create customer review 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:
review_id = "REV-2575466"
product_id = "PROD-346187"
user_id = "320eb87e-12bd-44ab-bb47-6fec45bd5144"
rating = 1
title = "Possible modern last rate memory fight conference "
content = "Character walk loss rock me social gun.\nCenter choice either push. Push stop yourself."
date = "2026-01-01"
verified_purchase = false
helpful_votes = 26


[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-2604144",
  "patient_mrn": "MRN-906692",
  "order_date": "2026-01-01",
  "panel": "Lipid",
  "results": [
    {
      "test": "Hemoglobin",
      "value": 180.3,
      "unit": "mg/dL",
      "flag": "high"
    },
    {
      "test": "Glucose",
      "value": 97.8,
      "unit": "mg/dL",
      "flag": "normal"
    },
    {
      "test": "Glucose",
      "value": 88.1,
      "unit": "g/dL",
      "flag": "high"
    },
    {
      "test": "Glucose",
      "value": 65.1,
      "unit": "mg/dL",
      "flag": "high"
    },
    {
      "test": "Hemoglobin",
      "value": 95.1,
      "unit": "g/dL",
      "flag": "high"
    },
    {
      "test": "Glucose",
      "value": 86.1,
      "unit": "mg/dL",
      "flag": "low"
    },
    {
      "test": "Hemoglobin",
      "value": 152.8,
      "unit": "mg/dL",
      "flag": "normal"
    }
  ]
}

[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-2604144</result_id>
<patient_mrn>MRN-906692</patient_mrn>
<order_date>2026-01-01</order_date>
<panel>Lipid</panel>
<results>
<test>Hemoglobin</test>
<value>180.3</value>
<unit>mg/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Glucose</test>
<value>97.8</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Glucose</test>
<value>88.1</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Glucose</test>
<value>65.1</value>
<unit>mg/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>95.1</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Glucose</test>
<value>86.1</value>
<unit>mg/dL</unit>
<flag>low</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>152.8</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
</lab_result>


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

[User] Output lab result as TOML.

[Assistant]
Approach:
1. Task: Create lab result 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:
result_id = "LAB-5790382"
patient_mrn = "MRN-357903"
order_date = "2026-01-02"
panel = "CBC"
[[results]]
test = "Glucose"
value = 56.1
unit = "mg/dL"
flag = "high"

[[results]]
test = "Glucose"
value = 114.1
unit = "mg/dL"
flag = "normal"

[[results]]
test = "WBC"
value = 154.7
unit = "mg/dL"
flag = "low"

[[results]]
test = "Glucose"
value = 196.1
unit = "g/dL"
flag = "normal"


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

[User] Generate prescription data in CSV format.

[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-04,"[{""name"": ""Metformin"", ""dosage"": ""20mg"", ""frequency"": ""TID"", ""quantity"": 30}, {""name"": ""Metformin"", ",MRN-277514,Timothy Goodman,RX-9442688
2026-01-05,"[{""name"": ""Atorvastatin"", ""dosage"": ""10mg"", ""frequency"": ""TID"", ""quantity"": 90}]",MRN-305050,Jonathan Bates,RX-4215789
2026-01-03,"[{""name"": ""Lisinopril"", ""dosage"": ""5mg"", ""frequency"": ""TID"", ""quantity"": 90}, {""name"": ""Metformin"", ",MRN-161836,Michael Nguyen,RX-4591569


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

[User]
Convert the following JSON to CSV:
{
  "product_id": "PROD-125540",
  "name": "Universal eco-centric approach",
  "category": "books",
  "price": 208.68,
  "currency": "USD",
  "stock": 879,
  "is_available": true,
  "rating": 4.53,
  "reviews": 925,
  "specs": {
    "weight_kg": 20.35,
    "dimensions": "45x91x83cm"
  }
}

[Assistant]
Approach:
1. Task: Convert product listing 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:
category,currency,is_available,name,price,product_id,rating,reviews,specs_dimensions,specs_weight_kg,stock
books,USD,True,Universal eco-centric approach,208.68,PROD-125540,4.53,925,45x91x83cm,20.35,879
books,USD,True,Customer-focused zero administration website,311.67,PROD-727436,3.4,405,97x86x37cm,0.96,903
clothing,USD,True,Devolved actuating support,776.46,PROD-215173,3.11,541,46x35x23cm,6.82,573
books,USD,True,Diverse next generation methodology,15.2,PROD-691282,2.95,528,33x85x28cm,23.35,239


[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"?>
<financial_report>
<net_income>4233102</net_income>
<metrics>
<profit_margin>14.29</profit_margin>
<roe>18.28</roe>
</metrics>
<company>Blackwell, Simpson and Pace</company>
<eps>0.79</eps>
<expenses>41343491</expenses>
</financial_report>

[Assistant]
Approach:
1. Task: Convert financial report 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:
{
  "net_income": 4233102,
  "metrics": {
    "profit_margin": 14.29,
    "roe": 18.28
  },
  "company": "Blackwell, Simpson and Pace",
  "eps": 0.79,
  "expenses": 41343491
}


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

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

[Assistant]
Approach:
1. Task: Create api specification 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"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Horizontal interactive project API</title>
<version>1.0.0</version>
</info>
<paths>
</base>
<get>
<summary>Management send father actually special image.</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>
<//base>
</paths>
</api_specification>


[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": "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"
          }
        }
      }
    }
  }
}

[Assistant]
Approach:
1. Task: Convert api specification 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"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Optional bottom-line complexity API</title>
<version>1.0.0</version>
</info>
<paths>
</traditional>
<get>
<summary>Discussion then kind hair.</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>
<//traditional>
</paths>
</api_specification>


[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:
{
  "result_id": "LAB-1056021",
  "patient_mrn": "MRN-977601",
  "order_date": "2026-01-02",
  "panel": "CMP",
  "results": [
    {
      "test": "WBC",
      "value": 124.0,
      "unit": "g/dL",
      "flag": "high"
    },
    {
      "test": "Hemoglobin",
      "value": 114.5,
      "unit": "g/dL",
      "flag": "high"
    },
    {
      "test": "WBC",
      "value": 70.6,
      "unit": "g/dL",
      "flag": "high"
    },
    {
      "test": "Glucose",
      "value": 119.6,
      "unit": "mg/dL",
      "flag": "high"
    },
    {
      "test": "Hemoglobin",
      "value": 171.0,
      "unit": "mg/dL",
      "flag": "normal"
    }
  ]
}

[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-1056021</result_id>
<patient_mrn>MRN-977601</patient_mrn>
<order_date>2026-01-02</order_date>
<panel>CMP</panel>
<results>
<test>WBC</test>
<value>124.0</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>114.5</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>WBC</test>
<value>70.6</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Glucose</test>
<value>119.6</value>
<unit>mg/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>171.0</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] Produce a XML document for a student assessment.

[Assistant]
Approach:
1. Task: Create student assessment 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"?>
<student_assessment>
<assessment_id>ASMT-852879</assessment_id>
<student_id>STU-517758</student_id>
<course_id>CRS-9070</course_id>
<type>exam</type>
<date>2026-01-04</date>
<scores>
<question>1</question>
<points_earned>4</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>2</question>
<points_earned>10</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>3</question>
<points_earned>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>4</question>
<points_earned>2</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>5</question>
<points_earned>7</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>6</question>
<points_earned>4</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>7</question>
<points_earned>3</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>8</question>
<points_earned>10</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>9</question>
<points_earned>7</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>10</question>
<points_earned>9</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>11</question>
<points_earned>6</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>12</question>
<points_earned>8</points_earned>
<points_possible>10</points_possible>
</scores>
<total_score>58</total_score>
<percentage>53.23</percentage>
<grade>C</grade>
</student_assessment>


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

[User] Create a XML representation of news article.

[Assistant]
Approach:
1. Task: Create news article 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"?>
<news_article>
<article_id>ART-4067367</article_id>
<headline>Polarized human-resource adapter</headline>
<author>Kristin Larson</author>
<published>2026-01-07T00:05:34.405255</published>

Business

<content>Ahead effort author use. Unit together series provide arrive country off. Whether let thought down.
Eight audience power analysis. Age hope leader yeah without. Experience kitchen heart city.</content>
<tags>program</tags>
<tags>final</tags>
<tags>computer</tags>
<tags>live</tags>
<views>74807</views>
<shares>3986</shares>
</news_article>


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

[User] Create a TOML representation of 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-1748125"
headline = "Customizable leadingedge structure"
author = "Sandra Bennett"
published = "2026-01-03T22:52:42.741679"
section = "Sports"
content = "Majority meeting sound have week public pass. Major food relate spend seven.\nIndeed run fund.\nFederal right stuff difficult alone miss. Stuff rest model job deep knowledge pull force. Too follow face husband every. Hit important agreement rather card west want."
tags = [ "subject", "attention", "class", "campaign", "second",]
views = 63827
shares = 2505


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

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

[Assistant]
Approach:
1. Task: Create clinical note 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"?>
<clinical_note>
<note_id>CN-3409162</note_id>
<patient>
<mrn>MRN-721241</mrn>
<age>35</age>
<gender>F</gender>
</patient>
<encounter_date>2026-01-05</encounter_date>
<chief_complaint>fever</chief_complaint>
<vitals>
<bp>173/107</bp>

61

<temp_f>99.6</temp_f>
</vitals>
<assessment>
<problem>diabetes</problem>
<icd10>J46</icd10>
</assessment>
</clinical_note>


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

[User] Generate product listing data in TOML format.

[Assistant]
Approach:
1. Task: Create product listing 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:
product_id = "PROD-723394"
name = "Streamlined full-range ability"
category = "clothing"
price = 959.9
currency = "USD"
stock = 28
is_available = true
rating = 3.7
reviews = 332

[specs]
weight_kg = 9.93
dimensions = "53x67x45cm"


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

[User] Output clinical note as TOML.

[Assistant]
Approach:
1. Task: Create clinical note 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:
note_id = "CN-2804449"
encounter_date = "2026-01-04"
chief_complaint = "fever"
[[assessment]]
problem = "hypertension"
icd10 = "K44"

[patient]
mrn = "MRN-394213"
age = 73
gender = "F"

[vitals]
bp = "162/64"
hr = 70
temp_f = 102.7


[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"?>
<course_syllabus>
<course_id>CRS-1689</course_id>
NZW166
<title>Operative modular system engine 101</title>
<instructor>David Chen</instructor>
<credits>4</credits>
<term>Fall 2021</term>
<schedule>
<week>1</week>
<topic>in</topic>
</schedule>
<schedule>
<week>2</week>
<topic>summer</topic>
</schedule>
<schedule>
<week>3</week>
<topic>unit</topic>
</schedule>
<schedule>
<week>4</week>
<topic>wind</topic>
</schedule>
<schedule>
<week>5</week>
<topic>act</topic>
</schedule>
<schedule>
<week>6</week>
<topic>itself</topic>
</schedule>
<schedule>
<week>7</week>
<topic>would</topic>
</schedule>
<schedule>
<week>8</week>
<topic>itself</topic>
</schedule>
<schedule>
<week>9</week>
<topic>tell</topic>
</schedule>
<schedule>
<week>10</week>
<topic>money</topic>
</schedule>
<schedule>
<week>11</week>
<topic>long</topic>
</schedule>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
</course_syllabus>

[Assistant]
Approach:
1. Task: Convert course syllabus 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:
{
  "course_id": "CRS-1689",
  "code": "NZW166",
  "title": "Operative modular system engine 101",
  "instructor": "David Chen",
  "credits": 4,
  "term": "Fall 2021",
  "schedule": [
    {
      "week": 1,
      "topic": "in"
    },
    {
      "week": 2,
      "topic": "summer"
    },
    {
      "week": 3,
      "topic": "unit"
    },
    {
      "week": 4,
      "topic": "wind"
    },
    {
      "week": 5,
      "topic": "act"
    },
    {
      "week": 6,
      "topic": "itself"
    },
    {
      "week": 7,
      "topic": "would"
    },
    {
      "week": 8,
      "topic": "itself"
    },
    {
      "week": 9,
      "topic": "tell"
    },
    {
      "week": 10,
      "topic": "money"
    },
    {
      "week": 11,
      "topic": "long"
    }
  ],
  "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]
Reformat the data below from TOML to YAML:
paper_id = "arXiv:2020.93852"
title = "Reactive solution-oriented circuit"
abstract = "Law fund huge better or. Federal forward north law. Work available call never.\nCarry cultural day front resource write. Southern white pattern fear."
keywords = [ "wind", "wife", "report", "financial",]
citations = 45
[[authors]]
name = "Jennifer Gray"
affiliation = "Bryant, Lewis and Wells"
email = "spalmer@example.com"

[[authors]]
name = "David Brown"
affiliation = "Cortez, Cook and Ross"
email = "melvin21@example.com"

[publication]
venue = "Cell"
year = 2023
doi = "10.1277/DPuH"

[Assistant]
Approach:
1. Task: Convert research paper from TOML 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:
paper_id: arXiv:2020.93852
title: Reactive solution-oriented circuit
authors:
- name: Jennifer Gray
  affiliation: Bryant, Lewis and Wells
  email: spalmer@example.com
- name: David Brown
  affiliation: Cortez, Cook and Ross
  email: melvin21@example.com
abstract: 'Law fund huge better or. Federal forward north law. Work available call
  never.

  Carry cultural day front resource write. Southern white pattern fear.'
keywords:
- wind
- wife
- report
- financial
publication:
  venue: Cell
  year: 2023
  doi: 10.1277/DPuH
citations: 45
funding_source: null


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

[User] Produce a XML document for a prescription.

[Assistant]
Approach:
1. Task: Create prescription 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"?>
<prescription>
<rx_id>RX-1795504</rx_id>
<patient_mrn>MRN-355763</patient_mrn>
<prescriber>Henry Padilla</prescriber>
<date>2026-01-01</date>
<medications>
<name>Metformin</name>
<dosage>20mg</dosage>
<frequency>daily</frequency>
<quantity>90</quantity>
</medications>
</prescription>


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

[User] Create a CSV representation of customer review.

[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
,Camera left hope prevent inside real. Whether trouble their always manager cultural majority popular,,2026-01-01,23,,,,PROD-173271,2,REV-5008217,,,,,Lay lead it politics brother.,11121b86-b60c-4ea2-b83a-cbb727cd7a24,True
electronics,,USD,,,True,Ameliorated fresh-thinking pricing structure,191.11,PROD-637206,2.52,,126,54x77x57cm,26.06,152,,,
clothing,,USD,,,True,Networked dynamic leverage,662.15,PROD-224605,2.13,,582,52x10x57cm,49.71,29,,,
books,,USD,,,True,Adaptive reciprocal forecast,730.04,PROD-373162,2.64,,797,73x18x15cm,5.77,79,,,


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

[User] Create a TOML representation of error log.

[Assistant]
Approach:
1. Task: Create error log 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:
error_id = "ff91c212-6cce-4ac2-978d-0740381882de"
timestamp = "2026-01-07T13:51:27.679071"
level = "WARNING"
service = "drawService"
message = "Support red list product forget cut speak."
stack_trace = [ "at girl.py:186", "at hold.py:186",]

[context]
user_id = "473e683b-291e-461f-b848-d224b7dcbd8b"
request_id = "454a35ad-23ee-42a8-9d57-dbf5cedbef74"


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

[User] Create a YAML representation of 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-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] Output clinical note as JSON.

[Assistant]
Approach:
1. Task: Create clinical note 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:
{
  "note_id": "CN-3041313",
  "patient": {
    "mrn": "MRN-164256",
    "age": 45,
    "gender": "F"
  },
  "encounter_date": "2026-01-04",
  "chief_complaint": "fever",
  "vitals": {
    "bp": "153/76",
    "hr": 98,
    "temp_f": 102.6
  },
  "assessment": [
    {
      "problem": "hypertension",
      "icd10": "I84"
    },
    {
      "problem": "hypertension",
      "icd10": "J93"
    }
  ]
}


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

[User] Create a JSON representation of research paper.

[Assistant]
Approach:
1. Task: Create research paper 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:
{
  "paper_id": "arXiv:2020.65510",
  "title": "Mandatory solution-oriented groupware",
  "authors": [
    {
      "name": "Jared Fuller",
      "affiliation": "Robinson, Crawford and Johnson",
      "email": "jenna58@example.net"
    },
    {
      "name": "Nancy Anderson",
      "affiliation": "Shannon-Johnson",
      "email": "richdonald@example.net"
    },
    {
      "name": "Julia Neal",
      "affiliation": "Roach, Harper and Cameron",
      "email": "gillcory@example.com"
    }
  ],
  "abstract": "Along its pressure yeah. Artist pattern nearly rich realize available skill. Month beyond rate make kid painting.",
  "keywords": [
    "surface",
    "consumer",
    "despite",
    "compare",
    "protect"
  ],
  "publication": {
    "venue": "Nature",
    "year": 2022,
    "doi": "10.8909/Qnkv"
  },
  "citations": 488,
  "funding_source": "Johnson LLC"
}


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

[User] Output financial report as CSV.

[Assistant]
Approach:
1. Task: Create financial report 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:
company,eps,expenses,metrics_profit_margin,metrics_roe,net_income,quarter,revenue,ticker
Leon-Lewis,7.9,46362888,25.04,5.27,14538939,Q4 2022,56885685,FGCI
"Acevedo, Robinson and Moreno",9.4,4293889,17.95,16.33,19555518,Q1 2022,38744580,QCJP
"Hernandez, Ellis and Glover",6.4,72656211,21.06,22.29,19183103,Q4 2021,55207114,TJLJ
Gonzalez Group,2.8,58785763,11.64,10.65,5236675,Q4 2022,44394829,YPUD


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

[User] Generate research paper data in JSON format.

[Assistant]
Approach:
1. Task: Create research paper 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:
{
  "paper_id": "arXiv:2020.69453",
  "title": "Assimilated needs-based portal",
  "authors": [
    {
      "name": "Evan Reed",
      "affiliation": "Orr, Wheeler and Johnson",
      "email": "cheryl05@example.net"
    },
    {
      "name": "Amanda Mcmahon",
      "affiliation": "Maxwell-Price",
      "email": "mbowen@example.org"
    },
    {
      "name": "Angel Vasquez",
      "affiliation": "Melendez, Osborne and Harris",
      "email": "timothysutton@example.com"
    }
  ],
  "abstract": "Economy instead thank kitchen. For pattern he purpose strong goal challenge.",
  "keywords": [
    "power",
    "main",
    "light",
    "form",
    "system"
  ],
  "publication": {
    "venue": "Cell",
    "year": 2024,
    "doi": "10.9550/gbOm"
  },
  "citations": 115,
  "funding_source": null
}


[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 = "Stand-alone dedicated complexity API"
version = "1.0.0"

[paths."/hear".get]
summary = "Chance cultural sort including high."
[[paths."/hear".get.parameters]]
name = "param0"
in = "query"
type = "string"

[[paths."/hear".get.parameters]]
name = "param1"
in = "query"
type = "string"

[[paths."/hear".get.parameters]]
name = "param2"
in = "query"
type = "string"

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

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


[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"?>
<prescription>
<medications>
<name>Atorvastatin</name>
<dosage>5mg</dosage>
<frequency>BID</frequency>
<quantity>30</quantity>
</medications>
<prescriber>Isaac Howard</prescriber>
<date>2026-01-03</date>
</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:
{
  "medications": [
    {
      "name": "Atorvastatin",
      "dosage": "5mg",
      "frequency": "BID",
      "quantity": 30
    }
  ],
  "prescriber": "Isaac Howard",
  "date": "2026-01-03"
}


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

[User] Output error log as XML.

[Assistant]
Approach:
1. Task: Create error log 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"?>
<error_log>
<error_id>d03afc03-94bd-4dbb-bf49-9cda441c119b</error_id>
<timestamp>2026-01-07T13:51:25.952127</timestamp>
<level>CRITICAL</level>
<service>fromService</service>
<message>Add perform politics some card score brother.</message>
<stack_trace>at send.py:152</stack_trace>
<stack_trace>at young.py:309</stack_trace>
<context>
<user_id>2b3e5573-7b69-4807-a899-cbaa4adadf38</user_id>
<request_id>beac9c14-4ae5-407d-9aae-d7a56f6790f6</request_id>
</context>
</error_log>


[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: 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. Populate fields with realistic example data based on the schema.

Output:
{
  "instructor": "Ryan Griffin",
  "course_id": "CRS-4864",
  "code": "NLW161"
}


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

[User] Create a YAML representation of sales analytics.

[Assistant]
Approach:
1. Task: Create sales analytics 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:
period: February 2020
total_revenue: 5010605
units_sold: 4486
channels:
- name: online
  revenue: 4865933
  growth: 41.22
- name: wholesale
  revenue: 4636446
  growth: 21.68
top_products:
- sku: SKU-3361
  sales: 360256
- sku: SKU-1576
  sales: 355717
- sku: SKU-8891
  sales: 396344


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

[User] Output financial report as JSON.

[Assistant]
Approach:
1. Task: Create financial report 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:
{
  "company": "Rodriguez, Curry and Yates",
  "ticker": "KWAZ",
  "quarter": "Q1 2020",
  "revenue": 4863925,
  "expenses": 55129980,
  "net_income": 12179320,
  "eps": 7.94,
  "metrics": {
    "profit_margin": 29.26,
    "roe": 9.63
  }
}


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

[User] Generate transaction record data in JSON format.

[Assistant]
Approach:
1. Task: Create transaction record 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:
{
  "txn_id": "TXN-31892506",
  "customer_id": "6c5d6d8e-2901-438d-be6d-be57a13ea5ab",
  "timestamp": "2026-01-07T13:51:25.485684",
  "items": [
    {
      "sku": "SKU-80058",
      "qty": 4,
      "price": 142.37
    },
    {
      "sku": "SKU-53232",
      "qty": 1,
      "price": 151.54
    }
  ],
  "subtotal": 692.94,
  "tax": 100.91,
  "total": 1647.14,
  "payment_method": "credit_card"
}


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

[User]
Convert the following JSON to YAML:
{
  "company": "Leon-Lewis",
  "ticker": "FGCI",
  "quarter": "Q4 2022",
  "revenue": 56885685,
  "expenses": 46362888,
  "net_income": 14538939,
  "eps": 7.9,
  "metrics": {
    "profit_margin": 25.04,
    "roe": 5.27
  }
}

[Assistant]
Approach:
1. Task: Convert financial report from JSON 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:
company: Leon-Lewis
ticker: FGCI
quarter: Q4 2022
revenue: 56885685
expenses: 46362888
net_income: 14538939
eps: 7.9
metrics:
  profit_margin: 25.04
  roe: 5.27


[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"?>
<course_syllabus>
<course_id>CRS-8855</course_id>
DBP130
<title>Team-oriented 3rdgeneration implementation 101</title>
<instructor>Carl Davis</instructor>
<credits>3</credits>
<term>Fall 2024</term>
<schedule>
<week>1</week>
<topic>manage</topic>
</schedule>
<schedule>
<week>2</week>
<topic>someone</topic>
</schedule>
<schedule>
<week>3</week>
<topic>bring</topic>
</schedule>
<schedule>
<week>4</week>
<topic>board</topic>
</schedule>
<schedule>
<week>5</week>
<topic>important</topic>
</schedule>
<schedule>
<week>6</week>
<topic>he</topic>
</schedule>
<schedule>
<week>7</week>
<topic>possible</topic>
</schedule>
<schedule>
<week>8</week>
<topic>office</topic>
</schedule>
<schedule>
<week>9</week>
<topic>board</topic>
</schedule>
<schedule>
<week>10</week>
<topic>drive</topic>
</schedule>
<schedule>
<week>11</week>
<topic>Mrs</topic>
</schedule>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
</course_syllabus>

[Assistant]
Approach:
1. Task: Convert course syllabus 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:
{
  "course_id": "CRS-8855",
  "code": "DBP130",
  "title": "Team-oriented 3rdgeneration implementation 101",
  "instructor": "Carl Davis",
  "credits": 3,
  "term": "Fall 2024",
  "schedule": [
    {
      "week": 1,
      "topic": "manage"
    },
    {
      "week": 2,
      "topic": "someone"
    },
    {
      "week": 3,
      "topic": "bring"
    },
    {
      "week": 4,
      "topic": "board"
    },
    {
      "week": 5,
      "topic": "important"
    },
    {
      "week": 6,
      "topic": "he"
    },
    {
      "week": 7,
      "topic": "possible"
    },
    {
      "week": 8,
      "topic": "office"
    },
    {
      "week": 9,
      "topic": "board"
    },
    {
      "week": 10,
      "topic": "drive"
    },
    {
      "week": 11,
      "topic": "Mrs"
    }
  ],
  "grading": {
    "homework": 30,
    "midterm": 30,
    "final": 40
  }
}


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

[User] Generate experiment result data in TOML format.

[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-506156"
title = "Effect of window on soldier"
conclusion = "significant"
[[results]]
metric = "safety"
baseline = 32.86
endpoint = 81.82
p_value = 0.3265

[[results]]
metric = "efficacy"
baseline = 88.84
endpoint = 10.2
p_value = 0.448

[[results]]
metric = "safety"
baseline = 27.68
endpoint = 60.55
p_value = 0.1062

[[results]]
metric = "safety"
baseline = 51.8
endpoint = 89.23
p_value = 0.4543

[methodology]
design = "observational"
sample_size = 884
duration_days = 87


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

[User] Create a JSON representation of customer review.

[Assistant]
Approach:
1. Task: Create customer review 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:
{
  "review_id": "REV-9982202",
  "product_id": "PROD-452864",
  "user_id": "015289de-7f3e-45e2-b1d0-7fe22aff92a9",
  "rating": 3,
  "title": "Example center fill free.",
  "content": "North describe old attention usually third. Important wish security ago somebody remain everyone modern. Significant chair place throughout study administration American.",
  "date": "2026-01-04",
  "verified_purchase": false,
  "helpful_votes": 34
}


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

[User]
Reformat the data below from CSV to TOML:
content,engagement_comments,engagement_likes,engagement_shares,hashtags,platform,post_id,timestamp,user_id,username
"Southern write three operation throw interest whether.
Decade quality training employee. Financial o",244,8106,850,"[""#report"", ""#newspaper""]",facebook,POST-52722833,2026-01-07T13:51:26.716888,d42576ea-a78d-4261-852d-cbcc2fd55da5,justin96
Claim all process significant night. Trade successful day all protect key character reality. Wind I ,355,270,592,"[""#generation"", ""#experience""]",twitter,POST-44196678,2026-01-07T13:51:26.719177,8211148c-5ca6-4095-be33-9fa87434f33e,martinwatson
"Arrive drop lay friend owner time. Any drop guess I deal continue artist.
Officer million human test",61,4148,200,"[""#certainly"", ""#push"", ""#production""]",twitter,POST-86367942,2026-01-07T13:51:26.719544,6961d01a-d590-4a78-b2b6-abbb8652c7e0,melissaruiz

[Assistant]
Approach:
1. Task: Convert social media post from CSV to 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. Transform values to match the target format specifications.

Output:
post_id = "POST-52722833"
platform = "facebook"
user_id = "d42576ea-a78d-4261-852d-cbcc2fd55da5"
username = "justin96"
content = "Southern write three operation throw interest whether.\nDecade quality training employee. Financial out position catch finish author. Past over in create.\nNice reduce try contain future back customer."
timestamp = "2026-01-07T13:51:26.716888"
hashtags = [ "#report", "#newspaper",]

[engagement]
likes = 8106
shares = 850
comments = 244


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

[User]
Convert the following JSON to XML:
{
  "experiment_id": "EXP-690622",
  "title": "Effect of drug on effect",
  "methodology": {
    "design": "RCT",
    "sample_size": 718,
    "duration_days": 247
  },
  "results": [
    {
      "metric": "efficacy",
      "baseline": 65.65,
      "endpoint": 47.19,
      "p_value": 0.4009
    },
    {
      "metric": "efficacy",
      "baseline": 18.88,
      "endpoint": 49.79,
      "p_value": 0.0184
    },
    {
      "metric": "efficacy",
      "baseline": 32.37,
      "endpoint": 97.44,
      "p_value": 0.3919
    }
  ],
  "conclusion": "non-significant"
}

[Assistant]
Approach:
1. Task: Convert experiment 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"?>
<experiment_result>
<experiment_id>EXP-690622</experiment_id>
<title>Effect of drug on effect</title>
<methodology>
<design>RCT</design>
<sample_size>718</sample_size>
<duration_days>247</duration_days>
</methodology>
<results>
<metric>efficacy</metric>
<baseline>65.65</baseline>
<endpoint>47.19</endpoint>
<p_value>0.4009</p_value>
</results>
<results>
<metric>efficacy</metric>
<baseline>18.88</baseline>
<endpoint>49.79</endpoint>
<p_value>0.0184</p_value>
</results>
<results>
<metric>efficacy</metric>
<baseline>32.37</baseline>
<endpoint>97.44</endpoint>
<p_value>0.3919</p_value>
</results>
<conclusion>non-significant</conclusion>
</experiment_result>


[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"?>
<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>

[Assistant]
Approach:
1. Task: Convert course syllabus 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:
{
  "course_id": "CRS-6204",
  "code": "WOR378",
  "title": "Multi-channeled bi-directional implementation 101",
  "instructor": "Charlene Houston",
  "credits": 4,
  "term": "Spring 2023",
  "schedule": [
    {
      "week": 1,
      "topic": "under"
    },
    {
      "week": 2,
      "topic": "trade"
    },
    {
      "week": 3,
      "topic": "good"
    },
    {
      "week": 4,
      "topic": "grow"
    },
    {
      "week": 5,
      "topic": "ability"
    },
    {
      "week": 6,
      "topic": "experience"
    },
    {
      "week": 7,
      "topic": "offer"
    },
    {
      "week": 8,
      "topic": "account"
    }
  ],
  "grading": {
    "homework": 30,
    "midterm": 30,
    "final": 40
  }
}


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

[User] Create a TOML representation of clinical note.

[Assistant]
Approach:
1. Task: Create clinical note 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:
chief_complaint = "chest pain"
note_id = "CN-6154695"
[[assessment]]
problem = "hypertension"
icd10 = "K41"

[[assessment]]
problem = "hypertension"
icd10 = "J91"

[[assessment]]
problem = "hypertension"
icd10 = "J64"

[vitals]
bp = "97/107"
hr = 107
temp_f = 99.6

[patient]
mrn = "MRN-705297"
age = 67
gender = "F"


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

[User] Generate customer review data in YAML format.

[Assistant]
Approach:
1. Task: Create customer review in YAML
2. Complexity: simple - 3-5 fields, minimal nesting
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:
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 XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Transform this JSON data into XML format:
{
  "course_id": "CRS-5704",
  "code": "BXM405",
  "title": "Profit-focused responsive throughput 101",
  "instructor": "Emily Bryan",
  "credits": 3,
  "term": "Spring 2021",
  "schedule": [
    {
      "week": 1,
      "topic": "southern"
    },
    {
      "week": 2,
      "topic": "raise"
    },
    {
      "week": 3,
      "topic": "across"
    },
    {
      "week": 4,
      "topic": "teacher"
    },
    {
      "week": 5,
      "topic": "service"
    },
    {
      "week": 6,
      "topic": "body"
    },
    {
      "week": 7,
      "topic": "practice"
    },
    {
      "week": 8,
      "topic": "authority"
    },
    {
      "week": 9,
      "topic": "throw"
    },
    {
      "week": 10,
      "topic": "second"
    },
    {
      "week": 11,
      "topic": "authority"
    }
  ],
  "grading": {
    "homework": 30,
    "midterm": 30,
    "final": 40
  }
}

[Assistant]
Approach:
1. Task: Convert course syllabus 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"?>
<course_syllabus>
<course_id>CRS-5704</course_id>
BXM405
<title>Profit-focused responsive throughput 101</title>
<instructor>Emily Bryan</instructor>
<credits>3</credits>
<term>Spring 2021</term>
<schedule>
<week>1</week>
<topic>southern</topic>
</schedule>
<schedule>
<week>2</week>
<topic>raise</topic>
</schedule>
<schedule>
<week>3</week>
<topic>across</topic>
</schedule>
<schedule>
<week>4</week>
<topic>teacher</topic>
</schedule>
<schedule>
<week>5</week>
<topic>service</topic>
</schedule>
<schedule>
<week>6</week>
<topic>body</topic>
</schedule>
<schedule>
<week>7</week>
<topic>practice</topic>
</schedule>
<schedule>
<week>8</week>
<topic>authority</topic>
</schedule>
<schedule>
<week>9</week>
<topic>throw</topic>
</schedule>
<schedule>
<week>10</week>
<topic>second</topic>
</schedule>
<schedule>
<week>11</week>
<topic>authority</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] Create a JSON representation of product listing.

[Assistant]
Approach:
1. Task: Create product listing 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:
{
  "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"?>
<lab_result>
<result_id>LAB-1812594</result_id>
<patient_mrn>MRN-755137</patient_mrn>
<order_date>2026-01-06</order_date>
<panel>CMP</panel>
<results>
<test>Glucose</test>
<value>131.9</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Glucose</test>
<value>183.7</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>WBC</test>
<value>130.1</value>
<unit>mg/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>178.3</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
</lab_result>

[Assistant]
Approach:
1. Task: Convert lab result 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:
{
  "result_id": "LAB-1812594",
  "patient_mrn": "MRN-755137",
  "order_date": "2026-01-06",
  "panel": "CMP",
  "results": [
    {
      "test": "Glucose",
      "value": 131.9,
      "unit": "mg/dL",
      "flag": "normal"
    },
    {
      "test": "Glucose",
      "value": 183.7,
      "unit": "g/dL",
      "flag": "normal"
    },
    {
      "test": "WBC",
      "value": 130.1,
      "unit": "mg/dL",
      "flag": "high"
    },
    {
      "test": "Hemoglobin",
      "value": 178.3,
      "unit": "g/dL",
      "flag": "low"
    }
  ]
}


[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:
openapi = "3.0.0"

[info]
title = "Cross-group bottom-line algorithm API"
version = "1.0.0"

[paths."/rule".get]
summary = "Center available level environment per away author"
[[paths."/rule".get.parameters]]
name = "param0"
in = "query"
type = "string"

[[paths."/rule".get.parameters]]
name = "param1"
in = "query"
type = "string"

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

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

[Assistant]
Approach:
1. Task: Convert api specification 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"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Cross-group bottom-line algorithm API</title>
<version>1.0.0</version>
</info>
<paths>
</rule>
<get>
<summary>Center available level environment per away author</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>
<//rule>
</paths>
</api_specification>


[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: 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
,Or dog never any center population. Program it they Republican over step. Who television finish true,,2026-01-01,23,,,,PROD-852988,2,REV-3836429,,,,,Report thus get describe identify.,39a3d2bd-fb84-4dfc-9cb6-45bd3ebddca0,False
electronics,,USD,,,True,Inverse bi-directional implementation,565.03,PROD-659674,3.57,,652,47x67x16cm,35.6,122,,,
books,,USD,,,True,Cloned even-keeled moderator,776.27,PROD-402930,2.27,,316,41x49x75cm,43.25,517,,,
books,,USD,,,True,Networked 3rdgeneration conglomeration,397.66,PROD-435382,1.58,,827,85x53x62cm,26.8,929,,,
books,,USD,,,True,Automated zero administration attitude,37.5,PROD-960949,4.67,,703,95x45x48cm,29.65,669,,,


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

[User] Output contract as YAML.

[Assistant]
Approach:
1. Task: Create contract 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:
contract_id: CTR-544771
parties:
- name: Prince-Finley
  role: party_a
- name: Stone LLC
  role: party_b
effective_date: '2026-01-02'
term_months: 52
value: 394049
status: active


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

[User] Generate api specification data in XML format.

[Assistant]
Approach:
1. Task: Create api specification 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"?>
<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 XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Reformat the data below from CSV to XML:
article_id,author,content,headline,published,section,shares,tags,views
ART-8221745,Maria Johnson,Would movement white military what them cup. Available remember control staff. None mean hundred PM.,Polarized zero administration support,2026-01-03T08:37:58.870132,Business,763,"[""environment"", ""name"", ""receive"", ""happen"", ""join""]",46852
ART-2170111,Ann Miller,Product training we truth chance whose. Chair wrong bag environment Democrat speech sort sea. Kitche,Operative multi-tasking strategy,2026-01-01T22:47:51.302000,Business,574,"[""garden"", ""order"", ""teach"", ""again"", ""mind""]",43772
ART-1541137,Elizabeth Castro,"Response also drive year even as company. Front one opportunity and get president.
Item subject ente",Sharable grid-enabled application,2026-01-01T01:19:53.037730,Business,3420,"[""through"", ""TV"", ""quality""]",48428

[Assistant]
Approach:
1. Task: Convert news article 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"?>
<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>


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

[User] Create a XML representation of product listing.

[Assistant]
Approach:
1. Task: Create product listing 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"?>
<product_listing>
<product_id>PROD-125540</product_id>
<name>Universal eco-centric approach</name>
<category>books</category>
<price>208.68</price>
<currency>USD</currency>
<stock>879</stock>
<is_available>True</is_available>
<rating>4.53</rating>
<reviews>925</reviews>
<specs>
<weight_kg>20.35</weight_kg>
<dimensions>45x91x83cm</dimensions>
</specs>
</product_listing>


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

[User] Generate product listing data in JSON format.

[Assistant]
Approach:
1. Task: Create product listing 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:
{
  "product_id": "PROD-210763",
  "name": "Team-oriented grid-enabled support",
  "category": "clothing",
  "price": 360.14,
  "currency": "USD",
  "stock": 657,
  "is_available": true,
  "rating": 3.34,
  "reviews": 923,
  "specs": {
    "weight_kg": 14.15,
    "dimensions": "28x80x26cm"
  }
}


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

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

[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:
content,date,helpful_votes,product_id,rating,review_id,title,user_id,verified_purchase
,2026-01-04,39,,5,REV-1864702,State standard bad message use.,,
Clearly scientist main debate guy. Lose population partner behavior hospital wrong. Work how some ta,2026-01-05,63,PROD-787796,2,REV-6301422,Tree allow senior wrong color answer.,223c8b02-3540-4b24-927b-7773696f93d9,True
Simply care manager fire write detail behind relationship. Wife about this. Today at available coupl,2026-01-01,24,PROD-452988,3,REV-7695509,See save cultural.,f82823d8-c49e-49bb-8e36-710b092a6062,True
"Total growth model room. Certainly unit dream article century attorney radio stage.
Black despite la",2026-01-03,13,PROD-630086,1,REV-9930959,Capital above pretty almost.,1cecce83-eb6b-4a24-af9c-e7068b056f4e,True


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

[User] Output social media post as XML.

[Assistant]
Approach:
1. Task: Create social media post 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"?>
<social_media_post>
<post_id>POST-59844758</post_id>
<timestamp>2026-01-07T13:51:27.358144</timestamp>
<hashtags>#population</hashtags>
<hashtags>#during</hashtags>
<hashtags>#executive</hashtags>
<hashtags>#house</hashtags>
</social_media_post>


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

[User] Produce a CSV document for a social media post.

[Assistant]
Approach:
1. Task: Create social media post 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:
content,engagement_comments,engagement_likes,engagement_shares,hashtags,platform,post_id,timestamp,user_id,username
"Thousand book animal myself wear beautiful. Room rock couple reality her.
Join town travel agency va",368,9942,119,"[""#case"", ""#along"", ""#only"", ""#have""]",instagram,POST-66277640,2026-01-07T13:51:26.676406,7e83a029-16e2-49ad-a855-906c882abe46,reynoldstaylor
"Option church list quite base lot along. When performance training us add ever first.
Drop state mon",376,7803,668,"[""#wall"", ""#later"", ""#certainly"", ""#hot""]",twitter,POST-92619883,2026-01-07T13:51:26.677878,4ae4b898-9469-4955-a73d-92323512c74d,qpierce
"Minute according add through environmental.
Like information area call level heart. Scientist small ",282,4413,789,"[""#probably"", ""#hard""]",facebook,POST-93375185,2026-01-07T13:51:26.678194,bab97434-ba20-4bf9-bcad-9f85bddbdf90,achandler
Provide most television low dinner television. Both important speech finally whether your. Within of,473,9636,586,"[""#evening"", ""#easy"", ""#reflect""]",twitter,POST-84786736,2026-01-07T13:51:26.678659,c115d6a2-7864-43c0-a8af-c61de4fa490b,williamskyle
Head pressure view recently central lawyer.,473,4366,759,"[""#democratic"", ""#reason"", ""#while""]",twitter,POST-36938532,2026-01-07T13:51:26.679076,a872cf43-c2a5-4280-9c56-e4b859821dfe,peterdecker


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

[User]
Convert the following CSV to TOML:
assessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f
"[{""problem"": ""hypertension"", ""icd10"": ""J35""}, {""problem"": ""hypertension"", ""icd10"": ""K44""}, {""problem",headache,2026-01-03,CN-6952117,50,F,MRN-227055,146/78,63,97.9
"[{""problem"": ""diabetes"", ""icd10"": ""K84""}]",chest pain,2026-01-06,CN-8134151,59,F,MRN-978661,156/83,92,98.6
"[{""problem"": ""diabetes"", ""icd10"": ""K56""}]",chest pain,2026-01-03,CN-2064605,82,F,MRN-113820,104/62,104,101.6
"[{""problem"": ""diabetes"", ""icd10"": ""I36""}]",chest pain,2026-01-05,CN-8885544,74,M,MRN-710128,179/87,77,99.8
"[{""problem"": ""hypertension"", ""icd10"": ""K39""}, {""problem"": ""hypertension"", ""icd10"": ""J17""}, {""problem",headache,2026-01-04,CN-7391338,80,M,MRN-554214,151/97,83,102.3

[Assistant]
Approach:
1. Task: Convert clinical note from CSV to 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. Transform values to match the target format specifications.

Output:
note_id = "CN-6952117"
encounter_date = "2026-01-03"
chief_complaint = "headache"
[[assessment]]
problem = "hypertension"
icd10 = "J35"

[[assessment]]
problem = "hypertension"
icd10 = "K44"

[[assessment]]
problem = "hypertension"
icd10 = "I58"

[patient]
mrn = "MRN-227055"
age = 50
gender = "F"

[vitals]
bp = "146/78"
hr = 63
temp_f = 97.9


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

[User] Generate course syllabus data in XML format.

[Assistant]
Approach:
1. Task: Create course syllabus 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"?>
<course_syllabus>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
<credits>4</credits>
<course_id>CRS-7759</course_id>
<schedule>
<week>1</week>
<topic>meet</topic>
</schedule>
<schedule>
<week>2</week>
<topic>around</topic>
</schedule>
<schedule>
<week>3</week>
<topic>college</topic>
</schedule>
<schedule>
<week>4</week>
<topic>fly</topic>
</schedule>
<schedule>
<week>5</week>
<topic>summer</topic>
</schedule>
<schedule>
<week>6</week>
<topic>painting</topic>
</schedule>
<schedule>
<week>7</week>
<topic>size</topic>
</schedule>
<schedule>
<week>8</week>
<topic>off</topic>
</schedule>
<schedule>
<week>9</week>
<topic>point</topic>
</schedule>
<schedule>
<week>10</week>
<topic>light</topic>
</schedule>
<schedule>
<week>11</week>
<topic>nothing</topic>
</schedule>
<instructor>Matthew Johnson</instructor>
</course_syllabus>


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

[User]
Transform this CSV data into XML format:
abstract,authors,citations,funding_source,keywords,paper_id,publication_doi,publication_venue,publication_year,title
Win both purpose hour professor table.,"[{""name"": ""Gary Johnson"", ""affiliation"": ""Wolf Group"", ""email"": ""jamie40@example.org""}, {""name"": ""Li",258,"Espinoza, Khan and Lowe","[""office"", ""during"", ""more"", ""apply"", ""program""]",arXiv:2022.79764,10.1780/NyHo,Nature,2023,Progressive exuding adapter
"Chance entire PM must way near. Difficult community sell.
Senior if behind.","[{""name"": ""Stephanie Stewart"", ""affiliation"": ""Hughes, Perry and Hernandez"", ""email"": ""christopherbo",485,None,"[""might"", ""Mr"", ""chair"", ""capital"", ""that""]",arXiv:2020.22680,10.9346/isYH,Science,2024,Team-oriented grid-enabled database
Activity magazine fish cultural likely half. Population both structure professional hair table arm. ,"[{""name"": ""Robert Lara"", ""affiliation"": ""Lee-Hill"", ""email"": ""dorisnewman@example.com""}, {""name"": ""C",229,None,"[""outside"", ""medical"", ""thousand"", ""into"", ""thus""]",arXiv:2024.19835,10.4945/nUcw,Cell,2021,Multi-tiered even-keeled firmware
Green participant teacher art. Again guess choose call. Month recently media say performance address,"[{""name"": ""Alexander Richard"", ""affiliation"": ""Gibson PLC"", ""email"": ""virginia57@example.com""}, {""na",2,Moyer LLC,"[""send"", ""provide"", ""civil"", ""although""]",arXiv:2021.44315,10.6759/gkrz,Cell,2024,Centralized homogeneous emulation

[Assistant]
Approach:
1. Task: Convert research paper from CSV 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:2022.79764</paper_id>
<title>Progressive exuding adapter</title>
<authors>
<name>Gary Johnson</name>
<affiliation>Wolf Group</affiliation>
<email>jamie40@example.org</email>
</authors>
<authors>
<name>Lisa Ortega</name>
<affiliation>Wells, Flores and Cooper</affiliation>
<email>nicholas25@example.com</email>
</authors>
<authors>
<name>Kimberly Alvarez</name>
<affiliation>Lewis-Hunt</affiliation>
<email>bookersteven@example.com</email>
</authors>
<abstract>Win both purpose hour professor table.</abstract>
<keywords>office</keywords>
<keywords>during</keywords>
<keywords>more</keywords>
<keywords>apply</keywords>
<keywords>program</keywords>
<publication>
<venue>Nature</venue>
<year>2023</year>
<doi>10.1780/NyHo</doi>
</publication>
<citations>258</citations>
<funding_source>Espinoza, Khan and Lowe</funding_source>
</research_paper>


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

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

[Assistant]
Approach:
1. Task: Create api specification 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"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Assimilated neutral archive API</title>
<version>1.0.0</version>
</info>
<paths>
</sea>
<get>
<summary>Team happen challenge address expert manage beyond</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>
<//sea>
</paths>
</api_specification>


[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"?>
<research_paper>
<paper_id>arXiv:2023.99214</paper_id>
<title>Integrated mobile database</title>
<authors>
<name>Clayton Martinez</name>
<affiliation>Flores, Levy and Farmer</affiliation>
<email>kathy80@example.org</email>
</authors>
<authors>
<name>Susan Bennett</name>
<affiliation>Collins, Daniel and Lyons</affiliation>
<email>shawnjefferson@example.org</email>
</authors>
<abstract>Full with spend role first drive. Want man instead today bed hand character.</abstract>
<keywords>bed</keywords>
<keywords>very</keywords>
<keywords>population</keywords>
<publication>
<venue>Nature</venue>
<year>2023</year>
<doi>10.4640/CkqB</doi>
</publication>
<citations>395</citations>
<funding_source />
</research_paper>

[Assistant]
Approach:
1. Task: Convert research paper 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:
{
  "paper_id": "arXiv:2023.99214",
  "title": "Integrated mobile database",
  "authors": [
    {
      "name": "Clayton Martinez",
      "affiliation": "Flores, Levy and Farmer",
      "email": "kathy80@example.org"
    },
    {
      "name": "Susan Bennett",
      "affiliation": "Collins, Daniel and Lyons",
      "email": "shawnjefferson@example.org"
    }
  ],
  "abstract": "Full with spend role first drive. Want man instead today bed hand character.",
  "keywords": [
    "bed",
    "very",
    "population"
  ],
  "publication": {
    "venue": "Nature",
    "year": 2023,
    "doi": "10.4640/CkqB"
  },
  "citations": 395,
  "funding_source": null
}


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

[User] Output social media post as YAML.

[Assistant]
Approach:
1. Task: Create social media post 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:
post_id: POST-61935008
platform: instagram
user_id: ecd9585e-2adb-45f4-adda-e91c5f4f7ebe
username: halezachary
content: Treat second sing development scientist particularly their. Like question
  recently line top. Resource movie enter involve order stop region.
timestamp: '2026-01-07T13:51:25.597395'
hashtags:
- '#box'
- '#speak'
- '#reason'
engagement:
  likes: 4027
  shares: 604
  comments: 194


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

[User] Output product listing as JSON.

[Assistant]
Approach:
1. Task: Create product listing 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:
{
  "product_id": "PROD-891981",
  "name": "Focused background info-mediaries",
  "category": "books",
  "price": 16.4,
  "currency": "USD",
  "stock": 192,
  "is_available": true,
  "rating": 3.23,
  "reviews": 117,
  "specs": {
    "weight_kg": 31.51,
    "dimensions": "65x39x62cm"
  }
}


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

[User] Generate experiment result data in TOML format.

[Assistant]
Approach:
1. Task: Create experiment result 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:
experiment_id = "EXP-818679"
title = "Effect of begin on task"
conclusion = "non-significant"
[[results]]
metric = "safety"
baseline = 17.77
endpoint = 32.37
p_value = 0.477

[[results]]
metric = "safety"
baseline = 20.98
endpoint = 13.84
p_value = 0.2984

[methodology]
design = "RCT"
sample_size = 180
duration_days = 157


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

[User] Output customer review as TOML.

[Assistant]
Approach:
1. Task: Create customer review 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:
review_id = "REV-8549692"
product_id = "PROD-108019"
user_id = "a4c4fbe3-7a0e-49f5-b14b-2ab1ca2d6ed5"
rating = 4
title = "Development know write believe teacher ability."
content = "Guy generation provide economy test bit. Page cost and.\nArm test ok green. Likely card reality school stop something those.\nYour spend discuss yeah hear. Same language box us magazine simple."
date = "2026-01-06"
verified_purchase = true
helpful_votes = 22


[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: 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"?>
<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 TOML format. Think step-by-step, then generate syntactically perfect TOML.

[User]
Transform this JSON data into TOML 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 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. Transform values to match the target format specifications.

Output:
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."
[[paths."/peace".get.parameters]]
name = "param0"
in = "query"
type = "string"

[[paths."/peace".get.parameters]]
name = "param1"
in = "query"
type = "string"

[[paths."/peace".get.parameters]]
name = "param2"
in = "query"
type = "string"

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

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


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

[User] Output contract as CSV.

[Assistant]
Approach:
1. Task: Create contract 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:
contract_id,effective_date,parties,status,term_months,value
CTR-919818,,"[{""name"": ""Riggs, Carey and Rojas"", ""role"": ""party_a""}, {""name"": ""Mcdowell-Koch"", ""role"": ""party_b""}",active,18,911148
CTR-873474,2026-01-06,"[{""name"": ""Green, Richardson and Villarreal"", ""role"": ""party_a""}, {""name"": ""Padilla LLC"", ""role"": ""p",executed,49,521192
CTR-356485,2026-01-05,"[{""name"": ""Moore Ltd"", ""role"": ""party_a""}, {""name"": ""Haney-Kennedy"", ""role"": ""party_b""}]",pending,20,81785
CTR-188763,2026-01-03,"[{""name"": ""Cunningham-Gardner"", ""role"": ""party_a""}, {""name"": ""Herring and Sons"", ""role"": ""party_b""}]",executed,23,642374


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

[User] Output transaction record as CSV.

[Assistant]
Approach:
1. Task: Create transaction record 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:
customer_id,items,payment_method,subtotal,tax,timestamp,total,txn_id
b13e97b5-e84b-41ec-9dea-05b4809cdd35,"[{""sku"": ""SKU-36351"", ""qty"": 1, ""price"": 310.41}, {""sku"": ""SKU-26629"", ""qty"": 2, ""price"": 119.44}, {",apple_pay,994.66,143.59,2026-01-07T13:51:25.895711,1762.36,TXN-28879814
47c0ca0e-71c0-40c9-bc60-6f6c0a5c5ee9,"[{""sku"": ""SKU-63036"", ""qty"": 3, ""price"": 336.76}]",apple_pay,1359.46,152.59,2026-01-07T13:51:25.896867,1079.13,TXN-35184985
282d3952-5751-4af1-bfb1-85190eb5a566,"[{""sku"": ""SKU-20275"", ""qty"": 2, ""price"": 369.59}, {""sku"": ""SKU-77103"", ""qty"": 2, ""price"": 433.93}, {",paypal,1606.78,78.55,2026-01-07T13:51:25.896913,1187.48,TXN-70311000


[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: 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"?>
<news_article>
<content>Capital way what customer unit skill. Arm bar occur article mouth enjoy. Exactly approach mention single.
Strong who against entire.
Kid television artist dream back agency. Need main ago investment job behavior.</content>
<published>2026-01-03T04:54:27.964292</published>
<views>73181</views>
<headline>Vision-oriented analyzing groupware</headline>

Business

</news_article>


[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-3366717</article_id>
<headline>Integrated bi-directional complexity</headline>
<author>Linda Clark</author>
<published>2026-01-07T13:19:20.433040</published>

Tech

<content>Anything music blood how public to. Even student idea piece if. Whom phone rich long.
Look memory help find reduce. Structure most tough realize ground.
Around fear reduce ago. Thus moment letter evening stuff three.
Her themselves campaign cup four catch as. Part turn leg.</content>
<tags>necessary</tags>
<tags>listen</tags>
<tags>employee</tags>
<tags>here</tags>
<views>75939</views>
<shares>1143</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-3366717",
  "headline": "Integrated bi-directional complexity",
  "author": "Linda Clark",
  "published": "2026-01-07T13:19:20.433040",
  "section": "Tech",
  "content": "Anything music blood how public to. Even student idea piece if. Whom phone rich long.\nLook memory help find reduce. Structure most tough realize ground.\nAround fear reduce ago. Thus moment letter evening stuff three.\nHer themselves campaign cup four catch as. Part turn leg.",
  "tags": [
    "necessary",
    "listen",
    "employee",
    "here"
  ],
  "views": 75939,
  "shares": 1143
}


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

[User] Generate financial report data in YAML format.

[Assistant]
Approach:
1. Task: Create financial report 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:
company: Tucker and Sons
ticker: BPQE
quarter: Q4 2024
revenue: 70279854
expenses: 61737533
net_income: 12235621
eps: 3.52
metrics:
  profit_margin: 24.27
  roe: 16.15


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

[User] Create a YAML representation of course syllabus.

[Assistant]
Approach:
1. Task: Create course syllabus in YAML
2. Complexity: simple - 3-5 fields, minimal nesting
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:
instructor: Rachel Moreno DVM
credits: 4
course_id: CRS-8305
title: Open-architected even-keeled support 101
term: Spring 2023


[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:
{
  "course_id": "CRS-3440",
  "code": "KLD251",
  "title": "Reverse-engineered foreground infrastructure 101",
  "instructor": "Courtney Escobar",
  "credits": 4,
  "term": "Spring 2022",
  "schedule": [
    {
      "week": 1,
      "topic": "despite"
    },
    {
      "week": 2,
      "topic": "choose"
    },
    {
      "week": 3,
      "topic": "action"
    },
    {
      "week": 4,
      "topic": "couple"
    },
    {
      "week": 5,
      "topic": "big"
    },
    {
      "week": 6,
      "topic": "trade"
    },
    {
      "week": 7,
      "topic": "measure"
    },
    {
      "week": 8,
      "topic": "music"
    }
  ],
  "grading": {
    "homework": 30,
    "midterm": 30,
    "final": 40
  }
}

[Assistant]
Approach:
1. Task: Convert course syllabus 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:
code,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title
KLD251,CRS-3440,4,40,30,30,Courtney Escobar,"[{""week"": 1, ""topic"": ""despite""}, {""week"": 2, ""topic"": ""choose""}, {""week"": 3, ""topic"": ""action""}, {""",Spring 2022,Reverse-engineered foreground infrastructure 101
OND359,CRS-1832,4,40,30,30,Hector Wilson,"[{""week"": 1, ""topic"": ""general""}, {""week"": 2, ""topic"": ""bag""}, {""week"": 3, ""topic"": ""significant""}, ",Fall 2023,Pre-emptive multi-state alliance 101
AXT418,CRS-6280,3,40,30,30,Robert Hall,"[{""week"": 1, ""topic"": ""check""}, {""week"": 2, ""topic"": ""south""}, {""week"": 3, ""topic"": ""him""}, {""week"":",Fall 2021,Focused mission-critical success 101


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

[User] Output customer review as JSON.

[Assistant]
Approach:
1. Task: Create customer review 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:
{
  "review_id": "REV-2691236",
  "product_id": "PROD-245093",
  "user_id": "98b0ec97-f0e6-4eda-907b-c1488d5de2f5",
  "rating": 1,
  "title": "Now new sell exist just.",
  "content": "Issue suddenly such maybe. Military they second staff end agreement.\nClose that speech alone know wish matter. Finally adult statement method.",
  "date": "2026-01-02",
  "verified_purchase": false,
  "helpful_votes": 34
}


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

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

[Assistant]
Approach:
1. Task: Create api specification 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:
openapi = "3.0.0"

[info]
title = "Ameliorated radical initiative API"
version = "1.0.0"

[paths."/population".get]
summary = "Lead room develop man according street century."
[[paths."/population".get.parameters]]
name = "param0"
in = "query"
type = "string"

[[paths."/population".get.parameters]]
name = "param1"
in = "query"
type = "string"

[[paths."/population".get.parameters]]
name = "param2"
in = "query"
type = "string"

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

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


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

[User]
Reformat the data below from YAML to CSV:
rx_id: RX-6036951
patient_mrn: MRN-440463
prescriber: Lisa Mathews
date: '2026-01-05'
medications:
- name: Metformin
  dosage: 20mg
  frequency: TID
  quantity: 90

[Assistant]
Approach:
1. Task: Convert prescription 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:
date,medications,patient_mrn,prescriber,rx_id
2026-01-05,"[{""name"": ""Metformin"", ""dosage"": ""20mg"", ""frequency"": ""TID"", ""quantity"": 90}]",MRN-440463,Lisa Mathews,RX-6036951
2026-01-01,"[{""name"": ""Metformin"", ""dosage"": ""5mg"", ""frequency"": ""daily"", ""quantity"": 30}]",MRN-186115,Autumn Berger,RX-9172149
2026-01-06,"[{""name"": ""Metformin"", ""dosage"": ""10mg"", ""frequency"": ""TID"", ""quantity"": 60}]",MRN-749981,Ryan Randall,RX-8059218


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

[User]
Convert the following JSON to XML:
{
  "txn_id": "TXN-98000345",
  "customer_id": "681a59bc-1151-4d49-8e75-1af0878315cb",
  "timestamp": "2026-01-07T13:51:26.087659",
  "items": [
    {
      "sku": "SKU-50616",
      "qty": 3,
      "price": 180.94
    },
    {
      "sku": "SKU-82812",
      "qty": 5,
      "price": 490.31
    }
  ],
  "subtotal": 948.16,
  "tax": 93.65,
  "total": 1389.7,
  "payment_method": "credit_card"
}

[Assistant]
Approach:
1. Task: Convert transaction record 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"?>
<transaction_record>
<txn_id>TXN-98000345</txn_id>
<customer_id>681a59bc-1151-4d49-8e75-1af0878315cb</customer_id>
<timestamp>2026-01-07T13:51:26.087659</timestamp>
<items>
<sku>SKU-50616</sku>
<qty>3</qty>
<price>180.94</price>
</items>
<items>
<sku>SKU-82812</sku>
<qty>5</qty>
<price>490.31</price>
</items>
<subtotal>948.16</subtotal>
<tax>93.65</tax>
<total>1389.7</total>
<payment_method>credit_card</payment_method>
</transaction_record>


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

[User] Create a CSV representation of course syllabus.

[Assistant]
Approach:
1. Task: Create course syllabus 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:
code,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title
TMG245,CRS-6496,,,,,Maria Bowers,"[{""week"": 1, ""topic"": ""situation""}, {""week"": 2, ""topic"": ""firm""}, {""week"": 3, ""topic"": ""involve""}, {",,
TFW250,CRS-4707,4,40,30,30,James Cox,"[{""week"": 1, ""topic"": ""song""}, {""week"": 2, ""topic"": ""goal""}, {""week"": 3, ""topic"": ""stock""}, {""week"":",Fall 2020,Networked optimizing extranet 101
BFK298,CRS-8927,3,40,30,30,Julia Perez,"[{""week"": 1, ""topic"": ""between""}, {""week"": 2, ""topic"": ""we""}, {""week"": 3, ""topic"": ""here""}, {""week"":",Spring 2021,Stand-alone static secured line 101


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

[User]
Reformat the data below from JSON to YAML:
{
  "effective_date": "2026-01-02",
  "term_months": 54,
  "status": "pending"
}

[Assistant]
Approach:
1. Task: Convert contract from JSON to YAML
2. Complexity: simple - 3-5 fields, minimal nesting
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:
effective_date: '2026-01-02'
term_months: 54
status: pending