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

[User]
Transform this XML data into CSV format:
<?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 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. Transform values to match the target format specifications.

Output:
abstract,authors,citations,date,funding_source,keywords,medications,paper_id,prescriber,publication_doi,publication_venue,publication_year,title
,,,2026-01-03,,,"[{""name"": ""Atorvastatin"", ""dosage"": ""5mg"", ""frequency"": ""BID"", ""quantity"": 30}]",,Isaac Howard,,,,
Generation although above offer head. Thing individual listen police. Business already box.,"[{""name"": ""Jeffrey Smith"", ""affiliation"": ""Johnson, Thompson and Le"", ""email"": ""sonya91@example.net""",191,,None,"[""than"", ""pass"", ""peace""]",,arXiv:2020.30041,,10.1917/Ctdt,Cell,2021,Object-based next generation open system
Become know number high feeling. Line Mrs city here say. Plan realize each environmental six.,"[{""name"": ""Brandon Hughes"", ""affiliation"": ""White PLC"", ""email"": ""kristin82@example.org""}, {""name"": ",372,,None,"[""her"", ""finish"", ""decade""]",,arXiv:2021.16892,,10.3630/jXSO,Cell,2020,Phased static standardization
Bank building hard person now. Relate article already many individual.,"[{""name"": ""Steven Orozco"", ""affiliation"": ""Davis-Robles"", ""email"": ""wellskelly@example.net""}, {""name",180,,None,"[""decade"", ""example"", ""food"", ""green""]",,arXiv:2024.64378,,10.4689/BPUR,Cell,2020,Function-based even-keeled implementation
Service painting room. Hold capital major else relate if. High military whom listen include discuss ,"[{""name"": ""Caleb Perez"", ""affiliation"": ""Savage-Washington"", ""email"": ""leroy85@example.org""}, {""name",203,,Martin-Barron,"[""over"", ""offer"", ""while""]",,arXiv:2021.47561,,10.6938/jqbb,Cell,2021,Intuitive human-resource archive


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

[User]
Convert the following JSON to XML:
{
  "contract_id": "CTR-291572",
  "parties": [
    {
      "name": "Smith and Sons",
      "role": "party_a"
    },
    {
      "name": "Avila-Campbell",
      "role": "party_b"
    }
  ],
  "effective_date": "2026-01-03",
  "term_months": 47,
  "value": 297446,
  "status": "pending"
}

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

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


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

[User] Create a TOML representation of contract.

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

Output:
contract_id = "CTR-291572"
effective_date = "2026-01-03"
term_months = 47
value = 297446
status = "pending"
[[parties]]
name = "Smith and Sons"
role = "party_a"

[[parties]]
name = "Avila-Campbell"
role = "party_b"


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

[User] Produce a YAML document for a prescription.

[Assistant]
Approach:
1. Task: Create prescription 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:
rx_id: RX-5973418
patient_mrn: MRN-615844
prescriber: Brian Erickson
date: '2026-01-01'
medications:
- name: Lisinopril
  dosage: 20mg
  frequency: TID
  quantity: 60
- name: Metformin
  dosage: 20mg
  frequency: daily
  quantity: 60


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

[User]
Reformat the data below from JSON to XML:
{
  "assessment_id": "ASMT-482875",
  "student_id": "STU-646713",
  "course_id": "CRS-2679",
  "type": "assignment",
  "date": "2026-01-01",
  "scores": [
    {
      "question": 1,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 2,
      "points_earned": 9,
      "points_possible": 10
    },
    {
      "question": 3,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 4,
      "points_earned": 7,
      "points_possible": 10
    },
    {
      "question": 5,
      "points_earned": 3,
      "points_possible": 10
    },
    {
      "question": 6,
      "points_earned": 8,
      "points_possible": 10
    },
    {
      "question": 7,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 8,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 9,
      "points_earned": 9,
      "points_possible": 10
    },
    {
      "question": 10,
      "points_earned": 8,
      "points_possible": 10
    }
  ],
  "total_score": 62,
  "percentage": 98.87,
  "grade": "C"
}

[Assistant]
Approach:
1. Task: Convert student assessment 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"?>
<student_assessment>
<assessment_id>ASMT-482875</assessment_id>
<student_id>STU-646713</student_id>
<course_id>CRS-2679</course_id>
<type>assignment</type>
<date>2026-01-01</date>
<scores>
<question>1</question>
<points_earned>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>2</question>
<points_earned>9</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>7</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>5</question>
<points_earned>3</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>6</question>
<points_earned>8</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>7</question>
<points_earned>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>8</question>
<points_earned>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>9</question>
<points_earned>9</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>10</question>
<points_earned>8</points_earned>
<points_possible>10</points_possible>
</scores>
<total_score>62</total_score>
<percentage>98.87</percentage>
<grade>C</grade>
</student_assessment>


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

[User] Create a TOML representation of product listing.

[Assistant]
Approach:
1. Task: Create product listing 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:
name = "Universal fault-tolerant service-desk"
price = 907.33
reviews = 493

[specs]
weight_kg = 8.02
dimensions = "62x22x22cm"


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

[User] Generate sales analytics data in JSON format.

[Assistant]
Approach:
1. Task: Create sales analytics 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:
{
  "period": "April 2020",
  "total_revenue": 1914989,
  "units_sold": 47758,
  "channels": [
    {
      "name": "wholesale",
      "revenue": 3617590,
      "growth": 20.48
    },
    {
      "name": "online",
      "revenue": 654207,
      "growth": 24.4
    }
  ],
  "top_products": [
    {
      "sku": "SKU-4328",
      "sales": 466200
    },
    {
      "sku": "SKU-2589",
      "sales": 244105
    },
    {
      "sku": "SKU-7725",
      "sales": 25778
    }
  ]
}


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

[User]
Reformat the data below from CSV to YAML:
abstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/base_get_parameters,paths_/base_get_responses_200_description,paths_/base_get_responses_400_description,paths_/base_get_summary,publication_doi,publication_venue,publication_year,title
,,,,Horizontal interactive project API,1.0.0,,3.0.0,,"[{""name"": ""param0"", ""in"": ""query"", ""type"": ""string""}]",Success,Bad Request,Management send father actually special image.,,,,
Game these campaign. Everybody need century present. Write certainly rock drive offer anything.,"[{""name"": ""Elizabeth Travis"", ""affiliation"": ""Peters-Bell"", ""email"": ""bgomez@example.net""}, {""name"":",468,Carr Ltd,,,"[""rather"", ""be"", ""whom"", ""enter"", ""data""]",,arXiv:2020.91324,,,,,10.9988/bkMi,Cell,2022,Cloned eco-centric complexity
"Color office these direction action.
Letter through picture which. Create nature leg former.","[{""name"": ""Micheal Copeland"", ""affiliation"": ""Griffin LLC"", ""email"": ""dhill@example.com""}, {""name"": ",426,None,,,"[""consider"", ""beyond"", ""security"", ""term"", ""relate""]",,arXiv:2023.83336,,,,,10.4969/UEsD,Science,2024,Cross-platform mission-critical toolset

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

Output:
openapi: 3.0.0
info:
  title: Horizontal interactive project API
  version: 1.0.0
paths:
  /base:
    get:
      summary: Management send father actually special image.
      parameters:
      - name: param0
        in: query
        type: string
      responses:
        '200':
          description: Success
        '400':
          description: Bad Request


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

[User] Generate course syllabus data in JSON format.

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

Output:
{
  "course_id": "CRS-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
  }
}


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

[User] Generate lab result data in CSV format.

[Assistant]
Approach:
1. Task: Create lab result in CSV
2. Complexity: 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:
order_date,panel,patient_mrn,result_id,results
2026-01-03,CMP,MRN-322322,LAB-9548003,"[{""test"": ""Glucose"", ""value"": 67.0, ""unit"": ""g/dL"", ""flag"": ""high""}, {""test"": ""Hemoglobin"", ""value"":"
2026-01-04,CMP,MRN-774832,LAB-7714416,"[{""test"": ""WBC"", ""value"": 129.7, ""unit"": ""mg/dL"", ""flag"": ""low""}, {""test"": ""WBC"", ""value"": 193.4, ""u"
2026-01-05,Lipid,MRN-430139,LAB-1961466,"[{""test"": ""Hemoglobin"", ""value"": 165.9, ""unit"": ""g/dL"", ""flag"": ""normal""}, {""test"": ""WBC"", ""value"": "


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

[User] Output student assessment as YAML.

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

Output:
assessment_id: ASMT-482875
student_id: STU-646713
course_id: CRS-2679
type: assignment
date: '2026-01-01'
scores:
- question: 1
  points_earned: 1
  points_possible: 10
- question: 2
  points_earned: 9
  points_possible: 10
- question: 3
  points_earned: 1
  points_possible: 10
- question: 4
  points_earned: 7
  points_possible: 10
- question: 5
  points_earned: 3
  points_possible: 10
- question: 6
  points_earned: 8
  points_possible: 10
- question: 7
  points_earned: 1
  points_possible: 10
- question: 8
  points_earned: 1
  points_possible: 10
- question: 9
  points_earned: 9
  points_possible: 10
- question: 10
  points_earned: 8
  points_possible: 10
total_score: 62
percentage: 98.87
grade: C


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

[User]
Convert the following JSON to XML:
{
  "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
  }
}

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


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

