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

[User] Generate course syllabus data in XML format.

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<course_syllabus>
<title>Stand-alone empowering functionalities 101</title>
<schedule>
<week>1</week>
<topic>class</topic>
</schedule>
<schedule>
<week>2</week>
<topic>leave</topic>
</schedule>
<schedule>
<week>3</week>
<topic>develop</topic>
</schedule>
<schedule>
<week>4</week>
<topic>style</topic>
</schedule>
<schedule>
<week>5</week>
<topic>again</topic>
</schedule>
<schedule>
<week>6</week>
<topic>man</topic>
</schedule>
<schedule>
<week>7</week>
<topic>list</topic>
</schedule>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
</course_syllabus>


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

[User]
Convert the following JSON to XML:
{
  "error_id": "234c0781-6e40-4e46-8b0d-ad1b39309eb0",
  "timestamp": "2026-01-07T13:51:25.659911",
  "level": "WARNING",
  "service": "beyondService",
  "message": "Section material entire top community.",
  "stack_trace": [
    "at reason.py:320",
    "at always.py:365",
    "at red.py:27"
  ],
  "context": {
    "user_id": "6765bd92-f82e-426f-a383-fa0a088a0752",
    "request_id": "4ccfb0b5-8185-4d26-902a-0379b3534400"
  }
}

[Assistant]
Approach:
1. Task: Convert error log 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"?>
<error_log>
<error_id>234c0781-6e40-4e46-8b0d-ad1b39309eb0</error_id>
<timestamp>2026-01-07T13:51:25.659911</timestamp>
<level>WARNING</level>
<service>beyondService</service>
<message>Section material entire top community.</message>
<stack_trace>at reason.py:320</stack_trace>
<stack_trace>at always.py:365</stack_trace>
<stack_trace>at red.py:27</stack_trace>
<context>
<user_id>6765bd92-f82e-426f-a383-fa0a088a0752</user_id>
<request_id>4ccfb0b5-8185-4d26-902a-0379b3534400</request_id>
</context>
</error_log>


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

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

[Assistant]
Approach:
1. Task: Create news article in TOML
2. Complexity: 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:
article_id = "ART-8221745"
headline = "Polarized zero administration support"
author = "Maria Johnson"
published = "2026-01-03T08:37:58.870132"
section = "Business"
content = "Would movement white military what them cup. Available remember control staff. None mean hundred PM.\nImprove wear produce price according. He method market computer TV strategy.\nBody into language. Which other hear they look some option."
tags = [ "environment", "name", "receive", "happen", "join",]
views = 46852
shares = 763


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

[User] Create a XML representation of prescription.

[Assistant]
Approach:
1. Task: Create prescription 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"?>
<prescription>
<rx_id>RX-8246470</rx_id>
<patient_mrn>MRN-256913</patient_mrn>
<prescriber>Victor Valentine</prescriber>
<date>2026-01-01</date>
<medications>
<name>Lisinopril</name>
<dosage>20mg</dosage>
<frequency>daily</frequency>
<quantity>30</quantity>
</medications>
<medications>
<name>Lisinopril</name>
<dosage>10mg</dosage>
<frequency>BID</frequency>
<quantity>60</quantity>
</medications>
<medications>
<name>Lisinopril</name>
<dosage>5mg</dosage>
<frequency>TID</frequency>
<quantity>30</quantity>
</medications>
</prescription>


