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

[User] Output product listing as XML.

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<product_listing>
<product_id>PROD-723394</product_id>
<name>Streamlined full-range ability</name>
<category>clothing</category>
<price>959.9</price>
<currency>USD</currency>
<stock>28</stock>
<is_available>True</is_available>
<rating>3.7</rating>
<reviews>332</reviews>
<specs>
<weight_kg>9.93</weight_kg>
<dimensions>53x67x45cm</dimensions>
</specs>
</product_listing>


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

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

[Assistant]
Approach:
1. Task: Create social media post in CSV
2. Complexity: 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
Forget late prevent year cold able arrive. Few possible himself sing community. Activity campaign su,482,3344,900,"[""#drop"", ""#consider"", ""#nature"", ""#all""]",facebook,POST-86945311,2026-01-07T13:51:26.810240,b9da037c-f6cd-4ced-8c95-ca7562cf6118,martinsteven
"Explain son program science paper evening chance before.
Improve subject you throw difficult section",268,4160,122,"[""#effort"", ""#vote"", ""#behind""]",instagram,POST-89391113,2026-01-07T13:51:26.811649,688b5b55-e549-4b48-9b27-44ea73883cf0,leedanielle
Know item future general public rich again. Stock green enough wonder suffer.,154,8825,337,"[""#kitchen"", ""#produce"", ""#executive""]",twitter,POST-22462345,2026-01-07T13:51:26.812027,ae08132b-1401-4b9c-96e8-11bf9f8cdb57,barneskristine
"Specific somebody difficult language. None stage color employee evening really center.
Thus usually ",484,5851,696,"[""#word"", ""#late"", ""#value"", ""#president""]",facebook,POST-30269346,2026-01-07T13:51:26.812330,8a63b8bb-cc35-4bf1-8bb9-e3966ff7045b,hfox


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

[User] Generate contract data in JSON format.

[Assistant]
Approach:
1. Task: Create contract 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:
{
  "effective_date": "2026-01-03",
  "value": 837359,
  "term_months": 24,
  "status": "executed"
}


[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-8706225</rx_id>
<patient_mrn>MRN-970748</patient_mrn>
<prescriber>Brady Keller</prescriber>
<date>2026-01-01</date>
<medications>
<name>Lisinopril</name>
<dosage>5mg</dosage>
<frequency>TID</frequency>
<quantity>30</quantity>
</medications>
</prescription>


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

[User] Generate financial report data in XML format.

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<financial_report>
<company>Taylor Ltd</company>
<ticker>AOED</ticker>
<quarter>Q1 2024</quarter>
<revenue>69752271</revenue>
<expenses>52626087</expenses>
<net_income>18580243</net_income>
<eps>1.63</eps>
<metrics>
<profit_margin>23.4</profit_margin>
<roe>21.22</roe>
</metrics>
</financial_report>


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

[User]
Reformat the data below from TOML to CSV:
company = "Moore-Thompson"
ticker = "XFVE"
quarter = "Q2 2022"
revenue = 73324772
expenses = 43130054
net_income = 18329728
eps = 9.88

[metrics]
profit_margin = 22.03
roe = 10.54

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

Output:
company,eps,expenses,metrics_profit_margin,metrics_roe,net_income,quarter,revenue,ticker
Moore-Thompson,9.88,43130054,22.03,10.54,18329728,Q2 2022,73324772,XFVE
Duran-Davis,2.51,10780399,25.22,20.67,375029,Q1 2023,55668459,CTUP
"Boyd, Jones and Gutierrez",1.84,11683095,14.85,5.3,5669472,Q2 2021,44633831,YDXA
Fleming Inc,6.17,26340930,19.31,21.04,15077203,Q2 2022,34770056,HPPD
Petersen-Hart,1.14,49442536,10.53,12.85,13772526,Q2 2022,57819296,EEVB


[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:
{
  "rx_id": "RX-7665793",
  "patient_mrn": "MRN-934255",
  "prescriber": "Danielle Brown",
  "date": "2026-01-06",
  "medications": [
    {
      "name": "Atorvastatin",
      "dosage": "20mg",
      "frequency": "daily",
      "quantity": 90
    },
    {
      "name": "Atorvastatin",
      "dosage": "5mg",
      "frequency": "BID",
      "quantity": 90
    },
    {
      "name": "Metformin",
      "dosage": "5mg",
      "frequency": "BID",
      "quantity": 60
    }
  ]
}

[Assistant]
Approach:
1. Task: Convert prescription 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"?>
<prescription>
<rx_id>RX-7665793</rx_id>
<patient_mrn>MRN-934255</patient_mrn>
<prescriber>Danielle Brown</prescriber>
<date>2026-01-06</date>
<medications>
<name>Atorvastatin</name>
<dosage>20mg</dosage>
<frequency>daily</frequency>
<quantity>90</quantity>
</medications>
<medications>
<name>Atorvastatin</name>
<dosage>5mg</dosage>
<frequency>BID</frequency>
<quantity>90</quantity>
</medications>
<medications>
<name>Metformin</name>
<dosage>5mg</dosage>
<frequency>BID</frequency>
<quantity>60</quantity>
</medications>
</prescription>


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

[User] Generate lab result data in TOML format.

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

Output:
result_id = "LAB-4504067"
patient_mrn = "MRN-266543"
order_date = "2026-01-05"
panel = "Lipid"
[[results]]
test = "Glucose"
value = 181.1
unit = "g/dL"
flag = "normal"

[[results]]
test = "Hemoglobin"
value = 164.3
unit = "mg/dL"
flag = "low"

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

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


[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: 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:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Visionary eco-centric methodology API",
    "version": "1.0.0"
  },
  "paths": {
    "/edge": {
      "get": {
        "summary": "Simple really social range.",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}


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

[User] Generate financial report data in YAML format.

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

Output:
company: Moore-Thompson
ticker: XFVE
quarter: Q2 2022
revenue: 73324772
expenses: 43130054
net_income: 18329728
eps: 9.88
metrics:
  profit_margin: 22.03
  roe: 10.54


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

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

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<customer_review>
<review_id>REV-7250124</review_id>
<product_id>PROD-375265</product_id>
<user_id>48302d32-0445-4405-afc6-604ef6300782</user_id>
<rating>1</rating>
<title>Very responsibility coach economy sea public you.</title>
<content>Chair painting shake city kind good though. Find reality water support key.
Fly party couple production fight. Live attention anyone her traditional. I room blood condition research fund model.</content>
<date>2026-01-03</date>
<verified_purchase>True</verified_purchase>
<helpful_votes>78</helpful_votes>
</customer_review>


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

[User]
Transform this CSV data into TOML format:
abstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/finally_get_parameters,paths_/finally_get_responses_200_description,paths_/finally_get_responses_400_description,paths_/finally_get_summary,publication_doi,publication_venue,publication_year,title
,,,,Robust demand-driven hub API,1.0.0,,3.0.0,,"[{""name"": ""param0"", ""in"": ""query"", ""type"": ""string""}, {""name"": ""param1"", ""in"": ""query"", ""type"": ""str",Success,Bad Request,Describe experience pick treatment up remain withi,,,,
Threat able no around later quickly upon. Rule address another tree end affect.,"[{""name"": ""Matthew Richards"", ""affiliation"": ""Hernandez-Rivera"", ""email"": ""jonathan71@example.net""},",37,None,,,"[""first"", ""sea"", ""cup"", ""than""]",,arXiv:2024.30877,,,,,10.3397/HKLv,Nature,2022,Operative dynamic definition
Employee news catch. Civil while sit behind how may authority.,"[{""name"": ""Jonathan Harrison"", ""affiliation"": ""Bryant-Mendoza"", ""email"": ""jacobwilliams@example.net""",412,None,,,"[""step"", ""if"", ""whether"", ""tend""]",,arXiv:2023.74568,,,,,10.5707/kRyB,Science,2020,Re-engineered next generation contingency

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

[info]
title = "Robust demand-driven hub API"
version = "1.0.0"

[paths."/finally".get]
summary = "Describe experience pick treatment up remain withi"
[[paths."/finally".get.parameters]]
name = "param0"
in = "query"
type = "string"

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

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

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

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


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

[User] Output sales analytics as TOML.

[Assistant]
Approach:
1. Task: Create sales analytics 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:
period = "February 2020"
total_revenue = 2337421
units_sold = 23839
[[channels]]
name = "retail"
revenue = 3840938
growth = 18.52

[[channels]]
name = "wholesale"
revenue = 1512471
growth = 13.02

[[top_products]]
sku = "SKU-1744"
sales = 276633

[[top_products]]
sku = "SKU-5145"
sales = 26445

[[top_products]]
sku = "SKU-9218"
sales = 412054


[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:
{
  "title": "Polarized methodical algorithm",
  "authors": [
    {
      "name": "Caroline Barnes",
      "affiliation": "Parker Ltd",
      "email": "angelajackson@example.net"
    },
    {
      "name": "Mario Boyd",
      "affiliation": "Johnson, Barber and Higgins",
      "email": "lfuller@example.com"
    }
  ],
  "funding_source": null
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<title>Polarized methodical algorithm</title>
<authors>
<name>Caroline Barnes</name>
<affiliation>Parker Ltd</affiliation>
<email>angelajackson@example.net</email>
</authors>
<authors>
<name>Mario Boyd</name>
<affiliation>Johnson, Barber and Higgins</affiliation>
<email>lfuller@example.com</email>
</authors>
<funding_source />
</research_paper>


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

[User] Produce a JSON document for a error log.

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

Output:
{
  "error_id": "19a033e5-3ad7-4877-8a96-e38503174031",
  "timestamp": "2026-01-07T13:51:26.139508",
  "level": "ERROR",
  "service": "offService",
  "message": "Light method real rich option.",
  "stack_trace": [
    "at very.py:253",
    "at piece.py:469",
    "at home.py:259"
  ],
  "context": {
    "user_id": "45de80c2-9a4d-4d83-abf9-651f235bf4e8",
    "request_id": "53b4884a-375f-459c-a303-838dd3a8411e"
  }
}


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

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

[Assistant]
Approach:
1. Task: Create social media post in TOML
2. Complexity: 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:
post_id = "POST-86898750"
platform = "instagram"
user_id = "a47ec401-ca4e-44b5-afc7-6c2b372f589e"
username = "dylan00"
content = "Might north politics.\nMoment bad without change physical store call. Enjoy question state student political boy tonight.\nSoon ten last small develop left enter. Health lead bank and air capital save."
timestamp = "2026-01-07T13:51:25.591017"
hashtags = [ "#kid", "#off", "#school", "#fund",]

[engagement]
likes = 9146
shares = 205
comments = 18


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

[User]
Reformat the data below from XML to YAML:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Sharable solution-oriented migration API</title>
<version>1.0.0</version>
</info>
<paths>
</anything>
<get>
<summary>Those all evidence respond she listen.</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>
<//anything>
</paths>
</api_specification>

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

Output:
openapi: 3.0.0
info:
  title: Sharable solution-oriented migration API
  version: 1.0.0
paths:
  /anything:
    get:
      summary: Those all evidence respond she listen.
      parameters:
      - name: param0
        in: query
        type: string
      - name: param1
        in: query
        type: string
      responses:
        '200':
          description: Success
        '400':
          description: Bad Request


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

[User]
Transform this JSON data into XML format:
{
  "rx_id": "RX-6036951",
  "patient_mrn": "MRN-440463",
  "prescriber": "Lisa Mathews",
  "date": "2026-01-05",
  "medications": [
    {
      "name": "Metformin",
      "dosage": "20mg",
      "frequency": "TID",
      "quantity": 90
    }
  ]
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<prescription>
<rx_id>RX-6036951</rx_id>
<patient_mrn>MRN-440463</patient_mrn>
<prescriber>Lisa Mathews</prescriber>
<date>2026-01-05</date>
<medications>
<name>Metformin</name>
<dosage>20mg</dosage>
<frequency>TID</frequency>
<quantity>90</quantity>
</medications>
</prescription>


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

[User] Produce a CSV document for a prescription.

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

Output:
date,medications,patient_mrn,prescriber,rx_id
2026-01-03,"[{""name"": ""Atorvastatin"", ""dosage"": ""5mg"", ""frequency"": ""BID"", ""quantity"": 90}, {""name"": ""Atorvastat",MRN-644295,Thomas Ponce,RX-5336793
2026-01-05,"[{""name"": ""Atorvastatin"", ""dosage"": ""20mg"", ""frequency"": ""BID"", ""quantity"": 60}, {""name"": ""Lisinopri",MRN-901215,Mr. Mario Allen,RX-2388578
2026-01-04,"[{""name"": ""Metformin"", ""dosage"": ""20mg"", ""frequency"": ""daily"", ""quantity"": 30}]",MRN-776742,Wendy Miller,RX-9424396


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

[User] Create a JSON representation of api specification.

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

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


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

[User] Create a YAML representation of news article.

[Assistant]
Approach:
1. Task: Create news article 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:
article_id: ART-6846954
headline: Triple-buffered intangible knowledgebase
author: Steven Burgess
published: '2026-01-02T13:52:55.283034'
section: Politics
content: 'Police report arm sense find civil during. New avoid old future quality
  finally bad. Meeting child effect go play issue.

  Thousand security article two color early. Avoid commercial science. Low method
  cultural personal night often.'
tags:
- couple
- specific
- him
views: 35509
shares: 3662


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

[User] Generate sales analytics data in JSON format.

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

Output:
{
  "period": "June 2020",
  "total_revenue": 2603625,
  "units_sold": 51574,
  "channels": [
    {
      "name": "retail",
      "revenue": 1926384,
      "growth": 34.29
    },
    {
      "name": "online",
      "revenue": 1062444,
      "growth": -1.99
    }
  ],
  "top_products": [
    {
      "sku": "SKU-3818",
      "sales": 48786
    },
    {
      "sku": "SKU-7605",
      "sales": 408187
    },
    {
      "sku": "SKU-6728",
      "sales": 223732
    }
  ]
}


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

[User]
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<financial_report>
<company>Rodriguez, Curry and Yates</company>
<ticker>KWAZ</ticker>
<quarter>Q1 2020</quarter>
<revenue>4863925</revenue>
<expenses>55129980</expenses>
<net_income>12179320</net_income>
<eps>7.94</eps>
<metrics>
<profit_margin>29.26</profit_margin>
<roe>9.63</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": "Rodriguez, Curry and Yates",
  "ticker": "KWAZ",
  "quarter": "Q1 2020",
  "revenue": 4863925,
  "expenses": 55129980,
  "net_income": 12179320,
  "eps": 7.94,
  "metrics": {
    "profit_margin": 29.26,
    "roe": 9.63
  }
}


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

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

[Assistant]
Approach:
1. Task: Create research paper in TOML
2. Complexity: 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:
paper_id = "arXiv:2021.48279"
title = "Operative systemic definition"
abstract = "Tv wear teacher under doctor. Eight mention month argue amount how voice."
keywords = [ "month", "southern", "administration",]
citations = 167
[[authors]]
name = "Patricia Owens"
affiliation = "Pearson, Quinn and Owens"
email = "christopher41@example.net"

[[authors]]
name = "Wayne Boyd"
affiliation = "Delacruz-Weaver"
email = "powens@example.net"

[[authors]]
name = "Christopher Castillo"
affiliation = "Lawrence-Caldwell"
email = "amandacarey@example.com"

[publication]
venue = "Cell"
year = 2021
doi = "10.1648/XIrv"


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

[User] Generate api specification data in YAML format.

[Assistant]
Approach:
1. Task: Create api specification in YAML
2. Complexity: 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:
openapi: 3.0.0
info:
  title: Cross-group bottom-line algorithm API
  version: 1.0.0
paths:
  /rule:
    get:
      summary: Center available level environment per away author
      parameters:
      - name: param0
        in: query
        type: string
      - name: param1
        in: query
        type: string
      responses:
        '200':
          description: Success
        '400':
          description: Bad Request


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

[User]
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Reactive exuding frame API</title>
<version>1.0.0</version>
</info>
<paths>
</second>
<get>
<summary>Life century work throughout however miss another.</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//second>
</paths>
</api_specification>

[Assistant]
Approach:
1. Task: Convert api specification 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:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Reactive exuding frame API",
    "version": "1.0.0"
  },
  "paths": {
    "/second": {
      "get": {
        "summary": "Life century work throughout however miss another.",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}


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

[User] Create a YAML representation of product listing.

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

Output:
product_id: PROD-428311
name: Object-based value-added workforce
category: books
price: 802.3
currency: USD
stock: 719
is_available: true
rating: 1.5
reviews: 81
specs:
  weight_kg: 27.85
  dimensions: 99x87x32cm


[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:
{
  "paper_id": "arXiv:2020.59386",
  "title": "Self-enabling demand-driven application",
  "authors": [
    {
      "name": "Keith Wilcox",
      "affiliation": "Ruiz-Torres",
      "email": "martinstephanie@example.org"
    },
    {
      "name": "Jennifer Mccoy",
      "affiliation": "Thompson-Marshall",
      "email": "brianvelasquez@example.org"
    }
  ],
  "abstract": "Before today call network oil future. Admit itself catch song various rest. Personal worry quality director.",
  "keywords": [
    "song",
    "TV",
    "southern"
  ],
  "publication": {
    "venue": "Nature",
    "year": 2020,
    "doi": "10.1369/MikD"
  },
  "citations": 274,
  "funding_source": null
}

[Assistant]
Approach:
1. Task: Convert research paper 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:
paper_id = "arXiv:2020.59386"
title = "Self-enabling demand-driven application"
abstract = "Before today call network oil future. Admit itself catch song various rest. Personal worry quality director."
keywords = [ "song", "TV", "southern",]
citations = 274
[[authors]]
name = "Keith Wilcox"
affiliation = "Ruiz-Torres"
email = "martinstephanie@example.org"

[[authors]]
name = "Jennifer Mccoy"
affiliation = "Thompson-Marshall"
email = "brianvelasquez@example.org"

[publication]
venue = "Nature"
year = 2020
doi = "10.1369/MikD"


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

[User]
Reformat the data below from YAML to CSV:
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 YAML to CSV
2. Complexity: medium - 5-8 fields, 2-3 levels
3. Format rules: header row, comma-separated, quoted fields with commas
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

Output:
abstract,authors,citations,funding_source,info_title,info_version,keywords,openapi,paper_id,paths_/reality_get_parameters,paths_/reality_get_responses_200_description,paths_/reality_get_responses_400_description,paths_/reality_get_summary,publication_doi,publication_venue,publication_year,title
,,,,Intuitive disintermediate website API,1.0.0,,3.0.0,,"[{""name"": ""param0"", ""in"": ""query"", ""type"": ""string""}, {""name"": ""param1"", ""in"": ""query"", ""type"": ""str",Success,Bad Request,Activity public whole paper there relationship tas,,,,
Effect attack before plan human lose. College military not news. Fill understand fine season.,"[{""name"": ""Martin Page"", ""affiliation"": ""Lucas, Gibson and Scott"", ""email"": ""brownalan@example.com""}",161,None,,,"[""miss"", ""reality"", ""his"", ""should"", ""time""]",,arXiv:2021.11331,,,,,10.9181/FRnB,Science,2020,Versatile foreground hardware
"Hand property fear may summer arrive. Trip recent apply condition laugh.
Season religious seat. Inve","[{""name"": ""Steven Reed"", ""affiliation"": ""George-Schmidt"", ""email"": ""tmartinez@example.org""}, {""name""",417,Palmer Group,,,"[""field"", ""any"", ""sit"", ""same"", ""hospital""]",,arXiv:2024.81224,,,,,10.7687/iSLd,Science,2022,Inverse maximized throughput


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

[User] Output lab result as JSON.

[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-2309770",
  "patient_mrn": "MRN-380513",
  "order_date": "2026-01-02",
  "panel": "CMP",
  "results": [
    {
      "test": "Glucose",
      "value": 62.8,
      "unit": "mg/dL",
      "flag": "normal"
    },
    {
      "test": "Hemoglobin",
      "value": 141.2,
      "unit": "mg/dL",
      "flag": "high"
    },
    {
      "test": "WBC",
      "value": 75.4,
      "unit": "g/dL",
      "flag": "low"
    },
    {
      "test": "Glucose",
      "value": 174.6,
      "unit": "g/dL",
      "flag": "low"
    },
    {
      "test": "Glucose",
      "value": 170.1,
      "unit": "g/dL",
      "flag": "low"
    }
  ]
}


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

[User]
Reformat the data below from JSON to XML:
{
  "assessment_id": "ASMT-475777",
  "student_id": "STU-613124",
  "course_id": "CRS-2241",
  "type": "assignment",
  "date": "2026-01-06",
  "scores": [
    {
      "question": 1,
      "points_earned": 8,
      "points_possible": 10
    },
    {
      "question": 2,
      "points_earned": 6,
      "points_possible": 10
    },
    {
      "question": 3,
      "points_earned": 3,
      "points_possible": 10
    },
    {
      "question": 4,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 5,
      "points_earned": 9,
      "points_possible": 10
    },
    {
      "question": 6,
      "points_earned": 7,
      "points_possible": 10
    },
    {
      "question": 7,
      "points_earned": 0,
      "points_possible": 10
    },
    {
      "question": 8,
      "points_earned": 9,
      "points_possible": 10
    },
    {
      "question": 9,
      "points_earned": 3,
      "points_possible": 10
    }
  ],
  "total_score": 75,
  "percentage": 81.54,
  "grade": "B"
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<student_assessment>
<assessment_id>ASMT-475777</assessment_id>
<student_id>STU-613124</student_id>
<course_id>CRS-2241</course_id>
<type>assignment</type>
<date>2026-01-06</date>
<scores>
<question>1</question>
<points_earned>8</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>2</question>
<points_earned>6</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>3</question>
<points_earned>3</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>9</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>6</question>
<points_earned>7</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>7</question>
<points_earned>0</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>8</question>
<points_earned>9</points_earned>
<points_possible>10</points_possible>
</scores>
<scores>
<question>9</question>
<points_earned>3</points_earned>
<points_possible>10</points_possible>
</scores>
<total_score>75</total_score>
<percentage>81.54</percentage>
<grade>B</grade>
</student_assessment>


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

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


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

[User] Produce a CSV document for a 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"": ""wholesale"", ""revenue"": 1234153, ""growth"": 40.64}, {""name"": ""online"", ""revenue"": 991509, """,,,,,November 2022,,,,,"[{""sku"": ""SKU-9585"", ""sales"": 30234}, {""sku"": ""SKU-8072"", ""sales"": 57362}, {""sku"": ""SKU-4011"", ""sale",9138741,89798
Up edge fast appear realize record my style. Approach five state drive example find book high.,"[{""name"": ""Jason Duncan"", ""affiliation"": ""Martinez PLC"", ""email"": ""jhart@example.net""}, {""name"": ""An",,234,Davies Ltd,"[""hair"", ""food"", ""require"", ""task"", ""rate""]",arXiv:2023.42442,,10.9771/AkkV,Science,2021,Re-engineered object-oriented groupware,,,
Student enter thing environment heart. Ready including data program number. Official top smile forme,"[{""name"": ""Jennifer Jensen"", ""affiliation"": ""Cooper and Sons"", ""email"": ""yfisher@example.org""}, {""na",,96,None,"[""local"", ""hot"", ""such"", ""executive"", ""against""]",arXiv:2023.30899,,10.4658/ckbU,Nature,2022,Reverse-engineered systemic workforce,,,


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

[User]
Convert the following JSON to XML:
{
  "company": "Taylor Ltd",
  "ticker": "AOED",
  "quarter": "Q1 2024",
  "revenue": 69752271,
  "expenses": 52626087,
  "net_income": 18580243,
  "eps": 1.63,
  "metrics": {
    "profit_margin": 23.4,
    "roe": 21.22
  }
}

[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>Taylor Ltd</company>
<ticker>AOED</ticker>
<quarter>Q1 2024</quarter>
<revenue>69752271</revenue>
<expenses>52626087</expenses>
<net_income>18580243</net_income>
<eps>1.63</eps>
<metrics>
<profit_margin>23.4</profit_margin>
<roe>21.22</roe>
</metrics>
</financial_report>


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

[User]
Convert the following TOML to YAML:
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 TOML to YAML
2. Complexity: complex - 8-10 fields, 3-4 levels
3. Format rules: consistent indentation, colon-space syntax, hyphen lists
4. Structure: Organize data logically with appropriate nesting
5. Transform values to match the target format specifications.

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


[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": "Re-engineered mobile superstructure API",
    "version": "1.0.0"
  },
  "paths": {
    "/benefit": {
      "get": {
        "summary": "Chair media space recognize doctor would second me",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param2",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}

[Assistant]
Approach:
1. Task: Convert api specification from JSON to XML
2. Complexity: 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>Re-engineered mobile superstructure API</title>
<version>1.0.0</version>
</info>
<paths>
</benefit>
<get>
<summary>Chair media space recognize doctor would second me</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<parameters>
<name>param1</name>
<in>query</in>
<type>string</type>
</parameters>
<parameters>
<name>param2</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//benefit>
</paths>
</api_specification>


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

[User] Output contract as YAML.

[Assistant]
Approach:
1. Task: Create contract in YAML
2. Complexity: 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:
contract_id: CTR-370819
parties:
- name: Stewart, Thompson and Rogers
  role: party_a
- name: Jackson, Griffin and Flowers
  role: party_b
effective_date: '2026-01-01'
term_months: 13
value: 109351
status: active


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

[User] Generate financial report data in YAML format.

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

Output:
company: Thompson LLC
ticker: QQLN
quarter: Q2 2020
revenue: 63838743
expenses: 967762
net_income: 16633381
eps: 0.69
metrics:
  profit_margin: 22.56
  roe: 23.58


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

[User] Output sales analytics as XML.

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<sales_analytics>
<period>June 2021</period>
<total_revenue>4317671</total_revenue>
<units_sold>11582</units_sold>
<channels>
<name>wholesale</name>
<revenue>2780960</revenue>
<growth>22.76</growth>
</channels>
<channels>
<name>retail</name>
<revenue>4140341</revenue>
<growth>-9.84</growth>
</channels>
<top_products>
<sku>SKU-8636</sku>
<sales>261407</sales>
</top_products>
<top_products>
<sku>SKU-9950</sku>
<sales>107242</sales>
</top_products>
<top_products>
<sku>SKU-8311</sku>
<sales>494004</sales>
</top_products>
</sales_analytics>


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

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<authors>
<name>Emily Davis</name>
<affiliation>Nelson, Diaz and Humphrey</affiliation>
<email>jpalmer@example.org</email>
</authors>
<authors>
<name>Robert Clark</name>
<affiliation>James Inc</affiliation>
<email>dennis02@example.net</email>
</authors>
<publication>
<venue>Science</venue>
<year>2022</year>
<doi>10.6797/tlMT</doi>
</publication>
<keywords>lead</keywords>
<keywords>list</keywords>
<keywords>she</keywords>
<funding_source />
<paper_id>arXiv:2022.72917</paper_id>
</research_paper>


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

[User] Create a XML representation of api specification.

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Business-focused zero administration encryption API</title>
<version>1.0.0</version>
</info>
<paths>
</teach>
<get>
<summary>Government trade direction personal reason hundred</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>
<//teach>
</paths>
</api_specification>


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

[User]
Convert the following YAML to JSON:
assessment_id: ASMT-744456
student_id: STU-954920
course_id: CRS-3021
type: exam
date: '2026-01-03'
scores:
- question: 1
  points_earned: 7
  points_possible: 10
- question: 2
  points_earned: 2
  points_possible: 10
- question: 3
  points_earned: 2
  points_possible: 10
- question: 4
  points_earned: 9
  points_possible: 10
- question: 5
  points_earned: 5
  points_possible: 10
- question: 6
  points_earned: 10
  points_possible: 10
- question: 7
  points_earned: 5
  points_possible: 10
- question: 8
  points_earned: 1
  points_possible: 10
- question: 9
  points_earned: 9
  points_possible: 10
- question: 10
  points_earned: 3
  points_possible: 10
- question: 11
  points_earned: 9
  points_possible: 10
- question: 12
  points_earned: 9
  points_possible: 10
total_score: 97
percentage: 89.67
grade: C

[Assistant]
Approach:
1. Task: Convert student assessment from YAML 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:
{
  "assessment_id": "ASMT-744456",
  "student_id": "STU-954920",
  "course_id": "CRS-3021",
  "type": "exam",
  "date": "2026-01-03",
  "scores": [
    {
      "question": 1,
      "points_earned": 7,
      "points_possible": 10
    },
    {
      "question": 2,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 3,
      "points_earned": 2,
      "points_possible": 10
    },
    {
      "question": 4,
      "points_earned": 9,
      "points_possible": 10
    },
    {
      "question": 5,
      "points_earned": 5,
      "points_possible": 10
    },
    {
      "question": 6,
      "points_earned": 10,
      "points_possible": 10
    },
    {
      "question": 7,
      "points_earned": 5,
      "points_possible": 10
    },
    {
      "question": 8,
      "points_earned": 1,
      "points_possible": 10
    },
    {
      "question": 9,
      "points_earned": 9,
      "points_possible": 10
    },
    {
      "question": 10,
      "points_earned": 3,
      "points_possible": 10
    },
    {
      "question": 11,
      "points_earned": 9,
      "points_possible": 10
    },
    {
      "question": 12,
      "points_earned": 9,
      "points_possible": 10
    }
  ],
  "total_score": 97,
  "percentage": 89.67,
  "grade": "C"
}


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

[User] Output clinical note as TOML.

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

Output:
note_id = "CN-5754690"
encounter_date = "2026-01-05"
chief_complaint = "fever"
[[assessment]]
problem = "diabetes"
icd10 = "K80"

[patient]
mrn = "MRN-521303"
age = 32
gender = "M"

[vitals]
bp = "101/104"
hr = 85
temp_f = 99.3


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

[User]
Convert the following JSON to XML:
{
  "txn_id": "TXN-23430167",
  "customer_id": "7fb2e914-3f0f-4c3f-abb9-ef22ed2c1064",
  "timestamp": "2026-01-07T13:51:26.046328",
  "items": [
    {
      "sku": "SKU-63492",
      "qty": 1,
      "price": 90.17
    },
    {
      "sku": "SKU-56350",
      "qty": 5,
      "price": 336.79
    }
  ],
  "subtotal": 152.9,
  "tax": 14.6,
  "total": 796.85,
  "payment_method": "apple_pay"
}

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<transaction_record>
<txn_id>TXN-23430167</txn_id>
<customer_id>7fb2e914-3f0f-4c3f-abb9-ef22ed2c1064</customer_id>
<timestamp>2026-01-07T13:51:26.046328</timestamp>
<items>
<sku>SKU-63492</sku>
<qty>1</qty>
<price>90.17</price>
</items>
<items>
<sku>SKU-56350</sku>
<qty>5</qty>
<price>336.79</price>
</items>
<subtotal>152.9</subtotal>
<tax>14.6</tax>
<total>796.85</total>
<payment_method>apple_pay</payment_method>
</transaction_record>


[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:2020.93852</paper_id>
<title>Reactive solution-oriented circuit</title>
<authors>
<name>Jennifer Gray</name>
<affiliation>Bryant, Lewis and Wells</affiliation>
<email>spalmer@example.com</email>
</authors>
<authors>
<name>David Brown</name>
<affiliation>Cortez, Cook and Ross</affiliation>
<email>melvin21@example.com</email>
</authors>
<abstract>Law fund huge better or. Federal forward north law. Work available call never.
Carry cultural day front resource write. Southern white pattern fear.</abstract>
<keywords>wind</keywords>
<keywords>wife</keywords>
<keywords>report</keywords>
<keywords>financial</keywords>
<publication>
<venue>Cell</venue>
<year>2023</year>
<doi>10.1277/DPuH</doi>
</publication>
<citations>45</citations>
<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:2020.93852",
  "title": "Reactive solution-oriented circuit",
  "authors": [
    {
      "name": "Jennifer Gray",
      "affiliation": "Bryant, Lewis and Wells",
      "email": "spalmer@example.com"
    },
    {
      "name": "David Brown",
      "affiliation": "Cortez, Cook and Ross",
      "email": "melvin21@example.com"
    }
  ],
  "abstract": "Law fund huge better or. Federal forward north law. Work available call never.\nCarry cultural day front resource write. Southern white pattern fear.",
  "keywords": [
    "wind",
    "wife",
    "report",
    "financial"
  ],
  "publication": {
    "venue": "Cell",
    "year": 2023,
    "doi": "10.1277/DPuH"
  },
  "citations": 45,
  "funding_source": null
}


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

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

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<research_paper>
<paper_id>arXiv:2022.73738</paper_id>
<title>Switchable maximized Local Area Network</title>
<authors>
<name>Heather Lee</name>
<affiliation>Garcia, Ellison and Kim</affiliation>
<email>kimberlysimpson@example.com</email>
</authors>
<authors>
<name>Jeremy Gonzalez</name>
<affiliation>Wilson, Sanchez and Copeland</affiliation>
<email>michelle83@example.com</email>
</authors>
<authors>
<name>Brianna Hart</name>
<affiliation>Shannon, Tran and Taylor</affiliation>
<email>penatyler@example.net</email>
</authors>
<abstract>List son shake understand food. Up no police friend factor. Support company yes push argue.</abstract>
<keywords>fact</keywords>
<keywords>guess</keywords>
<keywords>truth</keywords>
<publication>
<venue>Cell</venue>
<year>2024</year>
<doi>10.7028/ttmb</doi>
</publication>
<citations>36</citations>
<funding_source>Guerra, Richards and Schaefer</funding_source>
</research_paper>


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

[User] Output customer review as YAML.

[Assistant]
Approach:
1. Task: Create customer review in YAML
2. Complexity: 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:
review_id: REV-2575466
product_id: PROD-346187
user_id: 320eb87e-12bd-44ab-bb47-6fec45bd5144
rating: 1
title: 'Possible modern last rate memory fight conference '
content: 'Character walk loss rock me social gun.

  Center choice either push. Push stop yourself.'
date: '2026-01-01'
verified_purchase: false
helpful_votes: 26


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

[User] Create a JSON representation of product listing.

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

Output:
{
  "product_id": "PROD-723394",
  "name": "Streamlined full-range ability",
  "category": "clothing",
  "price": 959.9,
  "currency": "USD",
  "stock": 28,
  "is_available": true,
  "rating": 3.7,
  "reviews": 332,
  "specs": {
    "weight_kg": 9.93,
    "dimensions": "53x67x45cm"
  }
}


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

[User]
Convert the following XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>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>

[Assistant]
Approach:
1. Task: Convert api specification 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:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Distributed high-level website API",
    "version": "1.0.0"
  },
  "paths": {
    "/next": {
      "get": {
        "summary": "Movie my movie common adult.",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}


[System] You are an expert in 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-4164</course_id>
RVR286
<title>Team-oriented incremental info-mediaries 101</title>
<instructor>Shannon Miller</instructor>
<credits>3</credits>
<term>Fall 2023</term>
<schedule>
<week>1</week>
<topic>stuff</topic>
</schedule>
<schedule>
<week>2</week>
<topic>professional</topic>
</schedule>
<schedule>
<week>3</week>
<topic>hard</topic>
</schedule>
<schedule>
<week>4</week>
<topic>rather</topic>
</schedule>
<schedule>
<week>5</week>
<topic>lawyer</topic>
</schedule>
<schedule>
<week>6</week>
<topic>camera</topic>
</schedule>
<schedule>
<week>7</week>
<topic>focus</topic>
</schedule>
<schedule>
<week>8</week>
<topic>spend</topic>
</schedule>
<schedule>
<week>9</week>
<topic>couple</topic>
</schedule>
<schedule>
<week>10</week>
<topic>quickly</topic>
</schedule>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
</course_syllabus>

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

Output:
{
  "course_id": "CRS-4164",
  "code": "RVR286",
  "title": "Team-oriented incremental info-mediaries 101",
  "instructor": "Shannon Miller",
  "credits": 3,
  "term": "Fall 2023",
  "schedule": [
    {
      "week": 1,
      "topic": "stuff"
    },
    {
      "week": 2,
      "topic": "professional"
    },
    {
      "week": 3,
      "topic": "hard"
    },
    {
      "week": 4,
      "topic": "rather"
    },
    {
      "week": 5,
      "topic": "lawyer"
    },
    {
      "week": 6,
      "topic": "camera"
    },
    {
      "week": 7,
      "topic": "focus"
    },
    {
      "week": 8,
      "topic": "spend"
    },
    {
      "week": 9,
      "topic": "couple"
    },
    {
      "week": 10,
      "topic": "quickly"
    }
  ],
  "grading": {
    "homework": 30,
    "midterm": 30,
    "final": 40
  }
}


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

[User] Create a CSV representation of 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
VMZ479,CRS-4765,4,40,30,30,Amy Baker,"[{""week"": 1, ""topic"": ""show""}, {""week"": 2, ""topic"": ""cut""}, {""week"": 3, ""topic"": ""next""}, {""week"": 4",Fall 2022,Exclusive grid-enabled software 101
CNK275,CRS-8724,3,40,30,30,Dustin Beck,"[{""week"": 1, ""topic"": ""point""}, {""week"": 2, ""topic"": ""model""}, {""week"": 3, ""topic"": ""house""}, {""week",Fall 2021,Multi-channeled client-server data-warehouse 101
QZT211,CRS-1058,4,40,30,30,Michelle Smith,"[{""week"": 1, ""topic"": ""statement""}, {""week"": 2, ""topic"": ""money""}, {""week"": 3, ""topic"": ""arm""}, {""we",Fall 2020,Optimized asymmetric Internet solution 101


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

[User] Output lab result as XML.

[Assistant]
Approach:
1. Task: Create lab result in XML
2. Complexity: 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-5387789</result_id>
<patient_mrn>MRN-887521</patient_mrn>
<order_date>2026-01-05</order_date>
<panel>CBC</panel>
<results>
<test>WBC</test>
<value>66.6</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
<results>
<test>Glucose</test>
<value>111.4</value>
<unit>mg/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>168.1</value>
<unit>g/dL</unit>
<flag>high</flag>
</results>
<results>
<test>Hemoglobin</test>
<value>136.7</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
<results>
<test>WBC</test>
<value>148.7</value>
<unit>g/dL</unit>
<flag>low</flag>
</results>
<results>
<test>Glucose</test>
<value>86.9</value>
<unit>mg/dL</unit>
<flag>normal</flag>
</results>
</lab_result>


[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"?>
<product_listing>
<category>electronics</category>
<specs>
<weight_kg>38.59</weight_kg>
<dimensions>23x92x45cm</dimensions>
</specs>
<stock>596</stock>
<price>218.58</price>
</product_listing>

[Assistant]
Approach:
1. Task: Convert product listing 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:
{
  "category": "electronics",
  "specs": {
    "weight_kg": 38.59,
    "dimensions": "23x92x45cm"
  },
  "stock": 596,
  "price": 218.58
}


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

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

[Assistant]
Approach:
1. Task: Create student assessment in YAML
2. Complexity: 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:
course_id: CRS-9368
percentage: 68.59
assessment_id: ASMT-453812
scores:
- question: 1
  points_earned: 2
  points_possible: 10
- question: 2
  points_earned: 3
  points_possible: 10
- question: 3
  points_earned: 0
  points_possible: 10
- question: 4
  points_earned: 4
  points_possible: 10
- question: 5
  points_earned: 6
  points_possible: 10
- question: 6
  points_earned: 9
  points_possible: 10
- question: 7
  points_earned: 4
  points_possible: 10
- question: 8
  points_earned: 8
  points_possible: 10
- question: 9
  points_earned: 5
  points_possible: 10
- question: 10
  points_earned: 0
  points_possible: 10
- question: 11
  points_earned: 2
  points_possible: 10


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

[User] Output financial report as XML.

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<financial_report>
<company>Snow, Shelton and Parsons</company>
<ticker>LYEH</ticker>
<quarter>Q3 2022</quarter>
<revenue>49988929</revenue>
<expenses>3428077</expenses>
<net_income>8543670</net_income>
<eps>3.41</eps>
<metrics>
<profit_margin>11.21</profit_margin>
<roe>5.99</roe>
</metrics>
</financial_report>


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

[User] Output student assessment as YAML.

[Assistant]
Approach:
1. Task: Create student assessment in YAML
2. Complexity: 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:
assessment_id: ASMT-458464
student_id: STU-453066
course_id: CRS-7675
type: assignment
date: '2026-01-06'
scores:
- question: 1
  points_earned: 0
  points_possible: 10
- question: 2
  points_earned: 9
  points_possible: 10
- question: 3
  points_earned: 2
  points_possible: 10
- question: 4
  points_earned: 4
  points_possible: 10
- question: 5
  points_earned: 4
  points_possible: 10
- question: 6
  points_earned: 0
  points_possible: 10
- question: 7
  points_earned: 3
  points_possible: 10
- question: 8
  points_earned: 7
  points_possible: 10
- question: 9
  points_earned: 8
  points_possible: 10
total_score: 67
percentage: 65.79
grade: B


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

[User] Produce a TOML document for a error log.

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

Output:
error_id = "bcec7cd1-70fc-42ba-97dd-2c6e2159fc7d"
timestamp = "2026-01-07T13:51:27.288021"
level = "CRITICAL"
service = "reasonService"
message = "Recent security meet three Congress find seat."
stack_trace = [ "at current.py:236", "at your.py:146", "at without.py:194",]

[context]
user_id = "fc408ea4-9df4-4d81-87da-9d63d4bc8744"
request_id = "d8c95012-b6bb-42d7-8cb4-e57e77353a5b"


[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>
<quarter>Q3 2022</quarter>
<company>Dunn-Byrd</company>
<expenses>58548919</expenses>
<eps>9.56</eps>
<ticker>ATGQ</ticker>
</financial_report>


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

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

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<course_syllabus>
<course_id>CRS-9456</course_id>
KDS432
<title>Multi-channeled local complexity 101</title>
<instructor>Kenneth Rogers</instructor>
<credits>3</credits>
<term>Fall 2020</term>
<schedule>
<week>1</week>
<topic>activity</topic>
</schedule>
<schedule>
<week>2</week>
<topic>foot</topic>
</schedule>
<schedule>
<week>3</week>
<topic>reason</topic>
</schedule>
<schedule>
<week>4</week>
<topic>rule</topic>
</schedule>
<schedule>
<week>5</week>
<topic>paper</topic>
</schedule>
<schedule>
<week>6</week>
<topic>current</topic>
</schedule>
<schedule>
<week>7</week>
<topic>scene</topic>
</schedule>
<schedule>
<week>8</week>
<topic>later</topic>
</schedule>
<schedule>
<week>9</week>
<topic>choice</topic>
</schedule>
<schedule>
<week>10</week>
<topic>box</topic>
</schedule>
<grading>
<homework>30</homework>
<midterm>30</midterm>
<final>40</final>
</grading>
</course_syllabus>


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

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

[Assistant]
Approach:
1. Task: Create student assessment 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:
assessment_id,code,course_id,credits,date,grade,grading_final,grading_homework,grading_midterm,instructor,percentage,schedule,scores,student_id,term,title,total_score,type
ASMT-554535,,CRS-9992,,2026-01-03,B,,,,,63.99,,"[{""question"": 1, ""points_earned"": 9, ""points_possible"": 10}, {""question"": 2, ""points_earned"": 6, ""po",STU-693793,,,86,exam
,ROE204,CRS-5810,3,,,40,30,30,Tyler Rogers,,"[{""week"": 1, ""topic"": ""every""}, {""week"": 2, ""topic"": ""imagine""}, {""week"": 3, ""topic"": ""for""}, {""week",,,Fall 2024,Balanced intangible policy 101,,
,OKZ405,CRS-9934,4,,,40,30,30,Michael Cannon,,"[{""week"": 1, ""topic"": ""report""}, {""week"": 2, ""topic"": ""street""}, {""week"": 3, ""topic"": ""modern""}, {""w",,,Fall 2022,Multi-tiered dynamic function 101,,


[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"?>
<sales_analytics>
<period>May 2020</period>
<total_revenue>9864225</total_revenue>
<units_sold>74086</units_sold>
<channels>
<name>online</name>
<revenue>906832</revenue>
<growth>-8.93</growth>
</channels>
<channels>
<name>wholesale</name>
<revenue>2437365</revenue>
<growth>2.73</growth>
</channels>
<top_products>
<sku>SKU-7032</sku>
<sales>420063</sales>
</top_products>
<top_products>
<sku>SKU-9360</sku>
<sales>149398</sales>
</top_products>
<top_products>
<sku>SKU-9440</sku>
<sales>105905</sales>
</top_products>
</sales_analytics>

[Assistant]
Approach:
1. Task: Convert sales analytics 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:
{
  "period": "May 2020",
  "total_revenue": 9864225,
  "units_sold": 74086,
  "channels": [
    {
      "name": "online",
      "revenue": 906832,
      "growth": -8.93
    },
    {
      "name": "wholesale",
      "revenue": 2437365,
      "growth": 2.73
    }
  ],
  "top_products": [
    {
      "sku": "SKU-7032",
      "sales": 420063
    },
    {
      "sku": "SKU-9360",
      "sales": 149398
    },
    {
      "sku": "SKU-9440",
      "sales": 105905
    }
  ]
}


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

[User] Output course syllabus as JSON.

[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-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 XML format. Think step-by-step, then generate syntactically perfect XML.

[User] Create a XML representation of product listing.

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<product_listing>
<product_id>PROD-428311</product_id>
<name>Object-based value-added workforce</name>
<category>books</category>
<price>802.3</price>
<currency>USD</currency>
<stock>719</stock>
<is_available>True</is_available>
<rating>1.5</rating>
<reviews>81</reviews>
<specs>
<weight_kg>27.85</weight_kg>
<dimensions>99x87x32cm</dimensions>
</specs>
</product_listing>


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

[User] Generate news article data in XML format.

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<news_article>
<article_id>ART-6180455</article_id>
<headline>Grass-roots multi-tasking hub</headline>
<author>David Espinoza</author>
<published>2026-01-07T13:20:10.771283</published>

Politics

<content>Either large lot east. Show everybody away city election happy my. Believe left sure mother.
Whom game determine road little. Sing this character. Agent fill kitchen themselves agreement.
Woman draw budget stage. Star cultural old president where national success.</content>
<tags>size</tags>
<tags>commercial</tags>
<tags>president</tags>
<tags>city</tags>
<tags>expect</tags>
<views>43396</views>
<shares>2564</shares>
</news_article>


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

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

[Assistant]
Approach:
1. Task: Create customer review 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:
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
,"Guy generation provide economy test bit. Page cost and.
Arm test ok green. Likely card reality schoo",,2026-01-06,22,,,,PROD-108019,4,REV-8549692,,,,,Development know write believe teacher ability.,a4c4fbe3-7a0e-49f5-b14b-2ab1ca2d6ed5,True
clothing,,USD,,,True,Polarized user-facing architecture,414.88,PROD-678583,4.52,,226,47x93x39cm,3.38,297,,,
electronics,,USD,,,True,Customer-focused object-oriented forecast,120.22,PROD-271762,4.99,,555,83x89x17cm,28.94,608,,,
clothing,,USD,,,True,Switchable leadingedge intranet,618.55,PROD-615699,1.28,,86,74x74x55cm,20.88,549,,,


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

[User] Create a TOML representation of product listing.

[Assistant]
Approach:
1. Task: Create product listing in TOML
2. Complexity: 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:
product_id = "PROD-110536"
name = "Organized didactic parallelism"
category = "clothing"
price = 68.12
currency = "USD"
stock = 153
is_available = true
rating = 1.45
reviews = 277

[specs]
weight_kg = 1.85
dimensions = "33x70x14cm"


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

[User] Create a JSON representation of customer review.

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

Output:
{
  "review_id": "REV-9546377",
  "product_id": "PROD-108034",
  "user_id": "d01ac4e1-ccd9-4273-9fe0-9ca6afc6af77",
  "rating": 4,
  "title": "Appear speak sure list.",
  "content": "Today offer none role certain reach. Second Mr official enjoy movement turn city. Name employee early much first sit.",
  "date": "2026-01-01",
  "verified_purchase": true,
  "helpful_votes": 43
}


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

[User] Create a TOML representation of clinical note.

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

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

[patient]
mrn = "MRN-895859"
age = 79
gender = "M"

[vitals]
bp = "127/81"
hr = 117
temp_f = 102.4


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

[User] Output sales analytics as TOML.

[Assistant]
Approach:
1. Task: Create sales analytics 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:
period = "June 2020"
total_revenue = 2603625
units_sold = 51574
[[channels]]
name = "retail"
revenue = 1926384
growth = 34.29

[[channels]]
name = "online"
revenue = 1062444
growth = -1.99

[[top_products]]
sku = "SKU-3818"
sales = 48786

[[top_products]]
sku = "SKU-7605"
sales = 408187

[[top_products]]
sku = "SKU-6728"
sales = 223732


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

[User] Create a YAML representation of course syllabus.

[Assistant]
Approach:
1. Task: Create course syllabus in YAML
2. Complexity: 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:
course_id: CRS-4164
code: RVR286
title: Team-oriented incremental info-mediaries 101
instructor: Shannon Miller
credits: 3
term: Fall 2023
schedule:
- week: 1
  topic: stuff
- week: 2
  topic: professional
- week: 3
  topic: hard
- week: 4
  topic: rather
- week: 5
  topic: lawyer
- week: 6
  topic: camera
- week: 7
  topic: focus
- week: 8
  topic: spend
- week: 9
  topic: couple
- week: 10
  topic: quickly
grading:
  homework: 30
  midterm: 30
  final: 40


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

[User] Output clinical note as YAML.

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

Output:
note_id: CN-8293808
patient:
  mrn: MRN-980604
  age: 24
  gender: F
encounter_date: '2026-01-05'
chief_complaint: fever
vitals:
  bp: 150/98
  hr: 93
  temp_f: 102.4
assessment:
- problem: diabetes
  icd10: J39


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

[User] Output api specification as XML.

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<paths>
</sense>
<get>
<summary>Pay yes agree executive year ahead program.</summary>
<parameters>
<name>param0</name>
<in>query</in>
<type>string</type>
</parameters>
<responses>
<200>
<description>Success</description>
</200>
<400>
<description>Bad Request</description>
</400>
</responses>
</get>
<//sense>
</paths>
<info>
<title>Customer-focused zero-defect array API</title>
<version>1.0.0</version>
</info>
</api_specification>


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

[User] Create a JSON representation of social media post.

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


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

[User]
Reformat the data below from XML to JSON:
<?xml version="1.0" encoding="UTF-8"?>
<api_specification>
<openapi>3.0.0</openapi>
<info>
<title>Organic analyzing strategy API</title>
<version>1.0.0</version>
</info>
<paths>
</similar>
<get>
<summary>Natural see lot recently.</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>
<//similar>
</paths>
</api_specification>

[Assistant]
Approach:
1. Task: Convert api specification 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:
{
  "openapi": "3.0.0",
  "info": {
    "title": "Organic analyzing strategy API",
    "version": "1.0.0"
  },
  "paths": {
    "/similar": {
      "get": {
        "summary": "Natural see lot recently.",
        "parameters": [
          {
            "name": "param0",
            "in": "query",
            "type": "string"
          },
          {
            "name": "param1",
            "in": "query",
            "type": "string"
          }
        ],
        "responses": {
          "200": {
            "description": "Success"
          },
          "400": {
            "description": "Bad Request"
          }
        }
      }
    }
  }
}


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

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

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

Output:
note_id: CN-5751204
patient:
  mrn: MRN-566004
  age: 47
  gender: M
encounter_date: '2026-01-05'
chief_complaint: headache
vitals:
  bp: 160/96
  hr: 75
  temp_f: 102.4
assessment:
- problem: diabetes
  icd10: I93


[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"?>
<product_listing>
<product_id>PROD-308726</product_id>
<name>Cross-platform client-server attitude</name>
<category>electronics</category>
<price>875.12</price>
<currency>USD</currency>
<stock>161</stock>
<is_available>True</is_available>
<rating>1.18</rating>
<reviews>705</reviews>
<specs>
<weight_kg>37.34</weight_kg>
<dimensions>78x81x41cm</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-308726",
  "name": "Cross-platform client-server attitude",
  "category": "electronics",
  "price": 875.12,
  "currency": "USD",
  "stock": 161,
  "is_available": true,
  "rating": 1.18,
  "reviews": 705,
  "specs": {
    "weight_kg": 37.34,
    "dimensions": "78x81x41cm"
  }
}


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

[User]
Transform this YAML data into TOML format:
company: Smith-Glover
ticker: JROI
quarter: Q3 2023
revenue: 95238846
expenses: 30652579
net_income: 5856951
eps: 7.31
metrics:
  profit_margin: 9.94
  roe: 10.91

[Assistant]
Approach:
1. Task: Convert financial report from YAML 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:
company = "Smith-Glover"
ticker = "JROI"
quarter = "Q3 2023"
revenue = 95238846
expenses = 30652579
net_income = 5856951
eps = 7.31

[metrics]
profit_margin = 9.94
roe = 10.91


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

[User] Output course syllabus as YAML.

[Assistant]
Approach:
1. Task: Create course syllabus 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:
course_id: CRS-1689
code: NZW166
title: Operative modular system engine 101
instructor: David Chen
credits: 4
term: Fall 2021
schedule:
- week: 1
  topic: in
- week: 2
  topic: summer
- week: 3
  topic: unit
- week: 4
  topic: wind
- week: 5
  topic: act
- week: 6
  topic: itself
- week: 7
  topic: would
- week: 8
  topic: itself
- week: 9
  topic: tell
- week: 10
  topic: money
- week: 11
  topic: long
grading:
  homework: 30
  midterm: 30
  final: 40


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

[User]
Reformat the data below from CSV to YAML:
conclusion,experiment_id,methodology_design,methodology_duration_days,methodology_sample_size,results,title
significant,EXP-725280,observational,166,907,"[{""metric"": ""safety"", ""baseline"": 43.19, ""endpoint"": 64.81, ""p_value"": 0.4813}, {""metric"": ""safety"",",Effect of city on expert
significant,EXP-576786,RCT,123,209,"[{""metric"": ""safety"", ""baseline"": 41.98, ""endpoint"": 25.74, ""p_value"": 0.3385}, {""metric"": ""efficacy",Effect of meeting on pay
significant,EXP-737752,RCT,62,928,"[{""metric"": ""safety"", ""baseline"": 93.07, ""endpoint"": 53.57, ""p_value"": 0.0785}, {""metric"": ""efficacy",Effect of reality on level

[Assistant]
Approach:
1. Task: Convert experiment result from CSV 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:
experiment_id: EXP-725280
title: Effect of city on expert
methodology:
  design: observational
  sample_size: 907
  duration_days: 166
results:
- metric: safety
  baseline: 43.19
  endpoint: 64.81
  p_value: 0.4813
- metric: safety
  baseline: 71.73
  endpoint: 68.14
  p_value: 0.0851
- metric: safety
  baseline: 77.12
  endpoint: 63.9
  p_value: 0.1154
conclusion: significant


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

[User] Generate financial report data in JSON format.

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


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

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

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

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


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

[User] Generate prescription data in CSV format.

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

Output:
date,medications,patient_mrn,prescriber,rx_id
2026-01-06,"[{""name"": ""Atorvastatin"", ""dosage"": ""10mg"", ""frequency"": ""daily"", ""quantity"": 60}]",MRN-972429,Matthew Bennett,RX-3472120
2026-01-06,"[{""name"": ""Metformin"", ""dosage"": ""5mg"", ""frequency"": ""TID"", ""quantity"": 30}, {""name"": ""Metformin"", """,MRN-890041,Mr. Mark King,RX-2242464
2026-01-02,"[{""name"": ""Lisinopril"", ""dosage"": ""20mg"", ""frequency"": ""BID"", ""quantity"": 60}]",MRN-840995,Susan Oneill,RX-6955336
2026-01-04,"[{""name"": ""Lisinopril"", ""dosage"": ""5mg"", ""frequency"": ""BID"", ""quantity"": 60}]",MRN-252329,Michele Hines,RX-7123019


[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"?>
<social_media_post>
<engagement>
<likes>6676</likes>
<shares>196</shares>
<comments>84</comments>
</engagement>
<username>nicholasalvarez</username>
<post_id>POST-61351209</post_id>
<hashtags>#pretty</hashtags>
<hashtags>#admit</hashtags>
<hashtags>#available</hashtags>
<user_id>5e546096-8461-4a3f-84e6-813e9e89a39c</user_id>
</social_media_post>

[Assistant]
Approach:
1. Task: Convert social media post 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:
{
  "engagement": {
    "likes": 6676,
    "shares": 196,
    "comments": 84
  },
  "username": "nicholasalvarez",
  "post_id": "POST-61351209",
  "hashtags": [
    "#pretty",
    "#admit",
    "#available"
  ],
  "user_id": "5e546096-8461-4a3f-84e6-813e9e89a39c"
}


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

[User] Generate sales analytics data in XML format.

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

Output:
<?xml version="1.0" encoding="UTF-8"?>
<sales_analytics>
<period>November 2021</period>
<total_revenue>8992427</total_revenue>
<units_sold>30636</units_sold>
<channels>
<name>wholesale</name>
<revenue>3169564</revenue>
<growth>42.35</growth>
</channels>
<channels>
<name>retail</name>
<revenue>2683860</revenue>
<growth>36.55</growth>
</channels>
<top_products>
<sku>SKU-9614</sku>
<sales>412171</sales>
</top_products>
<top_products>
<sku>SKU-7573</sku>
<sales>203488</sales>
</top_products>
<top_products>
<sku>SKU-4372</sku>
<sales>55896</sales>
</top_products>
</sales_analytics>