[User]
Transform this XML data into JSON format:
<?xml version="1.0" encoding="UTF-8"?>
<transaction_record>
<txn_id>TXN-79156891</txn_id>
<customer_id>5450ecc9-30b8-498f-a527-04ec3de16dd8</customer_id>
<timestamp>2026-01-07T13:51:26.258900</timestamp>
<items>
<sku>SKU-81880</sku>
<qty>4</qty>
<price>401.7</price>
</items>
<items>
<sku>SKU-99718</sku>
<qty>5</qty>
<price>334.37</price>
</items>
<items>
<sku>SKU-65882</sku>
<qty>3</qty>
<price>292.8</price>
</items>
<items>
<sku>SKU-88201</sku>
<qty>2</qty>
<price>114.91</price>
</items>
<subtotal>258.62</subtotal>
<tax>22.79</tax>
<total>1713.37</total>
<payment_method>paypal</payment_method>
</transaction_record>

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

Output:
{
  "txn_id": "TXN-79156891",
  "customer_id": "5450ecc9-30b8-498f-a527-04ec3de16dd8",
  "timestamp": "2026-01-07T13:51:26.258900",
  "items": [
    {
      "sku": "SKU-81880",
      "qty": 4,
      "price": 401.7
    },
    {
      "sku": "SKU-99718",
      "qty": 5,
      "price": 334.37
    },
    {
      "sku": "SKU-65882",
      "qty": 3,
      "price": 292.8
    },
    {
      "sku": "SKU-88201",
      "qty": 2,
      "price": 114.91
    }
  ],
  "subtotal": 258.62,
  "tax": 22.79,
  "total": 1713.37,
  "payment_method": "paypal"
}


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

[User] Generate prescription data in TOML format.

[Assistant]
Approach:
1. Task: Create prescription 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:
rx_id = "RX-4278484"
patient_mrn = "MRN-990980"
prescriber = "Andrew Kelly"
date = "2026-01-06"
[[medications]]
name = "Metformin"
dosage = "10mg"
frequency = "BID"
quantity = 30

[[medications]]
name = "Atorvastatin"
dosage = "10mg"
frequency = "BID"
quantity = 90


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

[User]
Convert the following JSON to XML:
{
  "review_id": "REV-8075236",
  "product_id": "PROD-326180",
  "user_id": "e70c9373-b1ad-41a5-8939-e3c28041d8f5",
  "rating": 4,
  "title": "Most teacher Mrs system watch.",
  "content": "Address music major. Magazine three about. Security ready result improve.\nHand other collection name wife remain. Speech perhaps newspaper. Talk place third about writer billion physical.",
  "date": "2026-01-03",
  "verified_purchase": false,
  "helpful_votes": 50
}

[Assistant]
Approach:
1. Task: Convert customer review 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"?>
<customer_review>
<review_id>REV-8075236</review_id>
<product_id>PROD-326180</product_id>
<user_id>e70c9373-b1ad-41a5-8939-e3c28041d8f5</user_id>
<rating>4</rating>
<title>Most teacher Mrs system watch.</title>
<content>Address music major. Magazine three about. Security ready result improve.
Hand other collection name wife remain. Speech perhaps newspaper. Talk place third about writer billion physical.</content>
<date>2026-01-03</date>
<verified_purchase>False</verified_purchase>
<helpful_votes>50</helpful_votes>
</customer_review>


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

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

[Assistant]
Approach:
1. Task: Create experiment result 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"?>
<experiment_result>
<experiment_id>EXP-574681</experiment_id>
<title>Effect of anyone on society</title>
<methodology>
<design>cohort</design>
<sample_size>560</sample_size>
<duration_days>320</duration_days>
</methodology>
<results>
<metric>efficacy</metric>
<baseline>50.77</baseline>
<endpoint>70.83</endpoint>
<p_value>0.3046</p_value>
</results>
<results>
<metric>efficacy</metric>
<baseline>96.52</baseline>
<endpoint>82.25</endpoint>
<p_value>0.0326</p_value>
</results>
<results>
<metric>safety</metric>
<baseline>43.38</baseline>
<endpoint>72.88</endpoint>
<p_value>0.2787</p_value>
</results>
<results>
<metric>safety</metric>
<baseline>17.71</baseline>
<endpoint>95.37</endpoint>
<p_value>0.4542</p_value>
</results>
<conclusion>non-significant</conclusion>
</experiment_result>


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

[User] Output product listing as XML.

[Assistant]
Approach:
1. Task: Create product listing 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"?>
<product_listing>
<product_id>PROD-651261</product_id>
<name>Cross-platform scalable protocol</name>
<category>clothing</category>
<price>855.77</price>
<currency>USD</currency>
<stock>343</stock>
<is_available>True</is_available>
<rating>3.23</rating>
<reviews>830</reviews>
<specs>
<weight_kg>21.29</weight_kg>
<dimensions>84x20x91cm</dimensions>
</specs>
</product_listing>


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

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

[Assistant]
Approach:
1. Task: Create social media post 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:
username = "nicholasalvarez"
post_id = "POST-61351209"
hashtags = [ "#pretty", "#admit", "#available",]
user_id = "5e546096-8461-4a3f-84e6-813e9e89a39c"

[engagement]
likes = 6676
shares = 196
comments = 84


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

[User]
Convert the following CSV to XML:
assessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f
"[{""problem"": ""diabetes"", ""icd10"": ""J46""}]",fever,2026-01-06,CN-7237025,53,F,MRN-276187,95/82,103,102.9
"[{""problem"": ""hypertension"", ""icd10"": ""J61""}, {""problem"": ""diabetes"", ""icd10"": ""J13""}]",headache,2026-01-04,CN-4133145,71,M,MRN-677478,92/71,64,101.5
"[{""problem"": ""diabetes"", ""icd10"": ""K78""}, {""problem"": ""diabetes"", ""icd10"": ""J94""}]",headache,2026-01-05,CN-9624578,49,F,MRN-343832,176/78,116,97.9
"[{""problem"": ""hypertension"", ""icd10"": ""I14""}, {""problem"": ""hypertension"", ""icd10"": ""K62""}, {""problem",chest pain,2026-01-01,CN-3195889,20,F,MRN-415814,159/110,79,99.6
"[{""problem"": ""hypertension"", ""icd10"": ""K86""}]",chest pain,2026-01-01,CN-5641625,78,M,MRN-335317,164/63,118,101.9

[Assistant]
Approach:
1. Task: Convert clinical note 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"?>
<clinical_note>
<note_id>CN-7237025</note_id>
<patient>
<mrn>MRN-276187</mrn>
<age>53</age>
<gender>F</gender>
</patient>
<encounter_date>2026-01-06</encounter_date>
<chief_complaint>fever</chief_complaint>
<vitals>
<bp>95/82</bp>

103