[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>
<items>
<sku>SKU-71565</sku>
<qty>1</qty>
<price>387.38</price>
</items>
<items>
<sku>SKU-23891</sku>
<qty>1</qty>
<price>432.74</price>
</items>
<items>
<sku>SKU-77840</sku>
<qty>1</qty>
<price>463.12</price>
</items>
<items>
<sku>SKU-27496</sku>
<qty>3</qty>
<price>295.3</price>
</items>
<tax>39.55</tax>
<total>1865.58</total>
<customer_id>bf96f80b-072c-4f04-82b0-c235c01681a8</customer_id>
</transaction_record>

[Assistant]
Approach:
1. Task: Convert transaction record 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:
{
  "items": [
    {
      "sku": "SKU-71565",
      "qty": 1,
      "price": 387.38
    },
    {
      "sku": "SKU-23891",
      "qty": 1,
      "price": 432.74
    },
    {
      "sku": "SKU-77840",
      "qty": 1,
      "price": 463.12
    },
    {
      "sku": "SKU-27496",
      "qty": 3,
      "price": 295.3
    }
  ],
  "tax": 39.55,
  "total": 1865.58,
  "customer_id": "bf96f80b-072c-4f04-82b0-c235c01681a8"
}


[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>ff91c212-6cce-4ac2-978d-0740381882de</error_id>
<timestamp>2026-01-07T13:51:27.679071</timestamp>
<level>WARNING</level>
<service>drawService</service>
<message>Support red list product forget cut speak.</message>
<stack_trace>at girl.py:186</stack_trace>
<stack_trace>at hold.py:186</stack_trace>
<context>
<user_id>473e683b-291e-461f-b848-d224b7dcbd8b</user_id>
<request_id>454a35ad-23ee-42a8-9d57-dbf5cedbef74</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": "ff91c212-6cce-4ac2-978d-0740381882de",
  "timestamp": "2026-01-07T13:51:27.679071",
  "level": "WARNING",
  "service": "drawService",
  "message": "Support red list product forget cut speak.",
  "stack_trace": [
    "at girl.py:186",
    "at hold.py:186"
  ],
  "context": {
    "user_id": "473e683b-291e-461f-b848-d224b7dcbd8b",
    "request_id": "454a35ad-23ee-42a8-9d57-dbf5cedbef74"
  }
}


[System] You are an expert in 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: 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"?>
<social_media_post>
<post_id>POST-78526123</post_id>
<platform>twitter</platform>
<user_id>17596017-ad50-41af-8dc2-8746d15af00d</user_id>
<username>qsharp</username>
<content>Seven behavior less water pretty.
Rock key include. Kind than game agreement.
Paper position reduce purpose I affect wait threat. Third effect newspaper before include decision recently million.</content>
<timestamp>2026-01-07T13:51:27.460227</timestamp>
<hashtags>#draw</hashtags>
<hashtags>#five</hashtags>
<hashtags>#culture</hashtags>
<hashtags>#sport</hashtags>
<engagement>
<likes>1826</likes>
<shares>489</shares>
<comments>393</comments>
</engagement>
</social_media_post>


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

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


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

[User]
Transform this JSON data into CSV format:
{
  "note_id": "CN-7937835",
  "patient": {
    "mrn": "MRN-749785",
    "age": 66,
    "gender": "M"
  },
  "encounter_date": "2026-01-06",
  "chief_complaint": "chest pain",
  "vitals": {
    "bp": "179/85",
    "hr": 81,
    "temp_f": 101.7
  },
  "assessment": [
    {
      "problem": "hypertension",
      "icd10": "I52"
    },
    {
      "problem": "diabetes",
      "icd10": "J76"
    }
  ]
}

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

Output:
assessment,chief_complaint,encounter_date,note_id,patient_age,patient_gender,patient_mrn,vitals_bp,vitals_hr,vitals_temp_f
"[{""problem"": ""hypertension"", ""icd10"": ""I52""}, {""problem"": ""diabetes"", ""icd10"": ""J76""}]",chest pain,2026-01-06,CN-7937835,66,M,MRN-749785,179/85,81,101.7
"[{""problem"": ""hypertension"", ""icd10"": ""J61""}, {""problem"": ""diabetes"", ""icd10"": ""J60""}]",fever,2026-01-04,CN-9641504,66,F,MRN-273795,178/104,76,98.0
"[{""problem"": ""diabetes"", ""icd10"": ""I23""}, {""problem"": ""diabetes"", ""icd10"": ""K35""}]",headache,2026-01-06,CN-4036088,44,M,MRN-564198,139/69,64,98.4
"[{""problem"": ""diabetes"", ""icd10"": ""K26""}, {""problem"": ""diabetes"", ""icd10"": ""K31""}, {""problem"": ""diab",fever,2026-01-04,CN-2650447,19,F,MRN-971752,176/82,96,101.6


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

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<course_syllabus>
<course_id>CRS-8328</course_id>
QKE428
<title>Decentralized content-based leverage 101</title>
<instructor>Sarah Simon</instructor>
<credits>3</credits>
<term>Fall 2022</term>
<schedule>
<week>1</week>
<topic>whole</topic>
</schedule>
<schedule>
<week>2</week>
<topic>table</topic>
</schedule>
<schedule>
<week>3</week>
<topic>determine</topic>
</schedule>
<schedule>
<week>4</week>
<topic>evening</topic>
</schedule>
<schedule>
<week>5</week>
<topic>once</topic>
</schedule>
<schedule>
<week>6</week>
<topic>some</topic>
</schedule>
<schedule>
<week>7</week>
<topic>themselves</topic>
</schedule>
<schedule>
<week>8</week>
<topic>table</topic>
</schedule>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
</course_syllabus>

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

Output:
{
  "course_id": "CRS-8328",
  "code": "QKE428",
  "title": "Decentralized content-based leverage 101",
  "instructor": "Sarah Simon",
  "credits": 3,
  "term": "Fall 2022",
  "schedule": [
    {
      "week": 1,
      "topic": "whole"
    },
    {
      "week": 2,
      "topic": "table"
    },
    {
      "week": 3,
      "topic": "determine"
    },
    {
      "week": 4,
      "topic": "evening"
    },
    {
      "week": 5,
      "topic": "once"
    },
    {
      "week": 6,
      "topic": "some"
    },
    {
      "week": 7,
      "topic": "themselves"
    },
    {
      "week": 8,
      "topic": "table"
    }
  ],
  "grading": {
    "homework": 30,
    "midterm": 30,
    "final": 40
  }
}


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

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<clinical_note>
<note_id>CN-3766387</note_id>
<patient>
<mrn>MRN-378219</mrn>
<age>48</age>
<gender>F</gender>
</patient>
<encounter_date>2026-01-04</encounter_date>
<chief_complaint>headache</chief_complaint>
<vitals>
<bp>145/101</bp>

106

<temp_f>101.7</temp_f>
</vitals>
<assessment>
<problem>diabetes</problem>
<icd10>J94</icd10>
</assessment>
</clinical_note>

[Assistant]
Approach:
1. Task: Convert clinical note 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:
{
  "note_id": "CN-3766387",
  "patient": {
    "mrn": "MRN-378219",
    "age": 48,
    "gender": "F"
  },
  "encounter_date": "2026-01-04",
  "chief_complaint": "headache",
  "vitals": {
    "bp": "145/101",
    "hr": 106,
    "temp_f": 101.7
  },
  "assessment": [
    {
      "problem": "diabetes",
      "icd10": "J94"
    }
  ]
}


[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"?>
<product_listing>
<product_id>PROD-239354</product_id>
<name>User-centric tertiary contingency</name>
<category>electronics</category>
<price>998.51</price>
<currency>USD</currency>
<stock>842</stock>
<is_available>True</is_available>
<rating>2.36</rating>
<reviews>630</reviews>
<specs>
<weight_kg>0.61</weight_kg>
<dimensions>88x23x10cm</dimensions>
</specs>
</product_listing>

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


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

[User] Generate news article data in JSON format.

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


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

[User] Generate customer review data in YAML format.

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

Output:
rating: 5
review_id: REV-2205395
content: 'Respond order far story by area affect. Important also catch down choice
  office necessary political. Firm along bar.

  Stuff create including star question traditional reflect. Share fast thought.'


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

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

[Assistant]
Approach:
1. Task: Create news article in CSV
2. Complexity: 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:
article_id,author,content,headline,published,section,shares,tags,views
ART-6846954,Steven Burgess,Police report arm sense find civil during. New avoid old future quality finally bad. Meeting child e,Triple-buffered intangible knowledgebase,2026-01-02T13:52:55.283034,Politics,3662,"[""couple"", ""specific"", ""him""]",35509
ART-2474084,Cristina Conway,"Suggest seek of hair. Yeah available half action become information. Heavy say culture structure.
Pr",Advanced encompassing flexibility,2026-01-05T12:03:28.066252,Politics,4675,"[""read"", ""quite"", ""need"", ""style"", ""seem""]",2248
ART-6731221,Christina Benton,Dream lead even church will. Camera special culture car more. Anything according explain clearly gro,Up-sized zero administration challenge,2026-01-04T15:28:44.080877,Tech,2594,"[""impact"", ""marriage"", ""senior"", ""red""]",87331
ART-3827619,Sonya Jimenez,"Past field reveal. Set say agent wrong race thought. Court he model research then.
Beautiful stop de",Up-sized content-based leverage,2026-01-04T09:31:06.349983,Sports,1637,"[""important"", ""situation"", ""charge"", ""have""]",9281
ART-1882464,Joseph Wilson,Like once car direction. Market her enjoy history wall spring cost. Off professor hold admit quickly,Proactive foreground service-desk,2026-01-07T06:21:10.929827,Tech,3435,"[""heavy"", ""family"", ""president"", ""represent""]",34178


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

[User] Create a YAML representation of research paper.

[Assistant]
Approach:
1. Task: Create research paper 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:
paper_id: arXiv:2022.73738
title: Switchable maximized Local Area Network
authors:
- name: Heather Lee
  affiliation: Garcia, Ellison and Kim
  email: kimberlysimpson@example.com
- name: Jeremy Gonzalez
  affiliation: Wilson, Sanchez and Copeland
  email: michelle83@example.com
- name: Brianna Hart
  affiliation: Shannon, Tran and Taylor
  email: penatyler@example.net
abstract: List son shake understand food. Up no police friend factor. Support company
  yes push argue.
keywords:
- fact
- guess
- truth
publication:
  venue: Cell
  year: 2024
  doi: 10.7028/ttmb
citations: 36
funding_source: Guerra, Richards and Schaefer


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

[User]
Convert the following JSON to XML:
{
  "assessment_id": "ASMT-549878",
  "student_id": "STU-264168",
  "course_id": "CRS-6692",
  "type": "assignment",
  "date": "2026-01-01",
  "scores": [
    {
      "question": 1,
      "points_earned": 7,
      "points_possible": 10
    },
    {
      "question": 2,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 3,
      "points_earned": 9,
      "points_possible": 10
    },
    {
      "question": 4,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 5,
      "points_earned": 4,
      "points_possible": 10
    },
    {
      "question": 6,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 7,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 8,
      "points_earned": 1,
      "points_possible": 10
    }
  ],
  "total_score": 70,
  "percentage": 54.38,
  "grade": "C"
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<student_assessment>
<assessment_id>ASMT-549878</assessment_id>
<student_id>STU-264168</student_id>
<course_id>CRS-6692</course_id>
<type>assignment</type>
<date>2026-01-01</date>
<scores>
<question>1</question>
<points_earned>7</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>2</question>
<points_earned>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>3</question>
<points_earned>9</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>4</question>
<points_earned>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>5</question>
<points_earned>4</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>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>8</question>
<points_earned>1</points_earned>
<points_possible>10</points_possible>
</scores>
<total_score>70</total_score>
<percentage>54.38</percentage>
<grade>C</grade>
</student_assessment>


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

[User]
Transform this XML data into JSON format:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<paper_id>arXiv:2023.54834</paper_id>
<title>Profit-focused radical throughput</title>
<authors>
<name>Scott Dunlap</name>
<affiliation>Daniels PLC</affiliation>
<email>williamssheri@example.com</email>
</authors>
<authors>
<name>Shawn Payne</name>
<affiliation>Dorsey, Price and Burns</affiliation>
<email>smoyer@example.net</email>
</authors>
<authors>
<name>Chase Lee</name>
<affiliation>Garcia Inc</affiliation>
<email>burgesssarah@example.org</email>
</authors>
<abstract>Read deal buy final thus. Sure home game rest lose.
Those any reality if teach.
Main never still little study clearly today.</abstract>
<keywords>measure</keywords>
<keywords>stage</keywords>
<keywords>scene</keywords>
<keywords>reason</keywords>
<publication>
<venue>Science</venue>
<year>2020</year>
<doi>10.8776/UhOT</doi>
</publication>
<citations>388</citations>
<funding_source>Reese-Perez</funding_source>
</research_paper>

[Assistant]
Approach:
1. Task: Convert research paper 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:
{
  "paper_id": "arXiv:2023.54834",
  "title": "Profit-focused radical throughput",
  "authors": [
    {
      "name": "Scott Dunlap",
      "affiliation": "Daniels PLC",
      "email": "williamssheri@example.com"
    },
    {
      "name": "Shawn Payne",
      "affiliation": "Dorsey, Price and Burns",
      "email": "smoyer@example.net"
    },
    {
      "name": "Chase Lee",
      "affiliation": "Garcia Inc",
      "email": "burgesssarah@example.org"
    }
  ],
  "abstract": "Read deal buy final thus. Sure home game rest lose.\nThose any reality if teach.\nMain never still little study clearly today.",
  "keywords": [
    "measure",
    "stage",
    "scene",
    "reason"
  ],
  "publication": {
    "venue": "Science",
    "year": 2020,
    "doi": "10.8776/UhOT"
  },
  "citations": 388,
  "funding_source": "Reese-Perez"
}


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

[User]
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<prescription>
<rx_id>RX-6885629</rx_id>
<prescriber>John Cook</prescriber>
<medications>
<name>Metformin</name>
<dosage>5mg</dosage>
<frequency>daily</frequency>
<quantity>30</quantity>
</medications>
<medications>
<name>Atorvastatin</name>
<dosage>5mg</dosage>
<frequency>BID</frequency>
<quantity>90</quantity>
</medications>
<medications>
<name>Lisinopril</name>
<dosage>5mg</dosage>
<frequency>TID</frequency>
<quantity>60</quantity>
</medications>
<date>2026-01-02</date>
<patient_mrn>MRN-741538</patient_mrn>
</prescription>

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

Output:
{
  "rx_id": "RX-6885629",
  "prescriber": "John Cook",
  "medications": [
    {
      "name": "Metformin",
      "dosage": "5mg",
      "frequency": "daily",
      "quantity": 30
    },
    {
      "name": "Atorvastatin",
      "dosage": "5mg",
      "frequency": "BID",
      "quantity": 90
    },
    {
      "name": "Lisinopril",
      "dosage": "5mg",
      "frequency": "TID",
      "quantity": 60
    }
  ],
  "date": "2026-01-02",
  "patient_mrn": "MRN-741538"
}


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

[User]
Reformat the data below from JSON to XML:
{
  "result_id": "LAB-4911961",
  "patient_mrn": "MRN-250544",
  "order_date": "2026-01-03",
  "panel": "CBC",
  "results": [
    {
      "test": "Hemoglobin",
      "value": 121.1,
      "unit": "g/dL",
      "flag": "normal"
    },
    {
      "test": "Hemoglobin",
      "value": 77.4,
      "unit": "mg/dL",
      "flag": "high"
    },
    {
      "test": "Glucose",
      "value": 107.3,
      "unit": "g/dL",
      "flag": "high"
    },
    {
      "test": "Glucose",
      "value": 172.8,
      "unit": "g/dL",
      "flag": "normal"
    },
    {
      "test": "Hemoglobin",
      "value": 166.2,
      "unit": "mg/dL",
      "flag": "normal"
    },
    {
      "test": "Hemoglobin",
      "value": 140.6,
      "unit": "g/dL",
      "flag": "normal"
    },
    {
      "test": "WBC",
      "value": 120.4,
      "unit": "mg/dL",
      "flag": "normal"
    }
  ]
}

[Assistant]
Approach:
1. Task: Convert lab result 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"?>
<lab_result>
<result_id>LAB-4911961</result_id>
<patient_mrn>MRN-250544</patient_mrn>
<order_date>2026-01-03</order_date>
<panel>CBC</panel>
<results>
<test>Hemoglobin</test>
<value>121.1</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>77.4</value>
<unit>mg/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Glucose</test>
<value>107.3</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Glucose</test>
<value>172.8</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>166.2</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>140.6</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>WBC</test>
<value>120.4</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
</lab_result>


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

[User]
Convert the following JSON to XML:
{
  "review_id": "REV-5650887",
  "product_id": "PROD-601157",
  "user_id": "ac7725ae-2567-44d1-8d40-a64432b9801b",
  "rating": 3,
  "title": "Personal order single check off but my.",
  "content": "Key Mrs say because walk old certainly. Product figure event choice.\nSkill cut plan per side same. Between common join partner kid enter page discover.",
  "date": "2026-01-06",
  "verified_purchase": true,
  "helpful_votes": 66
}

[Assistant]
Approach:
1. Task: Convert customer review 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"?>
<customer_review>
<review_id>REV-5650887</review_id>
<product_id>PROD-601157</product_id>
<user_id>ac7725ae-2567-44d1-8d40-a64432b9801b</user_id>
<rating>3</rating>
<title>Personal order single check off but my.</title>
<content>Key Mrs say because walk old certainly. Product figure event choice.
Skill cut plan per side same. Between common join partner kid enter page discover.</content>
<date>2026-01-06</date>
<verified_purchase>True</verified_purchase>
<helpful_votes>66</helpful_votes>
</customer_review>


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

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

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

Output:
{
  "company": "Brooks LLC",
  "ticker": "HFOB",
  "quarter": "Q1 2020",
  "revenue": 30917299,
  "expenses": 61265128,
  "net_income": 10426094,
  "eps": 3.56,
  "metrics": {
    "profit_margin": 26.89,
    "roe": 20.49
  }
}


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

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

[Assistant]
Approach:
1. Task: Create customer review in JSON
2. Complexity: 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:
{
  "helpful_votes": 39,
  "date": "2026-01-04",
  "rating": 5,
  "review_id": "REV-1864702",
  "title": "State standard bad message use."
}


[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"?>
<experiment_result>
<experiment_id>EXP-818679</experiment_id>
<title>Effect of begin on task</title>
<methodology>
<design>RCT</design>
<sample_size>180</sample_size>
<duration_days>157</duration_days>
</methodology>
<results>
<metric>safety</metric>
<baseline>17.77</baseline>
<endpoint>32.37</endpoint>
<p_value>0.477</p_value>
</results>
<results>
<metric>safety</metric>
<baseline>20.98</baseline>
<endpoint>13.84</endpoint>
<p_value>0.2984</p_value>
</results>
<conclusion>non-significant</conclusion>
</experiment_result>

[Assistant]
Approach:
1. Task: Convert experiment result 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:
{
  "experiment_id": "EXP-818679",
  "title": "Effect of begin on task",
  "methodology": {
    "design": "RCT",
    "sample_size": 180,
    "duration_days": 157
  },
  "results": [
    {
      "metric": "safety",
      "baseline": 17.77,
      "endpoint": 32.37,
      "p_value": 0.477
    },
    {
      "metric": "safety",
      "baseline": 20.98,
      "endpoint": 13.84,
      "p_value": 0.2984
    }
  ],
  "conclusion": "non-significant"
}


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

[User]
Convert the following TOML to JSON:
period = "February 2020"
total_revenue = 2007174
units_sold = 24558
[[channels]]
name = "online"
revenue = 235807
growth = 46.03

[[channels]]
name = "wholesale"
revenue = 4419318
growth = 24.35

[[top_products]]
sku = "SKU-6554"
sales = 258652

[[top_products]]
sku = "SKU-8652"
sales = 200091

[[top_products]]
sku = "SKU-9581"
sales = 65110

[Assistant]
Approach:
1. Task: Convert sales analytics from TOML 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:
{
  "period": "February 2020",
  "total_revenue": 2007174,
  "units_sold": 24558,
  "channels": [
    {
      "name": "online",
      "revenue": 235807,
      "growth": 46.03
    },
    {
      "name": "wholesale",
      "revenue": 4419318,
      "growth": 24.35
    }
  ],
  "top_products": [
    {
      "sku": "SKU-6554",
      "sales": 258652
    },
    {
      "sku": "SKU-8652",
      "sales": 200091
    },
    {
      "sku": "SKU-9581",
      "sales": 65110
    }
  ]
}


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

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

[Assistant]
Approach:
1. Task: Create student assessment 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:
assessment_id = "ASMT-422317"
student_id = "STU-280699"
course_id = "CRS-7308"
type = "exam"
date = "2026-01-01"
total_score = 75
percentage = 83.59
grade = "B"
[[scores]]
question = 1
points_earned = 2
points_possible = 10

[[scores]]
question = 2
points_earned = 3
points_possible = 10

[[scores]]
question = 3
points_earned = 10
points_possible = 10

[[scores]]
question = 4
points_earned = 1
points_possible = 10

[[scores]]
question = 5
points_earned = 10
points_possible = 10

[[scores]]
question = 6
points_earned = 3
points_possible = 10

[[scores]]
question = 7
points_earned = 7
points_possible = 10


[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
ZMD258,CRS-5570,3,40,30,30,Gregory Dunn,"[{""week"": 1, ""topic"": ""guess""}, {""week"": 2, ""topic"": ""forget""}, {""week"": 3, ""topic"": ""technology""}, ",Spring 2021,Mandatory leadingedge superstructure 101
TJT277,CRS-6463,4,40,30,30,Alison Ramsey,"[{""week"": 1, ""topic"": ""commercial""}, {""week"": 2, ""topic"": ""reason""}, {""week"": 3, ""topic"": ""police""},",Fall 2023,Universal needs-based knowledgebase 101
AYQ141,CRS-6236,3,40,30,30,Jesse Greene,"[{""week"": 1, ""topic"": ""modern""}, {""week"": 2, ""topic"": ""small""}, {""week"": 3, ""topic"": ""point""}, {""wee",Fall 2024,Advanced full-range contingency 101


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

[User]
Convert the following YAML to JSON:
review_id: REV-5008217
product_id: PROD-173271
user_id: 11121b86-b60c-4ea2-b83a-cbb727cd7a24
rating: 2
title: Lay lead it politics brother.
content: Camera left hope prevent inside real. Whether trouble their always manager
  cultural majority popular. Song condition entire security concern science. Run number
  firm listen serious.
date: '2026-01-01'
verified_purchase: true
helpful_votes: 23

[Assistant]
Approach:
1. Task: Convert customer review from YAML 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-5008217",
  "product_id": "PROD-173271",
  "user_id": "11121b86-b60c-4ea2-b83a-cbb727cd7a24",
  "rating": 2,
  "title": "Lay lead it politics brother.",
  "content": "Camera left hope prevent inside real. Whether trouble their always manager cultural majority popular. Song condition entire security concern science. Run number firm listen serious.",
  "date": "2026-01-01",
  "verified_purchase": true,
  "helpful_votes": 23
}


[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:
{
  "company": "Williams Ltd",
  "ticker": "IHFM",
  "quarter": "Q3 2022",
  "revenue": 93368790,
  "expenses": 48847964,
  "net_income": 12028281,
  "eps": 9.18,
  "metrics": {
    "profit_margin": 7.56,
    "roe": 13.89
  }
}

[Assistant]
Approach:
1. Task: Convert financial report 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"?>
<financial_report>
<company>Williams Ltd</company>
<ticker>IHFM</ticker>
<quarter>Q3 2022</quarter>
<revenue>93368790</revenue>
<expenses>48847964</expenses>
<net_income>12028281</net_income>
<eps>9.18</eps>
<metrics>
<profit_margin>7.56</profit_margin>
<roe>13.89</roe>
</metrics>
</financial_report>


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

[User]
Transform this JSON data into XML format:
{
  "post_id": "POST-78635818",
  "platform": "facebook",
  "user_id": "a739269a-9642-463c-9c88-cb97c795c8d8",
  "username": "kevin10",
  "content": "Specific other kind choice. Condition main resource finish north reach with break. Area strategy huge edge.",
  "timestamp": "2026-01-07T13:51:25.965362",
  "hashtags": [
    "#model",
    "#firm"
  ],
  "engagement": {
    "likes": 3831,
    "shares": 379,
    "comments": 204
  }
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<social_media_post>
<post_id>POST-78635818</post_id>
<platform>facebook</platform>
<user_id>a739269a-9642-463c-9c88-cb97c795c8d8</user_id>
<username>kevin10</username>
<content>Specific other kind choice. Condition main resource finish north reach with break. Area strategy huge edge.</content>
<timestamp>2026-01-07T13:51:25.965362</timestamp>
<hashtags>#model</hashtags>
<hashtags>#firm</hashtags>
<engagement>
<likes>3831</likes>
<shares>379</shares>
<comments>204</comments>
</engagement>
</social_media_post>


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

[User] Create a XML representation of student assessment.

[Assistant]
Approach:
1. Task: Create student assessment 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"?>
<student_assessment>
<scores>
<question>1</question>
<points_earned>8</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>2</question>
<points_earned>4</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>4</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>5</question>
<points_earned>8</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>6</question>
<points_earned>10</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>0</points_earned>
<points_possible>10</points_possible>
</scores>
<grade>C</grade>
<date>2026-01-01</date>
</student_assessment>


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

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

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

Output:
category,content,currency,date,helpful_votes,is_available,name,price,product_id,rating,review_id,reviews,specs_dimensions,specs_weight_kg,stock,title,user_id,verified_purchase
,"Address music major. Magazine three about. Security ready result improve.
Hand other collection name",,2026-01-03,50,,,,PROD-326180,4,REV-8075236,,,,,Most teacher Mrs system watch.,e70c9373-b1ad-41a5-8939-e3c28041d8f5,False
electronics,,USD,,,True,Profit-focused tertiary adapter,507.18,PROD-564742,2.61,,884,18x18x86cm,37.31,152,,,
electronics,,USD,,,True,Quality-focused 3rdgeneration productivity,707.02,PROD-249143,3.37,,707,71x78x74cm,37.37,713,,,
books,,USD,,,True,Phased demand-driven monitoring,843.89,PROD-545884,3.4,,237,36x48x96cm,46.11,543,,,


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

[User]
Convert the following CSV to TOML:
contract_id,effective_date,parties,status,term_months,value
CTR-784600,2026-01-06,"[{""name"": ""Snyder-Thornton"", ""role"": ""party_a""}, {""name"": ""Oliver Group"", ""role"": ""party_b""}]",active,16,53888
CTR-695209,2026-01-03,"[{""name"": ""Howe LLC"", ""role"": ""party_a""}, {""name"": ""Chambers, Richardson and Sullivan"", ""role"": ""par",active,30,413817
CTR-762308,2026-01-01,"[{""name"": ""Rhodes, Clark and Ross"", ""role"": ""party_a""}, {""name"": ""Le Group"", ""role"": ""party_b""}]",pending,54,468174
CTR-849933,2026-01-02,"[{""name"": ""Rice, Heath and Phillips"", ""role"": ""party_a""}, {""name"": ""Oliver Group"", ""role"": ""party_b""",active,48,450525

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

Output:
contract_id = "CTR-784600"
effective_date = "2026-01-06"
term_months = 16
value = 53888
status = "active"
[[parties]]
name = "Snyder-Thornton"
role = "party_a"

[[parties]]
name = "Oliver Group"
role = "party_b"


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

[User] Generate lab result data in XML format.

[Assistant]
Approach:
1. Task: Create lab 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"?>
<lab_result>
<result_id>LAB-5796495</result_id>
<patient_mrn>MRN-496025</patient_mrn>
<order_date>2026-01-06</order_date>
<panel>Lipid</panel>
<results>
<test>Hemoglobin</test>
<value>74.9</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>68.3</value>
<unit>mg/dL</unit>
<flag>low</flag>
</results>
<results>
<test>WBC</test>
<value>121.2</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>142.6</value>
<unit>g/dL</unit>
<flag>normal</flag>
</results>
</lab_result>


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

[User] Create a XML representation of error log.

[Assistant]
Approach:
1. Task: Create error log 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"?>
<error_log>
<error_id>ff91c212-6cce-4ac2-978d-0740381882de</error_id>
<timestamp>2026-01-07T13:51:27.679071</timestamp>
<level>WARNING</level>
<service>drawService</service>
<message>Support red list product forget cut speak.</message>
<stack_trace>at girl.py:186</stack_trace>
<stack_trace>at hold.py:186</stack_trace>
<context>
<user_id>473e683b-291e-461f-b848-d224b7dcbd8b</user_id>
<request_id>454a35ad-23ee-42a8-9d57-dbf5cedbef74</request_id>
</context>
</error_log>


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

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

[Assistant]
Approach:
1. Task: Convert api specification from JSON 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,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/party_get_parameters,paths_/party_get_responses_200_description,paths_/party_get_responses_400_description,paths_/party_get_summary,publication_doi,publication_venue,publication_year,title
,,,,Object-based multimedia secured line API,1.0.0,,3.0.0,,"[{""name"": ""param0"", ""in"": ""query"", ""type"": ""string""}, {""name"": ""param1"", ""in"": ""query"", ""type"": ""str",Success,Bad Request,Discussion partner stay wear again.,,,,
Meeting material administration become within. Part however quite.,"[{""name"": ""Devon Bentley"", ""affiliation"": ""Campbell-Palmer"", ""email"": ""haley90@example.net""}, {""name",306,"Carr, Butler and Pruitt",,,"[""enter"", ""blue"", ""year"", ""hot""]",,arXiv:2022.42243,,,,,10.3428/FCjW,Science,2023,Cloned client-driven Graphical User Interface
"Able always newspaper take expert inside. Friend bank seat forget high nor.
Movie animal all policy ","[{""name"": ""Earl Goodwin"", ""affiliation"": ""Hernandez and Sons"", ""email"": ""dustin96@example.com""}, {""n",200,"Gonzalez, Moran and White",,,"[""development"", ""now"", ""what"", ""during"", ""professional""]",,arXiv:2021.87871,,,,,10.6337/KTqP,Nature,2023,Persevering well-modulated project
Part maybe somebody after. Prepare especially participant nature apply smile.,"[{""name"": ""Christopher Avery"", ""affiliation"": ""Clark, Bailey and Rodriguez"", ""email"": ""tbrown@exampl",64,None,,,"[""better"", ""quickly"", ""civil"", ""who""]",,arXiv:2022.53324,,,,,10.4616/jUDh,Science,2024,Multi-layered bifurcated focus group


[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"?>
<financial_report>
<company>Hill-Marsh</company>
<ticker>ZFVR</ticker>
<quarter>Q3 2024</quarter>
<revenue>46703834</revenue>
<expenses>77071880</expenses>
<net_income>4141173</net_income>
<eps>8.71</eps>
<metrics>
<profit_margin>28.84</profit_margin>
<roe>14.06</roe>
</metrics>
</financial_report>

[Assistant]
Approach:
1. Task: Convert financial report 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:
{
  "company": "Hill-Marsh",
  "ticker": "ZFVR",
  "quarter": "Q3 2024",
  "revenue": 46703834,
  "expenses": 77071880,
  "net_income": 4141173,
  "eps": 8.71,
  "metrics": {
    "profit_margin": 28.84,
    "roe": 14.06
  }
}


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

[User] Create a CSV representation of transaction record.

[Assistant]
Approach:
1. Task: Create transaction record 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:
customer_id,items,payment_method,subtotal,tax,timestamp,total,txn_id
acd22e98-51a5-48fa-ad66-a69b8fba3f2b,"[{""sku"": ""SKU-41387"", ""qty"": 1, ""price"": 386.75}]",,,171.02,2026-01-07T13:51:25.400660,,TXN-44773795
09af940e-cc0e-44da-aa7c-cee3ddb4b937,"[{""sku"": ""SKU-50191"", ""qty"": 4, ""price"": 360.52}, {""sku"": ""SKU-49381"", ""qty"": 2, ""price"": 425.12}, {",credit_card,111.26,157.87,2026-01-07T13:51:25.402856,509.77,TXN-21290452
81bce72b-5cfb-4075-9a8e-ea5388fcb612,"[{""sku"": ""SKU-46358"", ""qty"": 1, ""price"": 446.13}, {""sku"": ""SKU-56441"", ""qty"": 1, ""price"": 221.95}, {",credit_card,1612.53,11.12,2026-01-07T13:51:25.402939,1819.25,TXN-69347528
d827cdc7-daa4-4cd6-b2f4-8eb4853acada,"[{""sku"": ""SKU-80594"", ""qty"": 4, ""price"": 74.28}, {""sku"": ""SKU-61669"", ""qty"": 4, ""price"": 179.24}]",paypal,1028.94,108.61,2026-01-07T13:51:25.402990,258.37,TXN-20345904


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

[User]
Transform this CSV data into XML format:
abstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/next_get_parameters,paths_/next_get_responses_200_description,paths_/next_get_responses_400_description,paths_/next_get_summary,publication_doi,publication_venue,publication_year,title
,,,,Distributed high-level website API,1.0.0,,3.0.0,,"[{""name"": ""param0"", ""in"": ""query"", ""type"": ""string""}, {""name"": ""param1"", ""in"": ""query"", ""type"": ""str",Success,Bad Request,Movie my movie common adult.,,,,
Provide out moment hair. Not bed forward herself know fear remember.,"[{""name"": ""Ernest Rivera"", ""affiliation"": ""Sanchez PLC"", ""email"": ""jason82@example.org""}, {""name"": """,189,None,,,"[""she"", ""north"", ""yard"", ""pay""]",,arXiv:2022.19116,,,,,10.2959/AGvq,Cell,2021,Open-source disintermediate instruction set
Hand maybe capital begin support. Position capital put once increase believe design understand.,"[{""name"": ""Joseph Washington"", ""affiliation"": ""Garcia-Schultz"", ""email"": ""fernandezcharles@example.n",68,None,,,"[""those"", ""choice"", ""manager"", ""body"", ""director""]",,arXiv:2022.27549,,,,,10.8651/IiBa,Nature,2020,Synergistic 3rdgeneration firmware
Nation we year economic special. North staff seven coach.,"[{""name"": ""Natasha Murray"", ""affiliation"": ""Black-Horn"", ""email"": ""vgutierrez@example.net""}, {""name""",454,Bryan Group,,,"[""question"", ""building"", ""cultural"", ""war"", ""imagine""]",,arXiv:2021.57504,,,,,10.8712/WVkt,Cell,2022,Multi-tiered high-level framework
"Add often take energy practice lot section of. Matter occur number natural per.
Authority in everyon","[{""name"": ""Brad Ward"", ""affiliation"": ""Martin PLC"", ""email"": ""fhernandez@example.org""}, {""name"": ""Ke",410,James Ltd,,,"[""he"", ""box"", ""carry"", ""explain""]",,arXiv:2024.55685,,,,,10.2992/MJNk,Cell,2021,Enhanced stable migration

[Assistant]
Approach:
1. Task: Convert api specification 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"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Distributed high-level website API</title>
<version>1.0.0</version>
</info>
<paths>
</next>
<get>
<summary>Movie my movie common adult.</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>
<//next>
</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"?>
<product_listing>
<product_id>PROD-524008</product_id>
<name>Implemented multimedia focus group</name>
<category>electronics</category>
<price>524.9</price>
<currency>USD</currency>
<stock>714</stock>
<is_available>True</is_available>
<rating>2.56</rating>
<reviews>633</reviews>
<specs>
<weight_kg>40.1</weight_kg>
<dimensions>80x44x77cm</dimensions>
</specs>
</product_listing>

[Assistant]
Approach:
1. Task: Convert product listing 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:
{
  "product_id": "PROD-524008",
  "name": "Implemented multimedia focus group",
  "category": "electronics",
  "price": 524.9,
  "currency": "USD",
  "stock": 714,
  "is_available": true,
  "rating": 2.56,
  "reviews": 633,
  "specs": {
    "weight_kg": 40.1,
    "dimensions": "80x44x77cm"
  }
}


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

[User] Output api specification as JSON.

[Assistant]
Approach:
1. Task: Create api specification 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:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Assimilated neutral archive API",
    "version": "1.0.0"
  },
  "paths": {
    "/sea": {
      "get": {
        "summary": "Team happen challenge address expert manage beyond",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param2",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}


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

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

[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>
<eps>6.0</eps>
<company>Richardson-Gonzalez</company>
<quarter>Q3 2020</quarter>
<net_income>13953656</net_income>
</financial_report>


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

[User]
Convert the following CSV to YAML:
contract_id,effective_date,parties,status,term_months,value
CTR-919818,,"[{""name"": ""Riggs, Carey and Rojas"", ""role"": ""party_a""}, {""name"": ""Mcdowell-Koch"", ""role"": ""party_b""}",active,18,911148
CTR-152138,2026-01-03,"[{""name"": ""Harris-Clay"", ""role"": ""party_a""}, {""name"": ""Turner LLC"", ""role"": ""party_b""}]",executed,40,677618
CTR-755246,2026-01-01,"[{""name"": ""Lewis LLC"", ""role"": ""party_a""}, {""name"": ""Aguilar Inc"", ""role"": ""party_b""}]",executed,45,400510

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

Output:
value: 911148
contract_id: CTR-919818
parties:
- name: Riggs, Carey and Rojas
  role: party_a
- name: Mcdowell-Koch
  role: party_b
status: active
term_months: 18


[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:
{
  "post_id": "POST-23186111",
  "platform": "twitter",
  "user_id": "85951ac5-a9b8-4154-8edc-693bcde245cf",
  "username": "srodriguez",
  "content": "Stand leave decade year collection. Republican point edge yet business.\nSuffer accept central against. Cup theory mouth side message.\nConcern magazine exactly maybe oil difficult.",
  "timestamp": "2026-01-07T13:51:25.750515",
  "hashtags": [
    "#community",
    "#whatever"
  ],
  "engagement": {
    "likes": 4745,
    "shares": 251,
    "comments": 51
  }
}

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

Output:
post_id = "POST-23186111"
platform = "twitter"
user_id = "85951ac5-a9b8-4154-8edc-693bcde245cf"
username = "srodriguez"
content = "Stand leave decade year collection. Republican point edge yet business.\nSuffer accept central against. Cup theory mouth side message.\nConcern magazine exactly maybe oil difficult."
timestamp = "2026-01-07T13:51:25.750515"
hashtags = [ "#community", "#whatever",]

[engagement]
likes = 4745
shares = 251
comments = 51


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

[User] Generate customer review data in JSON format.

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

Output:
{
  "review_id": "REV-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
}


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

[User]
Transform this XML data into JSON format:
<?xml version="1.0" encoding="UTF-8"?>
<financial_report>
<company>Nichols, Ferguson and Butler</company>
<ticker>NDVN</ticker>
<quarter>Q1 2022</quarter>
<revenue>39470251</revenue>
<expenses>26562838</expenses>
<net_income>16784469</net_income>
<eps>3.2</eps>
<metrics>
<profit_margin>27.93</profit_margin>
<roe>5.96</roe>
</metrics>
</financial_report>

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


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

[User] Generate lab result data in JSON format.

[Assistant]
Approach:
1. Task: Create lab result 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:
{
  "order_date": "2026-01-05",
  "results": [
    {
      "test": "Hemoglobin",
      "value": 95.5,
      "unit": "g/dL",
      "flag": "low"
    },
    {
      "test": "Hemoglobin",
      "value": 52.7,
      "unit": "mg/dL",
      "flag": "high"
    },
    {
      "test": "Glucose",
      "value": 142.9,
      "unit": "mg/dL",
      "flag": "low"
    },
    {
      "test": "Glucose",
      "value": 146.5,
      "unit": "mg/dL",
      "flag": "high"
    }
  ],
  "panel": "Lipid"
}


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

[User] Create a YAML representation of prescription.

[Assistant]
Approach:
1. Task: Create prescription 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:
rx_id: RX-8350891
patient_mrn: MRN-446802
prescriber: James Bryant
date: '2026-01-03'
medications:
- name: Lisinopril
  dosage: 10mg
  frequency: daily
  quantity: 90
- name: Metformin
  dosage: 20mg
  frequency: TID
  quantity: 30


[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: medium - 5-8 fields, 2-3 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Populate fields with realistic example data based on the schema.

Output:
post_id: POST-54622203
platform: instagram
user_id: 1456e108-0a50-4482-8f1a-b1cb2398a121
username: fullersteven
content: 'Card these member kid western growth. Staff draw say early town general.
  Large break interesting ten against open.

  Any fine power truth. Big like investment simple whatever education.'
timestamp: '2026-01-07T13:51:25.504049'
hashtags:
- '#deep'
- '#yes'
- '#long'
- '#including'
engagement:
  likes: 464
  shares: 699
  comments: 294


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

[User] Create a JSON representation of research paper.

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

Output:
{
  "paper_id": "arXiv:2023.47681",
  "title": "Devolved bi-directional info-mediaries",
  "authors": [
    {
      "name": "Christian Randolph",
      "affiliation": "Hunt-Haynes",
      "email": "patrickmaddox@example.net"
    },
    {
      "name": "Allen Lewis",
      "affiliation": "Owen PLC",
      "email": "alexanderhenry@example.net"
    },
    {
      "name": "Cody Martin",
      "affiliation": "Mcknight PLC",
      "email": "michael00@example.org"
    }
  ],
  "abstract": "Help field ten it. Pick eight last star pull. Act politics discuss.",
  "keywords": [
    "hard",
    "open",
    "right",
    "could",
    "sea"
  ],
  "publication": {
    "venue": "Cell",
    "year": 2023,
    "doi": "10.8057/cNYF"
  },
  "citations": 411,
  "funding_source": null
}


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

[User]
Transform this CSV data into YAML format:
customer_id,items,payment_method,subtotal,tax,timestamp,total,txn_id
b5aca191-66fe-49e0-85ce-2d363d5ef454,"[{""sku"": ""SKU-56664"", ""qty"": 2, ""price"": 285.83}, {""sku"": ""SKU-25305"", ""qty"": 1, ""price"": 45.15}, {""",apple_pay,199.93,118.13,2026-01-07T13:51:26.163076,913.78,TXN-30876983
40d5c2fa-d45f-46d0-8fb5-912b29691f53,"[{""sku"": ""SKU-63266"", ""qty"": 4, ""price"": 427.22}, {""sku"": ""SKU-35151"", ""qty"": 5, ""price"": 360.57}]",credit_card,199.5,14.18,2026-01-07T13:51:26.164477,1360.45,TXN-60689807
d5a8d4eb-0a45-4682-beb8-8cb84689c4fa,"[{""sku"": ""SKU-91094"", ""qty"": 2, ""price"": 158.74}, {""sku"": ""SKU-24275"", ""qty"": 4, ""price"": 37.25}, {""",credit_card,1921.94,159.34,2026-01-07T13:51:26.164521,1244.14,TXN-22923057

[Assistant]
Approach:
1. Task: Convert transaction record 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:
txn_id: TXN-30876983
customer_id: b5aca191-66fe-49e0-85ce-2d363d5ef454
timestamp: '2026-01-07T13:51:26.163076'
items:
- sku: SKU-56664
  qty: 2
  price: 285.83
- sku: SKU-25305
  qty: 1
  price: 45.15
- sku: SKU-78820
  qty: 4
  price: 47.49
subtotal: 199.93
tax: 118.13
total: 913.78
payment_method: apple_pay


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

[User] Generate news article data in CSV format.

[Assistant]
Approach:
1. Task: Create news article 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:
article_id,author,content,headline,published,section,shares,tags,views
ART-1823437,Anna Ortiz,"Success off activity him process hot whose pay. Most probably including at arm avoid media finally.
",Integrated content-based throughput,2026-01-05T06:32:59.977242,Politics,3070,"[""base"", ""fight"", ""test""]",75522
ART-7726821,Devin Davis,Kind feel community southern guy figure. Model I commercial hold dog. Meeting student up care nor yo,Focused 24hour data-warehouse,2026-01-04T08:55:25.202540,Tech,1143,"[""administration"", ""over"", ""wear"", ""notice""]",68951
ART-7786819,Jeffery Allen,Matter simply might Democrat. Treat food protect bit. Newspaper worry generation way might purpose p,Advanced fresh-thinking migration,2026-01-04T01:22:06.456435,Tech,1698,"[""personal"", ""edge"", ""director""]",13606
ART-3636890,Jessica Estrada,"Board forget read western. Late change tree follow keep analysis.
Prevent begin add market scientist",Visionary hybrid analyzer,2026-01-04T04:35:25.267941,Sports,830,"[""hope"", ""American"", ""through"", ""consumer""]",67881
ART-1015403,Kelly Dawson,When write down ground they dark under class. Fight lay enter effort author go just. Not very probab,Synergized modular Graphical User Interface,2026-01-02T01:34:47.009501,Tech,640,"[""magazine"", ""heart"", ""minute"", ""whose""]",89829


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

[User] Create a CSV representation of sales analytics.

[Assistant]
Approach:
1. Task: Create sales analytics 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:
abstract,authors,channels,citations,funding_source,keywords,paper_id,period,publication_doi,publication_venue,publication_year,title,top_products,total_revenue,units_sold
,,"[{""name"": ""online"", ""revenue"": 3952303, ""growth"": 2.75}, {""name"": ""retail"", ""revenue"": 3970412, ""gro",,,,,March 2024,,,,,"[{""sku"": ""SKU-2514"", ""sales"": 485558}, {""sku"": ""SKU-5241"", ""sales"": 142515}, {""sku"": ""SKU-4600"", ""sa",2433324,8686
Activity work as. Sense television must perform son. Production as front perhaps too firm reflect.,"[{""name"": ""Tanya Garner"", ""affiliation"": ""Garza-Black"", ""email"": ""qchandler@example.net""}, {""name"": ",,473,"Cook, Hayes and Carpenter","[""fast"", ""industry"", ""trouble"", ""foreign"", ""charge""]",arXiv:2022.78747,,10.4984/DwZx,Cell,2023,Streamlined methodical budgetary management,,,
Husband concern threat first such job whom. Half history west remember usually.,"[{""name"": ""Brenda Burns"", ""affiliation"": ""Mcintyre, Manning and Allen"", ""email"": ""ericwilliams@examp",,315,"Brown, Chapman and Howard","[""week"", ""stage"", ""business"", ""need""]",arXiv:2023.46731,,10.2309/NSjW,Cell,2024,Enhanced upward-trending data-warehouse,,,
Skin paper add hand different scientist throw. Rule positive debate until bag.,"[{""name"": ""Joshua Moore"", ""affiliation"": ""Mclaughlin, Johnson and Ortega"", ""email"": ""elarson@example",,339,"Bennett, Edwards and Navarro","[""fund"", ""hotel"", ""next"", ""performance""]",arXiv:2024.89687,,10.1074/OrPa,Nature,2021,Polarized coherent migration,,,


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

[User] Generate contract data in YAML format.

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

Output:
contract_id: CTR-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


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

[User] Output student assessment as XML.

[Assistant]
Approach:
1. Task: Create student assessment 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"?>
<student_assessment>
<assessment_id>ASMT-422317</assessment_id>
<student_id>STU-280699</student_id>
<course_id>CRS-7308</course_id>
<type>exam</type>
<date>2026-01-01</date>
<scores>
<question>1</question>
<points_earned>2</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>2</question>
<points_earned>3</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>1</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>5</question>
<points_earned>10</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>6</question>
<points_earned>3</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>7</question>
<points_earned>7</points_earned>
<points_possible>10</points_possible>
</scores>
<total_score>75</total_score>
<percentage>83.59</percentage>
<grade>B</grade>
</student_assessment>


[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:
abstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/article_get_parameters,paths_/article_get_responses_200_description,paths_/article_get_responses_400_description,paths_/article_get_summary,publication_doi,publication_venue,publication_year,title
,,,,Secured well-modulated policy API,1.0.0,,3.0.0,,"[{""name"": ""param0"", ""in"": ""query"", ""type"": ""string""}, {""name"": ""param1"", ""in"": ""query"", ""type"": ""str",Success,Bad Request,During certainly full.,,,,
Across improve away population. Focus term customer nature worry design cut carry.,"[{""name"": ""Joe Johnson"", ""affiliation"": ""Fleming-Foster"", ""email"": ""michael23@example.com""}, {""name""",432,None,,,"[""lose"", ""family"", ""quickly"", ""place""]",,arXiv:2020.51769,,,,,10.8103/RBTT,Science,2021,Grass-roots 24/7 help-desk
"Hard participant thing sister detail region. Bad build deal career up.
North deal physical onto mess","[{""name"": ""Jonathan Moss"", ""affiliation"": ""Ramirez LLC"", ""email"": ""robert59@example.org""}, {""name"": ",499,None,,,"[""any"", ""catch"", ""cut"", ""wide"", ""cause""]",,arXiv:2020.27097,,,,,10.9577/iSRI,Nature,2021,Centralized scalable strategy
Everything seem alone want. Strong beat road skin. Statement team small.,"[{""name"": ""Eric Quinn"", ""affiliation"": ""Vazquez Inc"", ""email"": ""ewilliams@example.net""}, {""name"": ""I",89,Patton-Flores,,,"[""score"", ""us"", ""situation""]",,arXiv:2023.43567,,,,,10.2249/JZUK,Nature,2023,Ergonomic logistical collaboration

[Assistant]
Approach:
1. Task: Convert api specification from CSV 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:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Secured well-modulated policy API",
    "version": "1.0.0"
  },
  "paths": {
    "/article": {
      "get": {
        "summary": "During certainly full.",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param2",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}


[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"?>
<product_listing>
<product_id>PROD-891981</product_id>
<name>Focused background info-mediaries</name>
<category>books</category>
<price>16.4</price>
<currency>USD</currency>
<stock>192</stock>
<is_available>True</is_available>
<rating>3.23</rating>
<reviews>117</reviews>
<specs>
<weight_kg>31.51</weight_kg>
<dimensions>65x39x62cm</dimensions>
</specs>
</product_listing>

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


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

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

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<clinical_note>
<note_id>CN-2341842</note_id>
<patient>
<mrn>MRN-739833</mrn>
<age>85</age>
<gender>F</gender>
</patient>
<encounter_date>2026-01-01</encounter_date>
<chief_complaint>fever</chief_complaint>
<vitals>
<bp>174/60</bp>

60

<temp_f>98.7</temp_f>
</vitals>
<assessment>
<problem>diabetes</problem>
<icd10>I65</icd10>
</assessment>
<assessment>
<problem>diabetes</problem>
<icd10>J29</icd10>
</assessment>
</clinical_note>


[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-02,CBC,MRN-357903,LAB-5790382,"[{""test"": ""Glucose"", ""value"": 56.1, ""unit"": ""mg/dL"", ""flag"": ""high""}, {""test"": ""Glucose"", ""value"": 1"
2026-01-01,CBC,MRN-122641,LAB-3615713,"[{""test"": ""Glucose"", ""value"": 67.6, ""unit"": ""mg/dL"", ""flag"": ""high""}, {""test"": ""Hemoglobin"", ""value"""
2026-01-05,CMP,MRN-382292,LAB-7044015,"[{""test"": ""Glucose"", ""value"": 57.5, ""unit"": ""mg/dL"", ""flag"": ""normal""}, {""test"": ""WBC"", ""value"": 162"
2026-01-05,CMP,MRN-248964,LAB-9974854,"[{""test"": ""Glucose"", ""value"": 164.0, ""unit"": ""mg/dL"", ""flag"": ""normal""}, {""test"": ""Glucose"", ""value"""


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

[User] Output prescription as TOML.

[Assistant]
Approach:
1. Task: Create prescription 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:
prescriber = "Isaac Howard"
date = "2026-01-03"
[[medications]]
name = "Atorvastatin"
dosage = "5mg"
frequency = "BID"
quantity = 30


[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"?>
<prescription>
<rx_id>RX-1995080</rx_id>
<patient_mrn>MRN-674224</patient_mrn>
<prescriber>Emily Herrera</prescriber>
<date>2026-01-05</date>
<medications>
<name>Lisinopril</name>
<dosage>10mg</dosage>
<frequency>BID</frequency>
<quantity>60</quantity>
</medications>
</prescription>

[Assistant]
Approach:
1. Task: Convert prescription 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:
{
  "rx_id": "RX-1995080",
  "patient_mrn": "MRN-674224",
  "prescriber": "Emily Herrera",
  "date": "2026-01-05",
  "medications": [
    {
      "name": "Lisinopril",
      "dosage": "10mg",
      "frequency": "BID",
      "quantity": 60
    }
  ]
}


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

[User]
Convert the following JSON to XML:
{
  "product_id": "PROD-651261",
  "name": "Cross-platform scalable protocol",
  "category": "clothing",
  "price": 855.77,
  "currency": "USD",
  "stock": 343,
  "is_available": true,
  "rating": 3.23,
  "reviews": 830,
  "specs": {
    "weight_kg": 21.29,
    "dimensions": "84x20x91cm"
  }
}

[Assistant]
Approach:
1. Task: Convert product listing 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"?>
<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 CSV format. Think step-by-step, then generate syntactically perfect CSV.

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

[Assistant]
Approach:
1. Task: Create social media post 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:
content,engagement_comments,engagement_likes,engagement_shares,hashtags,platform,post_id,timestamp,user_id,username
Treat second sing development scientist particularly their. Like question recently line top. Resourc,194,4027,604,"[""#box"", ""#speak"", ""#reason""]",instagram,POST-61935008,2026-01-07T13:51:25.597395,ecd9585e-2adb-45f4-adda-e91c5f4f7ebe,halezachary
"Happy indeed whole day. Nor brother type. Cell recently method boy ability.
Human much push travel l",264,9516,995,"[""#central"", ""#step"", ""#instead""]",twitter,POST-22399127,2026-01-07T13:51:25.598790,6fce34a9-fae5-4e99-9fc0-2d124b25aa8d,ecole
Sing hospital marriage travel. Tend course sort single. Soon teacher almost north day environmental ,307,4702,221,"[""#watch"", ""#institution"", ""#piece"", ""#that""]",facebook,POST-79060770,2026-01-07T13:51:25.599113,01f7b26f-f630-4ba3-b553-d8bb7e426f3e,rallen
Important build nature reveal guy within these. Factor give act after trial live. Degree camera both,105,6399,218,"[""#test"", ""#matter"", ""#feel""]",twitter,POST-50100929,2026-01-07T13:51:25.599491,54e59b76-fd44-4594-80ea-79833b703591,wilsonpatricia
"Certainly third year property rise world but. Operation throw law current.
Bring realize believe him",231,8474,906,"[""#save"", ""#economy""]",instagram,POST-60695938,2026-01-07T13:51:25.599822,e583fff0-b790-400b-9f04-7c3448c1ff2b,obrewer


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

[User] Generate lab result data in JSON format.

[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-3941350",
  "patient_mrn": "MRN-739958",
  "order_date": "2026-01-01",
  "panel": "CBC",
  "results": [
    {
      "test": "Glucose",
      "value": 134.1,
      "unit": "mg/dL",
      "flag": "high"
    },
    {
      "test": "WBC",
      "value": 188.7,
      "unit": "g/dL",
      "flag": "low"
    },
    {
      "test": "Hemoglobin",
      "value": 142.9,
      "unit": "mg/dL",
      "flag": "high"
    },
    {
      "test": "Hemoglobin",
      "value": 117.3,
      "unit": "g/dL",
      "flag": "normal"
    },
    {
      "test": "Glucose",
      "value": 159.8,
      "unit": "g/dL",
      "flag": "normal"
    },
    {
      "test": "WBC",
      "value": 131.5,
      "unit": "g/dL",
      "flag": "normal"
    }
  ]
}


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

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

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

Output:
{
  "paper_id": "arXiv:2023.21424",
  "title": "Cross-platform fault-tolerant circuit",
  "authors": [
    {
      "name": "Charlotte Sellers",
      "affiliation": "Armstrong-Marks",
      "email": "weaverelizabeth@example.com"
    },
    {
      "name": "Cynthia Johnston MD",
      "affiliation": "Rogers Inc",
      "email": "ccastaneda@example.org"
    },
    {
      "name": "Robert Velasquez",
      "affiliation": "Alvarado LLC",
      "email": "psullivan@example.net"
    }
  ],
  "abstract": "Truth himself long country car environment. Free design relate hope admit learn identify.",
  "keywords": [
    "share",
    "feeling",
    "environmental"
  ],
  "publication": {
    "venue": "Science",
    "year": 2022,
    "doi": "10.6091/Sfwn"
  },
  "citations": 477,
  "funding_source": "Barker-Wise"
}


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

[User]
Reformat the data below from YAML to TOML:
timestamp: '2026-01-07T13:51:25.400660'
items:
- sku: SKU-41387
  qty: 1
  price: 386.75
txn_id: TXN-44773795
customer_id: acd22e98-51a5-48fa-ad66-a69b8fba3f2b
tax: 171.02

[Assistant]
Approach:
1. Task: Convert transaction record from YAML 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:
timestamp = "2026-01-07T13:51:25.400660"
txn_id = "TXN-44773795"
customer_id = "acd22e98-51a5-48fa-ad66-a69b8fba3f2b"
tax = 171.02
[[items]]
sku = "SKU-41387"
qty = 1
price = 386.75


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

[User] Create a JSON representation of course syllabus.

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

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


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

[User]
Convert the following CSV to TOML:
category,content,currency,date,helpful_votes,is_available,name,price,product_id,rating,review_id,reviews,specs_dimensions,specs_weight_kg,stock,title,user_id,verified_purchase
,Hear media safe I visit language. Difference part thousand. Society inside describe decision.,,2026-01-06,16,,,,PROD-143836,2,REV-3982215,,,,,Fight and building toward office.,0dd51960-e54b-4127-90d4-b32b17839969,True
electronics,,USD,,,True,Vision-oriented uniform contingency,642.59,PROD-746056,2.51,,629,20x72x47cm,14.55,351,,,
clothing,,USD,,,True,Stand-alone 24hour approach,635.33,PROD-937217,3.7,,660,36x60x25cm,1.35,509,,,

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

Output:
review_id = "REV-3982215"
product_id = "PROD-143836"
user_id = "0dd51960-e54b-4127-90d4-b32b17839969"
rating = 2
title = "Fight and building toward office."
content = "Hear media safe I visit language. Difference part thousand. Society inside describe decision."
date = "2026-01-06"
verified_purchase = true
helpful_votes = 16


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

[User] Output contract as XML.

[Assistant]
Approach:
1. Task: Create contract in XML
2. Complexity: 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"?>
<contract>
<contract_id>CTR-123472</contract_id>
<parties>
<name>Palmer-White</name>
<role>party_a</role>
</parties>
<parties>
<name>Rodriguez-Moore</name>
<role>party_b</role>
</parties>
<effective_date>2026-01-06</effective_date>
<term_months>59</term_months>
<value>388976</value>
<status>pending</status>
</contract>


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

[User]
Reformat the data below from TOML to YAML:
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"

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

[User]
Transform this JSON data into XML format:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Intuitive disintermediate website API",
    "version": "1.0.0"
  },
  "paths": {
    "/reality": {
      "get": {
        "summary": "Activity public whole paper there relationship tas",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Intuitive disintermediate website API</title>
<version>1.0.0</version>
</info>
<paths>
</reality>
<get>
<summary>Activity public whole paper there relationship tas</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>
<//reality>
</paths>
</api_specification>


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

[User] Output product listing as JSON.

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

Output:
{
  "product_id": "PROD-325945",
  "name": "Universal bottom-line system engine",
  "category": "electronics",
  "price": 225.75,
  "currency": "USD",
  "stock": 955,
  "is_available": true,
  "rating": 3.31,
  "reviews": 802,
  "specs": {
    "weight_kg": 22.25,
    "dimensions": "77x29x32cm"
  }
}


[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: 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:
rx_id: RX-6885629
prescriber: John Cook
medications:
- name: Metformin
  dosage: 5mg
  frequency: daily
  quantity: 30
- name: Atorvastatin
  dosage: 5mg
  frequency: BID
  quantity: 90
- name: Lisinopril
  dosage: 5mg
  frequency: TID
  quantity: 60
date: '2026-01-02'
patient_mrn: MRN-741538


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

[User] Create a TOML representation of 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 = "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] Generate research paper data in YAML format.

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


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

[User] Generate experiment result data in JSON format.

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