<temp_f>102.9</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]
Reformat the data below from JSON to TOML:
{
  "course_id": "CRS-6496",
  "code": "TMG245",
  "instructor": "Maria Bowers",
  "schedule": [
    {
      "week": 1,
      "topic": "situation"
    },
    {
      "week": 2,
      "topic": "firm"
    },
    {
      "week": 3,
      "topic": "involve"
    },
    {
      "week": 4,
      "topic": "change"
    },
    {
      "week": 5,
      "topic": "yard"
    },
    {
      "week": 6,
      "topic": "morning"
    },
    {
      "week": 7,
      "topic": "other"
    },
    {
      "week": 8,
      "topic": "left"
    }
  ]
}

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

Output:
course_id = "CRS-6496"
code = "TMG245"
instructor = "Maria Bowers"
[[schedule]]
week = 1
topic = "situation"

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

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

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

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

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

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

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


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

[User]
Convert the following JSON to XML:
{
  "customer_id": "5642be10-2f96-4bf3-93bb-ea73b498db7e",
  "timestamp": "2026-01-07T13:51:27.704310",
  "total": 2159.3,
  "tax": 150.65,
  "items": [
    {
      "sku": "SKU-21107",
      "qty": 2,
      "price": 436.86
    },
    {
      "sku": "SKU-34269",
      "qty": 3,
      "price": 260.71
    },
    {
      "sku": "SKU-81249",
      "qty": 3,
      "price": 416.92
    },
    {
      "sku": "SKU-97216",
      "qty": 3,
      "price": 177.96
    }
  ]
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<transaction_record>
<customer_id>5642be10-2f96-4bf3-93bb-ea73b498db7e</customer_id>
<timestamp>2026-01-07T13:51:27.704310</timestamp>
<total>2159.3</total>
<tax>150.65</tax>
<items>
<sku>SKU-21107</sku>
<qty>2</qty>
<price>436.86</price>
</items>
<items>
<sku>SKU-34269</sku>
<qty>3</qty>
<price>260.71</price>
</items>
<items>
<sku>SKU-81249</sku>
<qty>3</qty>
<price>416.92</price>
</items>
<items>
<sku>SKU-97216</sku>
<qty>3</qty>
<price>177.96</price>
</items>
</transaction_record>


[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-3281345</article_id>
<headline>Streamlined object-oriented toolset</headline>
<author>James Dunn</author>
<published>2026-01-03T08:23:33.060508</published>

Politics

<content>Win take among professor. Glass reflect black similar future. Risk than tree.
Economic sit plan. Available then already skill up reason back. Course his threat growth physical parent truth.
Laugh article pull goal. Believe those few.</content>
<tags>hit</tags>
<tags>summer</tags>
<tags>official</tags>
<tags>rather</tags>
<views>75669</views>
<shares>293</shares>
</news_article>

[Assistant]
Approach:
1. Task: Convert news article 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:
{
  "article_id": "ART-3281345",
  "headline": "Streamlined object-oriented toolset",
  "author": "James Dunn",
  "published": "2026-01-03T08:23:33.060508",
  "section": "Politics",
  "content": "Win take among professor. Glass reflect black similar future. Risk than tree.\nEconomic sit plan. Available then already skill up reason back. Course his threat growth physical parent truth.\nLaugh article pull goal. Believe those few.",
  "tags": [
    "hit",
    "summer",
    "official",
    "rather"
  ],
  "views": 75669,
  "shares": 293
}


[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:
{
  "post_id": "POST-20150897",
  "platform": "instagram",
  "user_id": "ace3958f-4578-4576-9236-9cbfc1f62953",
  "username": "spatrick",
  "content": "About industry woman size. Available box return camera public time. Establish outside ability sport describe air who.\nCertain miss girl different both wife. Blood relationship if model.",
  "timestamp": "2026-01-07T13:51:25.995017",
  "hashtags": [
    "#share",
    "#prevent",
    "#entire",
    "#owner"
  ],
  "engagement": {
    "likes": 3129,
    "shares": 891,
    "comments": 28
  }
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<social_media_post>
<post_id>POST-20150897</post_id>
<platform>instagram</platform>
<user_id>ace3958f-4578-4576-9236-9cbfc1f62953</user_id>
<username>spatrick</username>
<content>About industry woman size. Available box return camera public time. Establish outside ability sport describe air who.
Certain miss girl different both wife. Blood relationship if model.</content>
<timestamp>2026-01-07T13:51:25.995017</timestamp>
<hashtags>#share</hashtags>
<hashtags>#prevent</hashtags>
<hashtags>#entire</hashtags>
<hashtags>#owner</hashtags>
<engagement>
<likes>3129</likes>
<shares>891</shares>
<comments>28</comments>
</engagement>
</social_media_post>


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

[User] Create a JSON representation of error log.

[Assistant]
Approach:
1. Task: Create error log 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:
{
  "error_id": "69ef512f-ddd4-415a-b99a-51e8f50d151c",
  "timestamp": "2026-01-07T13:51:25.644182",
  "level": "WARNING",
  "service": "fillService",
  "message": "Minute heart focus arrive.",
  "stack_trace": [
    "at administration.py:211",
    "at lawyer.py:276",
    "at discussion.py:115"
  ],
  "context": {
    "user_id": "29c6c678-1224-4e33-8bc1-e94776cd4eb2",
    "request_id": "42e054d1-48f9-4a1c-ad7b-82ed505d6250"
  }
}


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

[User] Output clinical note as XML.

[Assistant]
Approach:
1. Task: Create clinical note 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"?>
<clinical_note>
<note_id>CN-6709459</note_id>
<patient>
<mrn>MRN-104418</mrn>
<age>50</age>
<gender>M</gender>
</patient>
<encounter_date>2026-01-03</encounter_date>
<chief_complaint>fever</chief_complaint>
<vitals>
<bp>143/96</bp>

69

<temp_f>101.3</temp_f>
</vitals>
<assessment>
<problem>diabetes</problem>
<icd10>J90</icd10>
</assessment>
<assessment>
<problem>hypertension</problem>
<icd10>I22</icd10>
</assessment>
<assessment>
<problem>hypertension</problem>
<icd10>K97</icd10>
</assessment>
</clinical_note>


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

[User] Create a TOML representation of research paper.

[Assistant]
Approach:
1. Task: Create research paper 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:
title = "Seamless cohesive projection"
abstract = "Middle several interesting move. Wrong represent guess threat. Once paper represent."
[[authors]]
name = "Laura White"
affiliation = "Coleman, Johnson and Ross"
email = "jillcollins@example.com"

[[authors]]
name = "Sarah Woods"
affiliation = "Durham, Thompson and White"
email = "sbeard@example.com"


[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"?>
<financial_report>
<company>Leon-Lewis</company>
<ticker>FGCI</ticker>
<quarter>Q4 2022</quarter>
<revenue>56885685</revenue>
<expenses>46362888</expenses>
<net_income>14538939</net_income>
<eps>7.9</eps>
<metrics>
<profit_margin>25.04</profit_margin>
<roe>5.27</roe>
</metrics>
</financial_report>

[Assistant]
Approach:
1. Task: Convert financial report 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:
{
  "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 XML format. Think step-by-step, then generate syntactically perfect XML.

[User]
Convert the following JSON to XML:
{
  "article_id": "ART-5646798",
  "headline": "Switchable hybrid groupware",
  "author": "Joshua Bell",
  "published": "2026-01-05T05:31:42.088007",
  "section": "Business",
  "content": "List road lay not year. Congress gas full particular according. Prevent hear century game friend civil live.\nPossible option especially woman. Ahead down suffer doctor six traditional. Prove ready American star impact operation just. Difficult yourself difficult base of four letter.",
  "tags": [
    "author",
    "son",
    "food"
  ],
  "views": 74484,
  "shares": 596
}

[Assistant]
Approach:
1. Task: Convert news article 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"?>
<news_article>
<article_id>ART-5646798</article_id>
<headline>Switchable hybrid groupware</headline>
<author>Joshua Bell</author>
<published>2026-01-05T05:31:42.088007</published>

Business

<content>List road lay not year. Congress gas full particular according. Prevent hear century game friend civil live.
Possible option especially woman. Ahead down suffer doctor six traditional. Prove ready American star impact operation just. Difficult yourself difficult base of four letter.</content>
<tags>author</tags>
<tags>son</tags>
<tags>food</tags>
<views>74484</views>
<shares>596</shares>
</news_article>


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

[User] Output clinical note as XML.

[Assistant]
Approach:
1. Task: Create clinical note 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"?>
<clinical_note>
<note_id>CN-5754690</note_id>
<patient>
<mrn>MRN-521303</mrn>
<age>32</age>
<gender>M</gender>
</patient>
<encounter_date>2026-01-05</encounter_date>
<chief_complaint>fever</chief_complaint>
<vitals>
<bp>101/104</bp>

85

<temp_f>99.3</temp_f>
</vitals>
<assessment>
<problem>diabetes</problem>
<icd10>K80</icd10>
</assessment>
</clinical_note>


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

[User] Create a XML representation of financial report.

[Assistant]
Approach:
1. Task: Create financial report in XML
2. Complexity: 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"?>
<financial_report>
<company>Richard Ltd</company>
<ticker>XHCL</ticker>
<quarter>Q4 2020</quarter>
<revenue>71255223</revenue>
<expenses>54916122</expenses>
<net_income>1190834</net_income>
<eps>4.63</eps>
<metrics>
<profit_margin>14.39</profit_margin>
<roe>19.33</roe>
</metrics>
</financial_report>


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

[User] Produce a TOML document for a financial report.

[Assistant]
Approach:
1. Task: Create financial report 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:
company = "Becker-Martinez"
ticker = "QZXR"
quarter = "Q4 2021"
revenue = 48919598
expenses = 50274851
net_income = 7284021
eps = 2.39

[metrics]
profit_margin = 17.0
roe = 10.6


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

[User] Produce a XML document for a sales analytics.

[Assistant]
Approach:
1. Task: Create sales analytics 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"?>
<sales_analytics>
<period>June 2021</period>
<total_revenue>1467254</total_revenue>
<units_sold>63744</units_sold>
<channels>
<name>wholesale</name>
<revenue>2975287</revenue>
<growth>-1.88</growth>
</channels>
<channels>
<name>online</name>
<revenue>2665464</revenue>
<growth>14.77</growth>
</channels>
<top_products>
<sku>SKU-1172</sku>
<sales>348860</sales>
</top_products>
<top_products>
<sku>SKU-4431</sku>
<sales>479568</sales>
</top_products>
<top_products>
<sku>SKU-6244</sku>
<sales>245719</sales>
</top_products>
</sales_analytics>


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

[User] Create a TOML representation of transaction record.

[Assistant]
Approach:
1. Task: Create transaction record 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:
total = 1900.4
payment_method = "apple_pay"
[[items]]
sku = "SKU-89816"
qty = 1
price = 437.44

[[items]]
sku = "SKU-65650"
qty = 1
price = 455.72

[[items]]
sku = "SKU-98183"
qty = 3
price = 337.62


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

[User] Output sales analytics as CSV.

[Assistant]
Approach:
1. Task: Create sales analytics 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:
abstract,authors,channels,citations,funding_source,keywords,paper_id,period,publication_doi,publication_venue,publication_year,title,top_products,total_revenue,units_sold
,,"[{""name"": ""wholesale"", ""revenue"": 3622404, ""growth"": -8.05}, {""name"": ""online"", ""revenue"": 1893923, ",,,,,January 2022,,,,,"[{""sku"": ""SKU-2073"", ""sales"": 98550}, {""sku"": ""SKU-3707"", ""sales"": 233488}, {""sku"": ""SKU-7843"", ""sal",7456708,82349
Our large outside guess American fill leave. Nation cost who fish message road. Share learn our choo,"[{""name"": ""Steven Mccall"", ""affiliation"": ""Miller-Hart"", ""email"": ""xbeck@example.org""}, {""name"": ""Jo",,80,Lane-Cooper,"[""allow"", ""agent"", ""industry"", ""not"", ""agency""]",arXiv:2021.21546,,10.8747/ADMz,Nature,2021,Pre-emptive responsive strategy,,,
"Such save oil strong town. Response hand since industry agree type job.
Enjoy program per like may. ","[{""name"": ""Andrew Krueger"", ""affiliation"": ""Doyle-Horton"", ""email"": ""zcole@example.com""}, {""name"": """,,116,None,"[""six"", ""positive"", ""cup"", ""might""]",arXiv:2023.52285,,10.5257/sCTQ,Science,2021,Team-oriented foreground access,,,


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

[User] Create a YAML representation of financial report.

[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: Thompson, Yang and Roberts
ticker: ATOM
quarter: Q1 2022
revenue: 59725729
expenses: 36274579
net_income: 7802792
eps: 8.84
metrics:
  profit_margin: 17.46
  roe: 22.69


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

[User] Produce a JSON document for a student assessment.

[Assistant]
Approach:
1. Task: Create student assessment 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:
{
  "date": "2026-01-01",
  "total_score": 85,
  "student_id": "STU-920172"
}


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

[User] Generate product listing data in YAML format.

[Assistant]
Approach:
1. Task: Create product listing 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:
product_id: PROD-597223
name: Proactive tertiary database
category: books
price: 435.77
currency: USD
stock: 111
is_available: true
rating: 1.73
reviews: 539
specs:
  weight_kg: 19.61
  dimensions: 87x91x85cm


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

[User] Generate social media post data in XML format.

[Assistant]
Approach:
1. Task: Create social media post 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"?>
<social_media_post>
<post_id>POST-94493547</post_id>
<platform>instagram</platform>
<user_id>ebddd714-2a63-4fd6-985c-fb7fe32db0b4</user_id>
<username>laura52</username>
<content>Property political your form stand cup blood. Business later seem sea represent enough relationship memory.
What ok that look past. Budget understand mouth during brother pull type spring.</content>
<timestamp>2026-01-07T13:51:27.134920</timestamp>
<hashtags>#red</hashtags>
<hashtags>#hotel</hashtags>
<hashtags>#create</hashtags>
<engagement>
<likes>8599</likes>
<shares>93</shares>
<comments>39</comments>
</engagement>
</social_media_post>


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

[User] Generate transaction record data in CSV format.

[Assistant]
Approach:
1. Task: Create transaction record in CSV
2. Complexity: 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
13707a49-23b0-4133-8216-7e83986c9575,"[{""sku"": ""SKU-82899"", ""qty"": 5, ""price"": 298.29}, {""sku"": ""SKU-51515"", ""qty"": 4, ""price"": 343.78}, {",credit_card,1914.1,175.88,2026-01-07T13:51:27.689251,1360.6,TXN-60159725
01117b4a-3d26-4d2d-8a76-96a79c487fa0,"[{""sku"": ""SKU-21681"", ""qty"": 4, ""price"": 183.49}, {""sku"": ""SKU-89553"", ""qty"": 1, ""price"": 449.84}, {",credit_card,1020.65,62.25,2026-01-07T13:51:27.690581,662.27,TXN-98601535
5e7a7426-8cef-41a9-a8d1-b12e8cba1633,"[{""sku"": ""SKU-63528"", ""qty"": 5, ""price"": 103.8}, {""sku"": ""SKU-10678"", ""qty"": 3, ""price"": 91.67}, {""s",apple_pay,1539.37,49.13,2026-01-07T13:51:27.690641,1811.28,TXN-43546008
630ccf7f-b60b-4f01-87d5-206096e709ad,"[{""sku"": ""SKU-47193"", ""qty"": 2, ""price"": 481.57}, {""sku"": ""SKU-92985"", ""qty"": 2, ""price"": 156.73}]",apple_pay,460.35,96.95,2026-01-07T13:51:27.690685,1234.65,TXN-97101482
afc459ac-6d24-4103-afae-395a97bd21d0,"[{""sku"": ""SKU-28484"", ""qty"": 5, ""price"": 260.93}, {""sku"": ""SKU-74830"", ""qty"": 4, ""price"": 418.47}, {",paypal,593.52,178.42,2026-01-07T13:51:27.690791,1399.97,TXN-64458914


[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"?>
<student_assessment>
<assessment_id>ASMT-871992</assessment_id>
<student_id>STU-916232</student_id>
<course_id>CRS-5865</course_id>
<type>quiz</type>
<date>2026-01-05</date>
<scores>
<question>1</question>
<points_earned>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>2</question>
<points_earned>6</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>3</question>
<points_earned>10</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>5</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>6</question>
<points_earned>5</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>7</question>
<points_earned>0</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>8</question>
<points_earned>7</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>9</question>
<points_earned>2</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>10</question>
<points_earned>4</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>11</question>
<points_earned>5</points_earned>
<points_possible>10</points_possible>
</scores>
<total_score>83</total_score>
<percentage>70.57</percentage>
<grade>B</grade>
</student_assessment>

[Assistant]
Approach:
1. Task: Convert student assessment 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:
{
  "assessment_id": "ASMT-871992",
  "student_id": "STU-916232",
  "course_id": "CRS-5865",
  "type": "quiz",
  "date": "2026-01-05",
  "scores": [
    {
      "question": 1,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 2,
      "points_earned": 6,
      "points_possible": 10
    },
    {
      "question": 3,
      "points_earned": 10,
      "points_possible": 10
    },
    {
      "question": 4,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 5,
      "points_earned": 5,
      "points_possible": 10
    },
    {
      "question": 6,
      "points_earned": 5,
      "points_possible": 10
    },
    {
      "question": 7,
      "points_earned": 0,
      "points_possible": 10
    },
    {
      "question": 8,
      "points_earned": 7,
      "points_possible": 10
    },
    {
      "question": 9,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 10,
      "points_earned": 4,
      "points_possible": 10
    },
    {
      "question": 11,
      "points_earned": 5,
      "points_possible": 10
    }
  ],
  "total_score": 83,
  "percentage": 70.57,
  "grade": "B"
}


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

[User] Generate clinical note data in JSON format.

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

Output:
{
  "note_id": "CN-6709459",
  "patient": {
    "mrn": "MRN-104418",
    "age": 50,
    "gender": "M"
  },
  "encounter_date": "2026-01-03",
  "chief_complaint": "fever",
  "vitals": {
    "bp": "143/96",
    "hr": 69,
    "temp_f": 101.3
  },
  "assessment": [
    {
      "problem": "diabetes",
      "icd10": "J90"
    },
    {
      "problem": "hypertension",
      "icd10": "I22"
    },
    {
      "problem": "hypertension",
      "icd10": "K97"
    }
  ]
}


[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: 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:
{
  "authors": [
    {
      "name": "Emily Davis",
      "affiliation": "Nelson, Diaz and Humphrey",
      "email": "jpalmer@example.org"
    },
    {
      "name": "Robert Clark",
      "affiliation": "James Inc",
      "email": "dennis02@example.net"
    }
  ],
  "publication": {
    "venue": "Science",
    "year": 2022,
    "doi": "10.6797/tlMT"
  },
  "keywords": [
    "lead",
    "list",
    "she"
  ],
  "funding_source": null,
  "paper_id": "arXiv:2022.72917"
}


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

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

[Assistant]
Approach:
1. Task: Create social media post 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:
post_id: POST-25055870
platform: twitter
user_id: 28837af0-4898-41b2-8a38-faf0e2d7f431
username: khahn
content: 'Serve student science today general. Tell risk ball quickly technology.

  Drive because generation support gun message majority. Though do old.'
timestamp: '2026-01-07T13:51:27.403909'
hashtags:
- '#conference'
- '#body'
engagement:
  likes: 9394
  shares: 444
  comments: 203


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

[User]
Transform this TOML data into YAML format:
paper_id = "arXiv:2020.65510"
title = "Mandatory solution-oriented groupware"
abstract = "Along its pressure yeah. Artist pattern nearly rich realize available skill. Month beyond rate make kid painting."
keywords = [ "surface", "consumer", "despite", "compare", "protect",]
citations = 488
funding_source = "Johnson LLC"
[[authors]]
name = "Jared Fuller"
affiliation = "Robinson, Crawford and Johnson"
email = "jenna58@example.net"

[[authors]]
name = "Nancy Anderson"
affiliation = "Shannon-Johnson"
email = "richdonald@example.net"

[[authors]]
name = "Julia Neal"
affiliation = "Roach, Harper and Cameron"
email = "gillcory@example.com"

[publication]
venue = "Nature"
year = 2022
doi = "10.8909/Qnkv"

[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.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] Create a CSV representation of course syllabus.

[Assistant]
Approach:
1. Task: Create course syllabus 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:
code,course_id,credits,grading_final,grading_homework,grading_midterm,instructor,schedule,term,title
KDS432,CRS-9456,3,40,30,30,Kenneth Rogers,"[{""week"": 1, ""topic"": ""activity""}, {""week"": 2, ""topic"": ""foot""}, {""week"": 3, ""topic"": ""reason""}, {""w",Fall 2020,Multi-channeled local complexity 101
VJV420,CRS-3760,3,40,30,30,Kathleen Erickson,"[{""week"": 1, ""topic"": ""that""}, {""week"": 2, ""topic"": ""home""}, {""week"": 3, ""topic"": ""quality""}, {""week",Fall 2022,Customer-focused mission-critical benchmark 101
WIT384,CRS-1909,3,40,30,30,Holly Jones,"[{""week"": 1, ""topic"": ""field""}, {""week"": 2, ""topic"": ""suffer""}, {""week"": 3, ""topic"": ""church""}, {""we",Spring 2020,User-centric encompassing attitude 101


[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:
{
  "paper_id": "arXiv:2020.57295",
  "title": "Persevering global groupware",
  "authors": [
    {
      "name": "Edwin Moore",
      "affiliation": "Smith-Jones",
      "email": "bowenzachary@example.net"
    },
    {
      "name": "Anna Collins",
      "affiliation": "Thomas, Rogers and Baldwin",
      "email": "thill@example.com"
    },
    {
      "name": "Mrs. Mary Delacruz MD",
      "affiliation": "French, Rodriguez and Johnson",
      "email": "amywest@example.org"
    }
  ],
  "abstract": "Stand season mind indicate either. Buy gas keep skin.",
  "keywords": [
    "stock",
    "member",
    "laugh",
    "language",
    "right"
  ],
  "publication": {
    "venue": "Cell",
    "year": 2022,
    "doi": "10.9461/HDZk"
  },
  "citations": 204,
  "funding_source": null
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<paper_id>arXiv:2020.57295</paper_id>
<title>Persevering global groupware</title>
<authors>
<name>Edwin Moore</name>
<affiliation>Smith-Jones</affiliation>
<email>bowenzachary@example.net</email>
</authors>
<authors>
<name>Anna Collins</name>
<affiliation>Thomas, Rogers and Baldwin</affiliation>
<email>thill@example.com</email>
</authors>
<authors>
<name>Mrs. Mary Delacruz MD</name>
<affiliation>French, Rodriguez and Johnson</affiliation>
<email>amywest@example.org</email>
</authors>
<abstract>Stand season mind indicate either. Buy gas keep skin.</abstract>
<keywords>stock</keywords>
<keywords>member</keywords>
<keywords>laugh</keywords>
<keywords>language</keywords>
<keywords>right</keywords>
<publication>
<venue>Cell</venue>
<year>2022</year>
<doi>10.9461/HDZk</doi>
</publication>
<citations>204</citations>
<funding_source />
</research_paper>


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

[User]
Transform this JSON data into XML format:
{
  "rx_id": "RX-3022361",
  "patient_mrn": "MRN-726192",
  "prescriber": "Jessica Warner",
  "date": "2026-01-02",
  "medications": [
    {
      "name": "Atorvastatin",
      "dosage": "20mg",
      "frequency": "BID",
      "quantity": 90
    },
    {
      "name": "Atorvastatin",
      "dosage": "20mg",
      "frequency": "daily",
      "quantity": 30
    }
  ]
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<prescription>
<rx_id>RX-3022361</rx_id>
<patient_mrn>MRN-726192</patient_mrn>
<prescriber>Jessica Warner</prescriber>
<date>2026-01-02</date>
<medications>
<name>Atorvastatin</name>
<dosage>20mg</dosage>
<frequency>BID</frequency>
<quantity>90</quantity>
</medications>
<medications>
<name>Atorvastatin</name>
<dosage>20mg</dosage>
<frequency>daily</frequency>
<quantity>30</quantity>
</medications>
</prescription>


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

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

[Assistant]
Approach:
1. Task: Create news article 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:
article_id: ART-4067367
headline: Polarized human-resource adapter
author: Kristin Larson
published: '2026-01-07T00:05:34.405255'
section: Business
content: 'Ahead effort author use. Unit together series provide arrive country off.
  Whether let thought down.

  Eight audience power analysis. Age hope leader yeah without. Experience kitchen
  heart city.'
tags:
- program
- final
- computer
- live
views: 74807
shares: 3986


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

[User] Create a JSON representation of news article.

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

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


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

[User] Create a CSV representation of student assessment.

[Assistant]
Approach:
1. Task: Create student assessment 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,percentage,schedule,scores,term,title,total_score
,CRS-4089,,,,,,78.32,,"[{""question"": 1, ""points_earned"": 0, ""points_possible"": 10}, {""question"": 2, ""points_earned"": 4, ""po",,,97
YGF139,CRS-9177,4,40,30,30,Deborah Reid,,"[{""week"": 1, ""topic"": ""head""}, {""week"": 2, ""topic"": ""really""}, {""week"": 3, ""topic"": ""tend""}, {""week""",,Spring 2023,Triple-buffered multi-tasking algorithm 101,
VBD303,CRS-5538,3,40,30,30,Ashley Taylor,,"[{""week"": 1, ""topic"": ""career""}, {""week"": 2, ""topic"": ""represent""}, {""week"": 3, ""topic"": ""future""}, ",,Fall 2021,Operative logistical knowledgebase 101,
AHN155,CRS-6045,3,40,30,30,Daniel Young,,"[{""week"": 1, ""topic"": ""property""}, {""week"": 2, ""topic"": ""vote""}, {""week"": 3, ""topic"": ""near""}, {""wee",,Fall 2021,Balanced client-driven adapter 101,


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

[User] Output api specification as TOML.

[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 = "Visionary eco-centric methodology API"
version = "1.0.0"

[paths."/edge".get]
summary = "Simple really social range."
[[paths."/edge".get.parameters]]
name = "param0"
in = "query"
type = "string"

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

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

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


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

[User]
Transform this CSV data into XML format:
abstract,authors,channels,citations,funding_source,keywords,paper_id,period,publication_doi,publication_venue,publication_year,title,top_products,total_revenue,units_sold
,,"[{""name"": ""wholesale"", ""revenue"": 941227, ""growth"": 26.4}, {""name"": ""retail"", ""revenue"": 937409, ""gr",,,,,June 2024,,,,,"[{""sku"": ""SKU-2900"", ""sales"": 81858}, {""sku"": ""SKU-8266"", ""sales"": 123988}, {""sku"": ""SKU-9969"", ""sal",5319249,96009
Decide loss another political city. Nature election effort sport technology.,"[{""name"": ""Emily Edwards"", ""affiliation"": ""Fox-Hughes"", ""email"": ""christiewolfe@example.org""}, {""nam",,25,Khan Ltd,"[""nearly"", ""threat"", ""professor"", ""explain"", ""involve""]",arXiv:2023.29703,,10.1486/taKX,Science,2024,Progressive clear-thinking implementation,,,
"Admit medical drop his ahead become.
Wind note father. World early else compare member live. Perform","[{""name"": ""Lorraine Chase"", ""affiliation"": ""Willis, Watson and Coffey"", ""email"": ""zavalacharles@exam",,104,None,"[""thing"", ""stay"", ""happy"", ""government"", ""charge""]",arXiv:2021.21853,,10.2254/mSEO,Science,2022,Multi-lateral value-added function,,,

[Assistant]
Approach:
1. Task: Convert sales analytics 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"?>
<sales_analytics>
<period>June 2024</period>
<total_revenue>5319249</total_revenue>
<units_sold>96009</units_sold>
<channels>
<name>wholesale</name>
<revenue>941227</revenue>
<growth>26.4</growth>
</channels>
<channels>
<name>retail</name>
<revenue>937409</revenue>
<growth>30.07</growth>
</channels>
<top_products>
<sku>SKU-2900</sku>
<sales>81858</sales>
</top_products>
<top_products>
<sku>SKU-8266</sku>
<sales>123988</sales>
</top_products>
<top_products>
<sku>SKU-9969</sku>
<sales>32400</sales>
</top_products>
</sales_analytics>


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

[User]
Convert the following YAML to XML:
article_id: ART-5347545
headline: Triple-buffered zero administration algorithm
author: Martha Brown
published: '2026-01-05T16:28:34.342789'
section: Sports
content: 'Have fall sing then fast research break. Bar ready eye medical school might
  recognize. Nice sometimes impact point white.

  Take many this never ever trip. Specific call according. We argue person federal
  central each.'
tags:
- line
- 'true'
- compare
- for
views: 96946
shares: 1479

[Assistant]
Approach:
1. Task: Convert news article from YAML 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-5347545</article_id>
<headline>Triple-buffered zero administration algorithm</headline>
<author>Martha Brown</author>
<published>2026-01-05T16:28:34.342789</published>

Sports

<content>Have fall sing then fast research break. Bar ready eye medical school might recognize. Nice sometimes impact point white.
Take many this never ever trip. Specific call according. We argue person federal central each.</content>
<tags>line</tags>
<tags>true</tags>
<tags>compare</tags>
<tags>for</tags>
<views>96946</views>
<shares>1479</shares>
</news_article>


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

[User] Output financial report as XML.

[Assistant]
Approach:
1. Task: Create financial report 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"?>
<financial_report>
<expenses>54498119</expenses>
<ticker>OKCY</ticker>
<company>Clark-Pearson</company>
</financial_report>


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

[User]
Convert the following JSON to XML:
{
  "term_months": 34,
  "parties": [
    {
      "name": "Garza-Henson",
      "role": "party_a"
    },
    {
      "name": "Griffin-Weaver",
      "role": "party_b"
    }
  ],
  "status": "executed",
  "effective_date": "2026-01-01"
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<contract>
<term_months>34</term_months>
<parties>
<name>Garza-Henson</name>
<role>party_a</role>
</parties>
<parties>
<name>Griffin-Weaver</name>
<role>party_b</role>
</parties>
<status>executed</status>
<effective_date>2026-01-01</effective_date>
</contract>


[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: 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:
note_id: CN-2341842
patient:
  mrn: MRN-739833
  age: 85
  gender: F
encounter_date: '2026-01-01'
chief_complaint: fever
vitals:
  bp: 174/60
  hr: 60
  temp_f: 98.7
assessment:
- problem: diabetes
  icd10: I65
- problem: diabetes
  icd10: J29


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

[User] Generate news article data in TOML format.

[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-3281345"
headline = "Streamlined object-oriented toolset"
author = "James Dunn"
published = "2026-01-03T08:23:33.060508"
section = "Politics"
content = "Win take among professor. Glass reflect black similar future. Risk than tree.\nEconomic sit plan. Available then already skill up reason back. Course his threat growth physical parent truth.\nLaugh article pull goal. Believe those few."
tags = [ "hit", "summer", "official", "rather",]
views = 75669
shares = 293


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

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

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<news_article>
<article_id>ART-5646798</article_id>
<headline>Switchable hybrid groupware</headline>
<author>Joshua Bell</author>
<published>2026-01-05T05:31:42.088007</published>

Business

<content>List road lay not year. Congress gas full particular according. Prevent hear century game friend civil live.
Possible option especially woman. Ahead down suffer doctor six traditional. Prove ready American star impact operation just. Difficult yourself difficult base of four letter.</content>
<tags>author</tags>
<tags>son</tags>
<tags>food</tags>
<views>74484</views>
<shares>596</shares>
</news_article>


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

[User]
Reformat the data below from JSON to XML:
{
  "period": "December 2023",
  "total_revenue": 5338205,
  "units_sold": 90572,
  "channels": [
    {
      "name": "wholesale",
      "revenue": 2316482,
      "growth": -1.07
    },
    {
      "name": "online",
      "revenue": 3744469,
      "growth": -0.81
    }
  ],
  "top_products": [
    {
      "sku": "SKU-4601",
      "sales": 454934
    },
    {
      "sku": "SKU-9892",
      "sales": 55264
    },
    {
      "sku": "SKU-8319",
      "sales": 254442
    }
  ]
}

[Assistant]
Approach:
1. Task: Convert sales analytics 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"?>
<sales_analytics>
<period>December 2023</period>
<total_revenue>5338205</total_revenue>
<units_sold>90572</units_sold>
<channels>
<name>wholesale</name>
<revenue>2316482</revenue>
<growth>-1.07</growth>
</channels>
<channels>
<name>online</name>
<revenue>3744469</revenue>
<growth>-0.81</growth>
</channels>
<top_products>
<sku>SKU-4601</sku>
<sales>454934</sales>
</top_products>
<top_products>
<sku>SKU-9892</sku>
<sales>55264</sales>
</top_products>
<top_products>
<sku>SKU-8319</sku>
<sales>254442</sales>
</top_products>
</sales_analytics>


[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:
{
  "txn_id": "TXN-13058367",
  "customer_id": "852e4544-1bd4-44f1-abf0-2ff01b4a4792",
  "timestamp": "2026-01-07T13:51:26.835091",
  "items": [
    {
      "sku": "SKU-47822",
      "qty": 3,
      "price": 237.72
    },
    {
      "sku": "SKU-38430",
      "qty": 4,
      "price": 285.9
    },
    {
      "sku": "SKU-22327",
      "qty": 1,
      "price": 141.71
    }
  ],
  "subtotal": 408.33,
  "tax": 11.32,
  "total": 1142.29,
  "payment_method": "paypal"
}

[Assistant]
Approach:
1. Task: Convert transaction record 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"?>
<transaction_record>
<txn_id>TXN-13058367</txn_id>
<customer_id>852e4544-1bd4-44f1-abf0-2ff01b4a4792</customer_id>
<timestamp>2026-01-07T13:51:26.835091</timestamp>
<items>
<sku>SKU-47822</sku>
<qty>3</qty>
<price>237.72</price>
</items>
<items>
<sku>SKU-38430</sku>
<qty>4</qty>
<price>285.9</price>
</items>
<items>
<sku>SKU-22327</sku>
<qty>1</qty>
<price>141.71</price>
</items>
<subtotal>408.33</subtotal>
<tax>11.32</tax>
<total>1142.29</total>
<payment_method>paypal</payment_method>
</transaction_record>


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

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<paper_id>arXiv:2020.69453</paper_id>
<title>Assimilated needs-based portal</title>
<authors>
<name>Evan Reed</name>
<affiliation>Orr, Wheeler and Johnson</affiliation>
<email>cheryl05@example.net</email>
</authors>
<authors>
<name>Amanda Mcmahon</name>
<affiliation>Maxwell-Price</affiliation>
<email>mbowen@example.org</email>
</authors>
<authors>
<name>Angel Vasquez</name>
<affiliation>Melendez, Osborne and Harris</affiliation>
<email>timothysutton@example.com</email>
</authors>
<abstract>Economy instead thank kitchen. For pattern he purpose strong goal challenge.</abstract>
<keywords>power</keywords>
<keywords>main</keywords>
<keywords>light</keywords>
<keywords>form</keywords>
<keywords>system</keywords>
<publication>
<venue>Cell</venue>
<year>2024</year>
<doi>10.9550/gbOm</doi>
</publication>
<citations>115</citations>
<funding_source />
</research_paper>


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

[User]
Transform this CSV data into JSON format:
company,eps,expenses,metrics_profit_margin,metrics_roe,net_income,quarter,revenue,ticker
Woods and Sons,8.84,48284794,12.42,23.86,2937548,Q1 2020,42196406,ZCNM
Ward-Owen,5.94,30293382,10.9,13.15,411663,Q3 2023,56599215,WOTZ
Thornton-Cardenas,7.02,18767437,9.14,5.5,14532116,Q3 2023,80447063,LZBZ

[Assistant]
Approach:
1. Task: Convert financial report from CSV 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:
{
  "company": "Woods and Sons",
  "ticker": "ZCNM",
  "quarter": "Q1 2020",
  "revenue": 42196406,
  "expenses": 48284794,
  "net_income": 2937548,
  "eps": 8.84,
  "metrics": {
    "profit_margin": 12.42,
    "roe": 23.86
  }
}


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

[User] Output customer review as YAML.

[Assistant]
Approach:
1. Task: Create customer review 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:
review_id: REV-1521978
product_id: PROD-894495
user_id: 0e93d4dc-0d39-4af2-8ec3-d8d1250011b9
rating: 4
title: Great how data open such.
content: City not either situation all along might. Under could expect build member.
  Fish ready onto white majority.
date: '2026-01-05'
verified_purchase: false
helpful_votes: 57


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

[User] Output api specification as XML.

[Assistant]
Approach:
1. Task: Create api specification 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"?>
<api_specification>
<info>
<title>Object-based multimedia secured line API</title>
<version>1.0.0</version>
</info>
<openapi>3.0.0</openapi>
<paths>
</party>
<get>
<summary>Discussion partner stay wear again.</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<parameters>
<name>param1</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//party>
</paths>
</api_specification>


[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"?>
<error_log>
<error_id>2d978d26-6fd7-4641-b202-43ebc0760711</error_id>
<timestamp>2026-01-07T13:51:26.663970</timestamp>
<level>WARNING</level>
<service>someoneService</service>
<message>Inside live none value unit Republican black.</message>
<stack_trace>at role.py:276</stack_trace>
<stack_trace>at loss.py:371</stack_trace>
<context>
<user_id>26f1b94c-c76e-47ab-9121-a3f8ec11053f</user_id>
<request_id>ce096dca-f53f-40bf-822d-ed29d8ca8dd9</request_id>
</context>
</error_log>

[Assistant]
Approach:
1. Task: Convert error log 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:
{
  "error_id": "2d978d26-6fd7-4641-b202-43ebc0760711",
  "timestamp": "2026-01-07T13:51:26.663970",
  "level": "WARNING",
  "service": "someoneService",
  "message": "Inside live none value unit Republican black.",
  "stack_trace": [
    "at role.py:276",
    "at loss.py:371"
  ],
  "context": {
    "user_id": "26f1b94c-c76e-47ab-9121-a3f8ec11053f",
    "request_id": "ce096dca-f53f-40bf-822d-ed29d8ca8dd9"
  }
}


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

[User] Generate product listing data in YAML format.

[Assistant]
Approach:
1. Task: Create product listing 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:
product_id: PROD-107958
name: Adaptive asynchronous synergy
category: electronics
price: 349.45
currency: USD
stock: 717
is_available: true
rating: 1.62
reviews: 33
specs:
  weight_kg: 15.32
  dimensions: 74x31x68cm


[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-137327"
title = "Effect of class on read"
conclusion = "significant"
[[results]]
metric = "safety"
baseline = 73.26
endpoint = 72.84
p_value = 0.0533

[[results]]
metric = "efficacy"
baseline = 49.24
endpoint = 28.3
p_value = 0.0809

[methodology]
design = "RCT"
sample_size = 679
duration_days = 111


[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: 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:
note_id = "CN-3766387"
encounter_date = "2026-01-04"
chief_complaint = "headache"
[[assessment]]
problem = "diabetes"
icd10 = "J94"

[patient]
mrn = "MRN-378219"
age = 48
gender = "F"

[vitals]
bp = "145/101"
hr = 106
temp_f = 101.7


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

[User] Produce a XML document for a research paper.

[Assistant]
Approach:
1. Task: Create research paper 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"?>
<research_paper>
<paper_id>arXiv:2023.21424</paper_id>
<title>Cross-platform fault-tolerant circuit</title>
<authors>
<name>Charlotte Sellers</name>
<affiliation>Armstrong-Marks</affiliation>
<email>weaverelizabeth@example.com</email>
</authors>
<authors>
<name>Cynthia Johnston MD</name>
<affiliation>Rogers Inc</affiliation>
<email>ccastaneda@example.org</email>
</authors>
<authors>
<name>Robert Velasquez</name>
<affiliation>Alvarado LLC</affiliation>
<email>psullivan@example.net</email>
</authors>
<abstract>Truth himself long country car environment. Free design relate hope admit learn identify.</abstract>
<keywords>share</keywords>
<keywords>feeling</keywords>
<keywords>environmental</keywords>
<publication>
<venue>Science</venue>
<year>2022</year>
<doi>10.6091/Sfwn</doi>
</publication>
<citations>477</citations>
<funding_source>Barker-Wise</funding_source>
</research_paper>


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

[User] Produce a YAML document for a student assessment.

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

Output:
assessment_id: ASMT-766800
student_id: STU-927295
course_id: CRS-8819
type: assignment
date: '2026-01-03'
scores:
- question: 1
  points_earned: 8
  points_possible: 10
- question: 2
  points_earned: 3
  points_possible: 10
- question: 3
  points_earned: 8
  points_possible: 10
- question: 4
  points_earned: 1
  points_possible: 10
- question: 5
  points_earned: 5
  points_possible: 10
- question: 6
  points_earned: 2
  points_possible: 10
- question: 7
  points_earned: 0
  points_possible: 10
- question: 8
  points_earned: 4
  points_possible: 10
- question: 9
  points_earned: 3
  points_possible: 10
total_score: 99
percentage: 71.71
grade: A


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

[User] Produce a TOML document for a research paper.

[Assistant]
Approach:
1. Task: Create research paper 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:
paper_id = "arXiv:2023.67735"
title = "Optimized even-keeled conglomeration"
abstract = "Sort suffer stand purpose six resource. Forward hard officer film the word human first."
keywords = [ "attack", "not", "describe",]
citations = 172
funding_source = "Wood, Baldwin and Cain"
[[authors]]
name = "Garrett Contreras"
affiliation = "Drake-Dunn"
email = "sandrapineda@example.net"

[[authors]]
name = "Ryan Bell"
affiliation = "Ramos, Gates and Reed"
email = "kdavis@example.net"

[[authors]]
name = "Cindy Silva"
affiliation = "Bryant, Pratt and Henderson"
email = "fmiller@example.net"

[publication]
venue = "Nature"
year = 2024
doi = "10.7544/lKSL"


[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"?>
<financial_report>
<eps>6.0</eps>
<company>Richardson-Gonzalez</company>
<quarter>Q3 2020</quarter>
<net_income>13953656</net_income>
</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:
{
  "eps": 6.0,
  "company": "Richardson-Gonzalez",
  "quarter": "Q3 2020",
  "net_income": 13953656
}


[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-554535</assessment_id>
<student_id>STU-693793</student_id>
<course_id>CRS-9992</course_id>
<type>exam</type>
<date>2026-01-03</date>
<scores>
<question>1</question>
<points_earned>9</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>2</question>
<points_earned>6</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>3</question>
<points_earned>7</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>4</question>
<points_earned>6</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>5</question>
<points_earned>6</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>6</question>
<points_earned>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>7</question>
<points_earned>4</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>8</question>
<points_earned>8</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>9</question>
<points_earned>2</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>10</question>
<points_earned>3</points_earned>
<points_possible>10</points_possible>
</scores>
<total_score>86</total_score>
<percentage>63.99</percentage>
<grade>B</grade>
</student_assessment>


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

[User] Create a JSON representation of lab result.

[Assistant]
Approach:
1. Task: Create lab result 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:
{
  "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"
    }
  ]
}


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

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

[Assistant]
Approach:
1. Task: Create lab result 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:
order_date: '2026-01-01'
panel: Lipid
patient_mrn: MRN-952425
result_id: LAB-8958063
results:
- test: Glucose
  value: 142.4
  unit: g/dL
  flag: normal
- test: Hemoglobin
  value: 196.3
  unit: g/dL
  flag: normal
- test: Hemoglobin
  value: 74.4
  unit: mg/dL
  flag: normal
- test: Hemoglobin
  value: 119.9
  unit: mg/dL
  flag: high
- test: WBC
  value: 99.2
  unit: mg/dL
  flag: normal
- test: Glucose
  value: 51.3
  unit: g/dL
  flag: normal
- test: Glucose
  value: 186.5
  unit: mg/dL
  flag: low


[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-852387"
name = "Profound logistical array"
category = "electronics"
price = 299.46
currency = "USD"
stock = 505
is_available = true
rating = 2.95
reviews = 519

[specs]
weight_kg = 6.22
dimensions = "16x47x36cm"


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

[User] Generate customer review data in TOML format.

[Assistant]
Approach:
1. Task: Create customer review in TOML
2. Complexity: 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-1274071"
product_id = "PROD-300785"
user_id = "c183a72e-4d6f-40ac-92b0-2d1073039571"
rating = 5
title = "Follow large high gas clear drug pretty else."
content = "Recent cause family writer. Old less control he woman. Coach quickly will.\nRelationship same against one stand agreement. Be fine occur ten energy resource wall. Nation ten continue."
date = "2026-01-06"
verified_purchase = true
helpful_votes = 37


[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"?>
<contract>
<contract_id>CTR-926700</contract_id>
<parties>
<name>Kelly-Jackson</name>
<role>party_a</role>
</parties>
<parties>
<name>Ramos, Hampton and Hartman</name>
<role>party_b</role>
</parties>
<effective_date>2026-01-04</effective_date>
<term_months>36</term_months>
<value>178791</value>
<status>pending</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-926700",
  "parties": [
    {
      "name": "Kelly-Jackson",
      "role": "party_a"
    },
    {
      "name": "Ramos, Hampton and Hartman",
      "role": "party_b"
    }
  ],
  "effective_date": "2026-01-04",
  "term_months": 36,
  "value": 178791,
  "status": "pending"
}


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

[User] Create a YAML representation of api specification.

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

Output:
openapi: 3.0.0
info:
  title: Organic analyzing strategy API
  version: 1.0.0
paths:
  /similar:
    get:
      summary: Natural see lot recently.
      parameters:
      - name: param0
        in: query
        type: string
      - name: param1
        in: query
        type: string
      responses:
        '200':
          description: Success
        '400':
          description: Bad Request


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

[User] Produce a TOML document for a financial report.

[Assistant]
Approach:
1. Task: Create financial report 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:
net_income = 16280737
revenue = 93235840
expenses = 6835352

[metrics]
profit_margin = 9.67
roe = 5.79


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

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

[Assistant]
Approach:
1. Task: Create lab result 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:
order_date,panel,patient_mrn,result_id,results
2026-01-02,Lipid,MRN-230243,LAB-4303735,"[{""test"": ""WBC"", ""value"": 142.8, ""unit"": ""g/dL"", ""flag"": ""high""}, {""test"": ""Hemoglobin"", ""value"": 10"
2026-01-01,Lipid,MRN-246342,LAB-5141721,"[{""test"": ""WBC"", ""value"": 115.0, ""unit"": ""g/dL"", ""flag"": ""high""}, {""test"": ""Hemoglobin"", ""value"": 17"
2026-01-02,CBC,MRN-762667,LAB-8260317,"[{""test"": ""Hemoglobin"", ""value"": 139.3, ""unit"": ""mg/dL"", ""flag"": ""high""}, {""test"": ""Hemoglobin"", ""va"
2026-01-01,CBC,MRN-864582,LAB-3732150,"[{""test"": ""Glucose"", ""value"": 161.0, ""unit"": ""g/dL"", ""flag"": ""low""}, {""test"": ""WBC"", ""value"": 189.3,"
2026-01-01,Lipid,MRN-711884,LAB-1928819,"[{""test"": ""WBC"", ""value"": 66.6, ""unit"": ""mg/dL"", ""flag"": ""normal""}, {""test"": ""Hemoglobin"", ""value"": "


[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"?>
<customer_review>
<review_id>REV-1384784</review_id>
<product_id>PROD-499626</product_id>
<user_id>4c396b1f-b1b7-4ef7-9587-0fda03a6f7f9</user_id>
<rating>1</rating>
<title>Respond out five.</title>
<content>I stay little Democrat money where stop. Than development activity.
Along ahead their standard early nor reason. Fight with minute learn soldier understand.</content>
<date>2026-01-05</date>
<verified_purchase>False</verified_purchase>
<helpful_votes>94</helpful_votes>
</customer_review>

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

Output:
{
  "review_id": "REV-1384784",
  "product_id": "PROD-499626",
  "user_id": "4c396b1f-b1b7-4ef7-9587-0fda03a6f7f9",
  "rating": 1,
  "title": "Respond out five.",
  "content": "I stay little Democrat money where stop. Than development activity.\nAlong ahead their standard early nor reason. Fight with minute learn soldier understand.",
  "date": "2026-01-05",
  "verified_purchase": false,
  "helpful_votes": 94
}