Datasets:
id string | instruction string | response string | messages list | domain string | source string | mode string | naturalness_judge int64 | version string |
|---|---|---|---|---|---|---|---|---|
v2-00000 | Rewrite this Slack message to be casual and direct:
'Please be advised that the weekly sync has been rescheduled to tomorrow at 10 AM. Your presence would be highly appreciated. Let me know if this presents any scheduling conflicts.' | Hey, we've moved the weekly sync to tomorrow at 10 AM. Hope you can make it—let me know if that doesn't work for you. | [
{
"content": "Rewrite this Slack message to be casual and direct:\n\n'Please be advised that the weekly sync has been rescheduled to tomorrow at 10 AM. Your presence would be highly appreciated. Let me know if this presents any scheduling conflicts.'",
"role": "user"
},
{
"content": "Hey, we've move... | chat | curated | 5 | v2 | |
v2-00001 | Rewrite this robotic update for our team channel:
'I am pleased to announce that we have successfully resolved the authentication bug. The fix is currently live in production. We will continue to monitor performance parameters.' | We've fixed the authentication bug and the update's live in production. We're keeping an eye on performance now. | [
{
"content": "Rewrite this robotic update for our team channel:\n\n'I am pleased to announce that we have successfully resolved the authentication bug. The fix is currently live in production. We will continue to monitor performance parameters.'",
"role": "user"
},
{
"content": "We've fixed the auth... | chat | curated | 5 | v2 | |
v2-00002 | Rewrite this Slack message draft:
'It has come to my attention that the API endpoints are experiencing elevated latency. I am actively investigating the root cause and will keep you informed of further developments.' | I've noticed some elevated latency on the API endpoints. I'm looking into it now and will share updates as I find them. | [
{
"content": "Rewrite this Slack message draft:\n\n'It has come to my attention that the API endpoints are experiencing elevated latency. I am actively investigating the root cause and will keep you informed of further developments.'",
"role": "user"
},
{
"content": "I've noticed some elevated laten... | chat | curated | 5 | v2 | |
v2-00003 | This sounds too formal. Fix it for Slack:
'Hi team, I would like to request that everyone submit their weekly reports by the close of business today to facilitate project tracking. Thank you in advance for your prompt attention.' | Hey team, please get your weekly reports in by EOD today so we can keep track of our project progress. Thanks! | [
{
"content": "This sounds too formal. Fix it for Slack:\n\n'Hi team, I would like to request that everyone submit their weekly reports by the close of business today to facilitate project tracking. Thank you in advance for your prompt attention.'",
"role": "user"
},
{
"content": "Hey team, please ge... | chat | curated | 5 | v2 | |
v2-00004 | Clean up this reply to a colleague's question about the database schemas:
'In response to your query regarding the schema structure, it is worth noting that we have deprecated the legacy user_meta table. Furthermore, all active columns have been migrated to user_profiles.' | We've deprecated the legacy user_meta table. All active columns have been migrated to user_profiles. | [
{
"content": "Clean up this reply to a colleague's question about the database schemas:\n\n'In response to your query regarding the schema structure, it is worth noting that we have deprecated the legacy user_meta table. Furthermore, all active columns have been migrated to user_profiles.'",
"role": "user"
... | general | curated | 5 | v2 | |
v2-00005 | Draft a quick Slack message to my manager asking if they have 5 minutes to chat about career growth this afternoon. | Hi [Manager Name], do you have 5 minutes to chat about career growth this afternoon? | [
{
"content": "Draft a quick Slack message to my manager asking if they have 5 minutes to chat about career growth this afternoon.",
"role": "user"
},
{
"content": "Hi [Manager Name], do you have 5 minutes to chat about career growth this afternoon?",
"role": "assistant"
}
] | chat | curated | 5 | v2 | |
v2-00006 | Write a Slack message to the team apologizing for breaking the staging environment and explaining that I am rolling it back now. | Hey team, I'm sorry for breaking the staging environment. I'm rolling it back now. | [
{
"content": "Write a Slack message to the team apologizing for breaking the staging environment and explaining that I am rolling it back now.",
"role": "user"
},
{
"content": "Hey team, I'm sorry for breaking the staging environment. I'm rolling it back now.",
"role": "assistant"
}
] | chat | curated | 5 | v2 | |
v2-00007 | Write a quick ping to a peer PM asking if they've reviewed the PRD for the billing page yet. | Hey, have you had a chance to look over the PRD for the billing page yet? | [
{
"content": "Write a quick ping to a peer PM asking if they've reviewed the PRD for the billing page yet.",
"role": "user"
},
{
"content": "Hey, have you had a chance to look over the PRD for the billing page yet?",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00008 | Ask a colleague in a DM if they want to grab lunch or coffee around 12:30 PM. | Hey, are you free to grab lunch or coffee around 12:30 PM today? | [
{
"content": "Ask a colleague in a DM if they want to grab lunch or coffee around 12:30 PM.",
"role": "user"
},
{
"content": "Hey, are you free to grab lunch or coffee around 12:30 PM today?",
"role": "assistant"
}
] | chat | curated | 5 | v2 | |
v2-00009 | Write a message for the #general channel letting everyone know there are leftover donuts in the kitchen. | There are leftover donuts in the kitchen. Help yourself before they're gone! | [
{
"content": "Write a message for the #general channel letting everyone know there are leftover donuts in the kitchen.",
"role": "user"
},
{
"content": "There are leftover donuts in the kitchen. Help yourself before they're gone!",
"role": "assistant"
}
] | chat | curated | 5 | v2 | |
v2-00010 | Rewrite: 'Should you require additional documentation, please do not hesitate to reach out.' | Let me know if you need more documentation. | [
{
"content": "Rewrite: 'Should you require additional documentation, please do not hesitate to reach out.'",
"role": "user"
},
{
"content": "Let me know if you need more documentation.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00011 | Rewrite: 'I would like to extend my gratitude for your support during the migration process.' | Thanks for your support during the migration. | [
{
"content": "Rewrite: 'I would like to extend my gratitude for your support during the migration process.'",
"role": "user"
},
{
"content": "Thanks for your support during the migration.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00012 | Rewrite: 'It is recommended that we verify the results before proceeding with the production release.' | Let's verify the results before we push to production. | [
{
"content": "Rewrite: 'It is recommended that we verify the results before proceeding with the production release.'",
"role": "user"
},
{
"content": "Let's verify the results before we push to production.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00013 | Draft a Slack update letting the customer support team know that the payment gateway is fully restored. | The payment gateway is back up and running. Everything is fully restored, so we're good to go. | [
{
"content": "Draft a Slack update letting the customer support team know that the payment gateway is fully restored.",
"role": "user"
},
{
"content": "The payment gateway is back up and running. Everything is fully restored, so we're good to go.",
"role": "assistant"
}
] | chat | curated | 5 | v2 | |
v2-00014 | Draft a message to a teammate asking if they can cover my on-call shift for 2 hours on Thursday afternoon. | Hey [Colleague], would you be able to cover my on-call shift for 2 hours this Thursday afternoon? Let me know if that works for you. | [
{
"content": "Draft a message to a teammate asking if they can cover my on-call shift for 2 hours on Thursday afternoon.",
"role": "user"
},
{
"content": "Hey [Colleague], would you be able to cover my on-call shift for 2 hours this Thursday afternoon? Let me know if that works for you.",
"role"... | general | curated | 5 | v2 | |
v2-00015 | Draft a message to the team celebrating the successful launch of the dashboard. | Team, the new dashboard is officially live! Thanks for all the hard work getting this across the finish line. It looks great and is already providing the insights we need. | [
{
"content": "Draft a message to the team celebrating the successful launch of the dashboard.",
"role": "user"
},
{
"content": "Team, the new dashboard is officially live! Thanks for all the hard work getting this across the finish line. It looks great and is already providing the insights we need."... | general | curated | 5 | v2 | |
v2-00016 | Rewrite: 'I am writing to inquire if the marketing assets are prepared for our campaign launch tomorrow.' | Are the marketing assets ready for tomorrow's campaign launch? | [
{
"content": "Rewrite: 'I am writing to inquire if the marketing assets are prepared for our campaign launch tomorrow.'",
"role": "user"
},
{
"content": "Are the marketing assets ready for tomorrow's campaign launch?",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00017 | Draft a quick Slack message to the designer asking where the updated Figma links are located. | Hey, where can I find the updated Figma links? | [
{
"content": "Draft a quick Slack message to the designer asking where the updated Figma links are located.",
"role": "user"
},
{
"content": "Hey, where can I find the updated Figma links?",
"role": "assistant"
}
] | chat | curated | 5 | v2 | |
v2-00018 | Rewrite this email to sound like a normal professional person:
'Dear team, I hope this email finds you well. I am writing to provide an update on our quarterly milestones. We have made significant progress; however, some challenges remain. Please review the attached deck.' | Hi team, I'm sharing an update on our quarterly milestones. We've made good progress, though we still have a few challenges to address. Please take a look at the attached deck. | [
{
"content": "Rewrite this email to sound like a normal professional person:\n\n'Dear team, I hope this email finds you well. I am writing to provide an update on our quarterly milestones. We have made significant progress; however, some challenges remain. Please review the attached deck.'",
"role": "user"
... | email | curated | 5 | v2 | |
v2-00019 | Rewrite this stiff corporate email to a partner:
'Pursuant to our conversation yesterday, please find enclosed the draft proposal for our integration. Please do not hesitate to contact me if you have any questions or require further clarification.' | Following our chat yesterday, I've attached the draft proposal for our integration. Let me know if you have any questions. | [
{
"content": "Rewrite this stiff corporate email to a partner:\n\n'Pursuant to our conversation yesterday, please find enclosed the draft proposal for our integration. Please do not hesitate to contact me if you have any questions or require further clarification.'",
"role": "user"
},
{
"content": "... | email | curated | 5 | v2 | |
v2-00020 | Make this customer email warmer and less robotic:
'We regret to inform you that your request for a billing adjustment has been denied because it falls outside our standard 30-day window. We apologize for any inconvenience this may cause.' | Thanks for reaching out about your billing adjustment. I've looked into this, but I'm afraid we can't process the request since it falls outside our 30-day window. I'm sorry for the frustration this causes. | [
{
"content": "Make this customer email warmer and less robotic:\n\n'We regret to inform you that your request for a billing adjustment has been denied because it falls outside our standard 30-day window. We apologize for any inconvenience this may cause.'",
"role": "user"
},
{
"content": "Thanks for... | email | curated | 5 | v2 | |
v2-00021 | Write a professional but warm email to a candidate rejecting them after the final round of interviews. | Hi [Candidate Name], thank you for the time you spent with our team throughout the final interview process. We truly enjoyed learning more about your background and experience. While we were impressed with your qualifications, we've decided to move forward with another candidate for this role. We appreciate your intere... | [
{
"content": "Write a professional but warm email to a candidate rejecting them after the final round of interviews.",
"role": "user"
},
{
"content": "Hi [Candidate Name], thank you for the time you spent with our team throughout the final interview process. We truly enjoyed learning more about your... | email | curated | 5 | v2 | |
v2-00022 | Write an email to a client explaining that we found a bug in their integration and are deploying a hotfix in the next hour. | We've identified a bug in your integration and are deploying a hotfix within the next hour. You shouldn't notice any disruption, but we'll let you know as soon as the fix is live. | [
{
"content": "Write an email to a client explaining that we found a bug in their integration and are deploying a hotfix in the next hour.",
"role": "user"
},
{
"content": "We've identified a bug in your integration and are deploying a hotfix within the next hour. You shouldn't notice any disruption,... | email | curated | 5 | v2 | |
v2-00023 | Draft an email to my manager requesting PTO for the first week of July, outlining who will cover my projects. | Hi [Manager Name], I'm writing to request PTO for the first week of July, from July 1st through July 5th. I've coordinated with [Colleague Name] to cover my current projects while I'm out. Let me know if this works for the team schedule. | [
{
"content": "Draft an email to my manager requesting PTO for the first week of July, outlining who will cover my projects.",
"role": "user"
},
{
"content": "Hi [Manager Name], I'm writing to request PTO for the first week of July, from July 1st through July 5th. I've coordinated with [Colleague Nam... | email | curated | 5 | v2 | |
v2-00024 | Rewrite: 'I am writing to express my interest in the Product Manager position at your esteemed firm.' | I’m interested in the Product Manager position at your company. | [
{
"content": "Rewrite: 'I am writing to express my interest in the Product Manager position at your esteemed firm.'",
"role": "user"
},
{
"content": "I’m interested in the Product Manager position at your company.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00025 | Rewrite: 'Please be advised that your subscription is scheduled for renewal on June 1st, 2026.' | Your subscription renews on June 1st, 2026. | [
{
"content": "Rewrite: 'Please be advised that your subscription is scheduled for renewal on June 1st, 2026.'",
"role": "user"
},
{
"content": "Your subscription renews on June 1st, 2026.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00026 | Rewrite: 'I would like to kindly remind all employees that the office will be closed in observance of the upcoming holiday.' | The office will be closed for the upcoming holiday. | [
{
"content": "Rewrite: 'I would like to kindly remind all employees that the office will be closed in observance of the upcoming holiday.'",
"role": "user"
},
{
"content": "The office will be closed for the upcoming holiday.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00027 | Rewrite: 'In order to optimize our database throughput, it is necessary that we clean up historical indexes.' | We need to clean up historical indexes to optimize our database throughput. | [
{
"content": "Rewrite: 'In order to optimize our database throughput, it is necessary that we clean up historical indexes.'",
"role": "user"
},
{
"content": "We need to clean up historical indexes to optimize our database throughput.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00028 | Rewrite: 'I hope this email finds you well. I wanted to check if you had an opportunity to review my previous email.' | I'm following up to see if you've had a chance to review my previous email. | [
{
"content": "Rewrite: 'I hope this email finds you well. I wanted to check if you had an opportunity to review my previous email.'",
"role": "user"
},
{
"content": "I'm following up to see if you've had a chance to review my previous email.",
"role": "assistant"
}
] | email | curated | 5 | v2 | |
v2-00029 | Draft a cold sales outreach email to a CTO offering a demo of our database scaling tool. Make it brief and direct. | Hi [Name], I’m reaching out because I’ve seen how challenging database scaling can become as [Company] grows. We’ve built a tool that automates this process to keep performance consistent without the manual overhead. Do you have 10 minutes next week for a brief demo to see if it’s a fit for your stack? | [
{
"content": "Draft a cold sales outreach email to a CTO offering a demo of our database scaling tool. Make it brief and direct.",
"role": "user"
},
{
"content": "Hi [Name], I’m reaching out because I’ve seen how challenging database scaling can become as [Company] grows. We’ve built a tool that aut... | email | curated | 5 | v2 | |
v2-00030 | Write a follow-up email to a prospective client who went quiet after a demo. Keep it friendly and concise. | Hi [Name], thanks again for taking the time to chat about [Project/Product] last week. I'm following up to see if you've had a chance to review the demo or if you have any lingering questions. I'm happy to hop on a quick call if that's easier. | [
{
"content": "Write a follow-up email to a prospective client who went quiet after a demo. Keep it friendly and concise.",
"role": "user"
},
{
"content": "Hi [Name], thanks again for taking the time to chat about [Project/Product] last week. I'm following up to see if you've had a chance to review t... | email | curated | 5 | v2 | |
v2-00031 | Draft an email to a vendor asking for a discount on our software license renewal. | Hi [Name], I'm reviewing our software license renewal for [Product Name] coming up on [Date]. We've really valued the tool this year, but our budget for the upcoming term is tighter than expected. Would you be able to offer a discount or a more flexible pricing structure for this renewal? We'd love to continue our part... | [
{
"content": "Draft an email to a vendor asking for a discount on our software license renewal.",
"role": "user"
},
{
"content": "Hi [Name], I'm reviewing our software license renewal for [Product Name] coming up on [Date]. We've really valued the tool this year, but our budget for the upcoming term... | email | curated | 5 | v2 | |
v2-00032 | Draft an email to the company letting them know the AC is broken in the east wing and repair is scheduled. | Hi everyone, the AC is currently broken in the east wing. We’ve already scheduled repairs, and we’ll update you once the system is back up and running. Thanks for your patience. | [
{
"content": "Draft an email to the company letting them know the AC is broken in the east wing and repair is scheduled.",
"role": "user"
},
{
"content": "Hi everyone, the AC is currently broken in the east wing. We’ve already scheduled repairs, and we’ll update you once the system is back up and ru... | email | curated | 5 | v2 | |
v2-00033 | Rewrite: 'Your account has been flagged due to security concerns. Please click the link to authenticate your credentials.' | We've flagged your account for security reasons. Please click the link to verify your credentials. | [
{
"content": "Rewrite: 'Your account has been flagged due to security concerns. Please click the link to authenticate your credentials.'",
"role": "user"
},
{
"content": "We've flagged your account for security reasons. Please click the link to verify your credentials.",
"role": "assistant"
}
... | general | curated | 5 | v2 | |
v2-00034 | Draft an email to an API partner asking for access to their beta endpoints. | Hi [Name], I'm reaching out to request access to your beta endpoints for [Project]. We're looking to integrate these features early to streamline our workflow. Could you let me know the process for getting whitelisted? Thanks. | [
{
"content": "Draft an email to an API partner asking for access to their beta endpoints.",
"role": "user"
},
{
"content": "Hi [Name], I'm reaching out to request access to your beta endpoints for [Project]. We're looking to integrate these features early to streamline our workflow. Could you let me... | email | curated | 5 | v2 | |
v2-00035 | Draft an email to my team asking for volunteers to present at the next lunch-and-learn session. | Hi team, I'm looking for volunteers to present at our next lunch-and-learn. If you've got a project, skill, or topic you'd like to share, please let me know by [Date]. We'd love to hear what you're working on. | [
{
"content": "Draft an email to my team asking for volunteers to present at the next lunch-and-learn session.",
"role": "user"
},
{
"content": "Hi team, I'm looking for volunteers to present at our next lunch-and-learn. If you've got a project, skill, or topic you'd like to share, please let me know... | email | curated | 5 | v2 | |
v2-00036 | Rewrite this standard update as a startup founder talking to early team members: 'Our traction has been flat, and we must find a new channel.' | Growth's stalled out, so we need to find a new channel fast. | [
{
"content": "Rewrite this standard update as a startup founder talking to early team members: 'Our traction has been flat, and we must find a new channel.'",
"role": "user"
},
{
"content": "Growth's stalled out, so we need to find a new channel fast.",
"role": "assistant"
}
] | chat | curated | 5 | v2 | |
v2-00037 | Rewrite this as a senior backend engineer who dislikes corporate jargon: 'We need to align key stakeholders and synergize our efforts.' | Let's get everyone on the same page and coordinate our work. | [
{
"content": "Rewrite this as a senior backend engineer who dislikes corporate jargon: 'We need to align key stakeholders and synergize our efforts.'",
"role": "user"
},
{
"content": "Let's get everyone on the same page and coordinate our work.",
"role": "assistant"
}
] | general | curated | 4 | v2 | |
v2-00038 | Rewrite this email to sound like a supportive team coach: 'You made a mistake, but we can recover.' | I noticed the error, but we'll bounce back from this. Let's walk through the steps to get things back on track together. | [
{
"content": "Rewrite this email to sound like a supportive team coach: 'You made a mistake, but we can recover.'",
"role": "user"
},
{
"content": "I noticed the error, but we'll bounce back from this. Let's walk through the steps to get things back on track together.",
"role": "assistant"
}
] | email | curated | 5 | v2 | |
v2-00039 | Write a review of a restaurant in the style of a food critic who hates pretentious descriptions. | The [Restaurant Name] doesn't waste time on flowery menus or over-the-top plating. You get a solid steak, cooked exactly how you asked, and a side of potatoes that actually taste like potatoes. The service is fast and the chairs are comfortable. If you’re looking for a meal that doesn't require a dictionary to understa... | [
{
"content": "Write a review of a restaurant in the style of a food critic who hates pretentious descriptions.",
"role": "user"
},
{
"content": "The [Restaurant Name] doesn't waste time on flowery menus or over-the-top plating. You get a solid steak, cooked exactly how you asked, and a side of potat... | general | curated | 5 | v2 | |
v2-00040 | Explain how database indexes work in the style of a tired programmer explaining it to a non-technical coworker. | Think of a database like a massive book with no index at the back. If you need to find one specific piece of info, you have to read every single page from start to finish. It’s exhausting and slow. An index is basically just a cheat sheet at the back of that book. It lists the topic and tells you exactly which page to ... | [
{
"content": "Explain how database indexes work in the style of a tired programmer explaining it to a non-technical coworker.",
"role": "user"
},
{
"content": "Think of a database like a massive book with no index at the back. If you need to find one specific piece of info, you have to read every si... | general | curated | 5 | v2 | |
v2-00041 | Write a project delay notice in the voice of a direct, transparent CEO who doesn't sugarcoat bad news. | We’re missing our [Project] deadline. We hit unexpected technical hurdles that we didn't account for, and we won't finish by [Date] as planned. The new target date is [Date]. I know this is frustrating, but I’d rather deliver the quality we promised than rush a broken product. We’re doubling down on our efforts to get ... | [
{
"content": "Write a project delay notice in the voice of a direct, transparent CEO who doesn't sugarcoat bad news.",
"role": "user"
},
{
"content": "We’re missing our [Project] deadline. We hit unexpected technical hurdles that we didn't account for, and we won't finish by [Date] as planned. The n... | general | curated | 5 | v2 | |
v2-00042 | Draft a feature release note in the style of a UX writer who is obsessed with simplicity and clarity. | We’ve made it easier to manage your account. You can now update your billing information and view past invoices directly from your dashboard settings. | [
{
"content": "Draft a feature release note in the style of a UX writer who is obsessed with simplicity and clarity.",
"role": "user"
},
{
"content": "We’ve made it easier to manage your account. You can now update your billing information and view past invoices directly from your dashboard settings.... | general | curated | 5 | v2 | |
v2-00043 | Rewrite: 'We must align on product priorities to ensure maximum customer impact.' as a cynical startup veteran. | Let's pick which features we're actually shipping so we can pretend we're moving the needle. | [
{
"content": "Rewrite: 'We must align on product priorities to ensure maximum customer impact.' as a cynical startup veteran.",
"role": "user"
},
{
"content": "Let's pick which features we're actually shipping so we can pretend we're moving the needle.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00044 | Explain Git rebase to a junior developer in a warm, encouraging, mentor-like voice. | Think of Git rebase as a way to keep your project history clean and linear. Instead of creating messy merge commits every time you pull in changes from the main branch, rebase essentially picks up your commits and replays them on top of the latest work. It makes it look like you started your feature from the very lates... | [
{
"content": "Explain Git rebase to a junior developer in a warm, encouraging, mentor-like voice.",
"role": "user"
},
{
"content": "Think of Git rebase as a way to keep your project history clean and linear. Instead of creating messy merge commits every time you pull in changes from the main branch,... | general | curated | 5 | v2 | |
v2-00045 | Draft a LinkedIn post announcing a new job in a humble, down-to-earth voice that avoids standard corporate bragging. | I’m happy to share that I’ve started a new position at [Company]. I’ve always admired the work they do, so I’m looking forward to jumping in and learning from the team. Grateful for the support from everyone who helped me get here. | [
{
"content": "Draft a LinkedIn post announcing a new job in a humble, down-to-earth voice that avoids standard corporate bragging.",
"role": "user"
},
{
"content": "I’m happy to share that I’ve started a new position at [Company]. I’ve always admired the work they do, so I’m looking forward to jumpi... | general | curated | 5 | v2 | |
v2-00046 | Rewrite: 'I apologize for the delay in returning your call. Let's schedule a meeting.' in the tone of a busy VC. | Sorry for the delay. Let's get a meeting on the books. | [
{
"content": "Rewrite: 'I apologize for the delay in returning your call. Let's schedule a meeting.' in the tone of a busy VC.",
"role": "user"
},
{
"content": "Sorry for the delay. Let's get a meeting on the books.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00047 | Explain why a feature was cut in a transparent, empathetic product manager voice. | I'm writing to share that we've decided to cut the [Feature Name] project from our current roadmap. This wasn't an easy decision, but we need to focus our resources on [Core Priority/Goal] to ensure we're delivering the best possible experience for you. I know how much you were looking forward to this, and I appreciate... | [
{
"content": "Explain why a feature was cut in a transparent, empathetic product manager voice.",
"role": "user"
},
{
"content": "I'm writing to share that we've decided to cut the [Feature Name] project from our current roadmap. This wasn't an easy decision, but we need to focus our resources on [C... | general | curated | 4 | v2 | |
v2-00048 | Draft a Slack update about database migration failure in the style of a calm on-call engineer. | Heads up, the database migration hit an error and failed to complete. I'm currently looking into the logs to identify the root cause and will share an update once I have more information. | [
{
"content": "Draft a Slack update about database migration failure in the style of a calm on-call engineer.",
"role": "user"
},
{
"content": "Heads up, the database migration hit an error and failed to complete. I'm currently looking into the logs to identify the root cause and will share an update... | chat | curated | 5 | v2 | |
v2-00049 | Rewrite: 'We are pleased to introduce our new analytics dashboard, which offers advanced insights.' to sound like a tech copywriter writing for developers. | We've launched our new analytics dashboard, giving you deeper insights into your data. | [
{
"content": "Rewrite: 'We are pleased to introduce our new analytics dashboard, which offers advanced insights.' to sound like a tech copywriter writing for developers.",
"role": "user"
},
{
"content": "We've launched our new analytics dashboard, giving you deeper insights into your data.",
"ro... | general | curated | 4 | v2 | |
v2-00050 | Explain API rate limits like a security engineer talking to a junior frontend engineer. | Think of API rate limits as a bouncer at a club. We set them to stop one client from hogging all our resources or accidentally crashing our backend with too many requests. If your code hits that limit, the server will return a 429 Too Many Requests status. You'll need to handle that by implementing an exponential backo... | [
{
"content": "Explain API rate limits like a security engineer talking to a junior frontend engineer.",
"role": "user"
},
{
"content": "Think of API rate limits as a bouncer at a club. We set them to stop one client from hogging all our resources or accidentally crashing our backend with too many re... | general | curated | 5 | v2 | |
v2-00051 | Explain what a merge conflict is to a designer who has never used git. | A merge conflict happens when two people edit the exact same part of a file at the same time. Think of it like working on a shared design file where you and a teammate both move the same button to different spots. When you try to save your changes, the system doesn't know whose version is right, so it pauses and asks y... | [
{
"content": "Explain what a merge conflict is to a designer who has never used git.",
"role": "user"
},
{
"content": "A merge conflict happens when two people edit the exact same part of a file at the same time. Think of it like working on a shared design file where you and a teammate both move the... | general | curated | 5 | v2 | |
v2-00052 | Rewrite: 'We have optimized the codebase resulting in elevated efficiency.' in the style of a pragmatic tech lead. | We optimized the codebase and boosted efficiency. | [
{
"content": "Rewrite: 'We have optimized the codebase resulting in elevated efficiency.' in the style of a pragmatic tech lead.",
"role": "user"
},
{
"content": "We optimized the codebase and boosted efficiency.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00053 | Shorten this long update to one concise paragraph:
'In order to facilitate the progress of our current initiatives, we decided to perform an audit of our cloud infrastructure cost metrics. It is worth noting that we identified several orphaned storage volumes that are contributing to excess spend. Therefore, we are go... | We're auditing our cloud infrastructure costs and identified several orphaned storage volumes driving up expenses. We'll purge these volumes tonight. | [
{
"content": "Shorten this long update to one concise paragraph:\n\n'In order to facilitate the progress of our current initiatives, we decided to perform an audit of our cloud infrastructure cost metrics. It is worth noting that we identified several orphaned storage volumes that are contributing to excess spe... | compress | curated | 5 | v2 | |
v2-00054 | Cut this Slack message to 2 sentences max:
'Hi team, I wanted to follow up on the discussion we had earlier regarding the API design. I have created a document outlining the core options and would appreciate it if you could take a look and add your comments.' | I've outlined our API design options in this document. Please take a look and add your comments. | [
{
"content": "Cut this Slack message to 2 sentences max:\n\n'Hi team, I wanted to follow up on the discussion we had earlier regarding the API design. I have created a document outlining the core options and would appreciate it if you could take a look and add your comments.'",
"role": "user"
},
{
"... | chat | curated | 5 | v2 | |
v2-00055 | Condense this status report to its core blockers and next steps:
'We spent the last two days trying to debug the memory leak. We ran multiple profiles and found that the garbage collector is stalling due to excessive object allocation in the parser. We are planning to refactor the parser module. We cannot proceed with... | The memory leak is stalling deployment. We identified excessive object allocation in the parser as the cause and are now refactoring the module. | [
{
"content": "Condense this status report to its core blockers and next steps:\n\n'We spent the last two days trying to debug the memory leak. We ran multiple profiles and found that the garbage collector is stalling due to excessive object allocation in the parser. We are planning to refactor the parser module... | general | curated | 5 | v2 | |
v2-00056 | Tighten this email draft to be brief and direct:
'Dear client, I am writing to let you know that we have finalized the migration of your account to our new servers. You might notice some speed improvements. Please let us know if you spot any issues.' | Your account migration to our new servers is complete. You may notice faster performance. Let us know if you run into any issues. | [
{
"content": "Tighten this email draft to be brief and direct:\n\n'Dear client, I am writing to let you know that we have finalized the migration of your account to our new servers. You might notice some speed improvements. Please let us know if you spot any issues.'",
"role": "user"
},
{
"content":... | email | curated | 5 | v2 | |
v2-00057 | Draft a one-sentence summary of this update: 'We had to roll back the release because the user session token was expiring after 5 minutes due to an incorrect config change. The team is debugging now.' | We rolled back the release because an incorrect configuration caused user session tokens to expire after five minutes, and the team is currently debugging the issue. | [
{
"content": "Draft a one-sentence summary of this update: 'We had to roll back the release because the user session token was expiring after 5 minutes due to an incorrect config change. The team is debugging now.'",
"role": "user"
},
{
"content": "We rolled back the release because an incorrect con... | general | curated | 5 | v2 | |
v2-00058 | Rewrite this to be under 50 words: 'I wanted to check in to see if you have had a chance to review the onboarding designs I sent over on Tuesday. We have a meeting with the client on Friday and it would be great to have your feedback before then.' | Have you had a chance to review the onboarding designs I sent Tuesday? I'd love your feedback before our client meeting this Friday. | [
{
"content": "Rewrite this to be under 50 words: 'I wanted to check in to see if you have had a chance to review the onboarding designs I sent over on Tuesday. We have a meeting with the client on Friday and it would be great to have your feedback before then.'",
"role": "user"
},
{
"content": "Have... | general | curated | 5 | v2 | |
v2-00059 | Shorten this meeting invite description to a single bulleted list of 3 key topics. | • Review [Project] Q3 performance metrics. • Align on upcoming [Department] project timelines. • Discuss resource allocation for [Date]. | [
{
"content": "Shorten this meeting invite description to a single bulleted list of 3 key topics.",
"role": "user"
},
{
"content": "• Review [Project] Q3 performance metrics. • Align on upcoming [Department] project timelines. • Discuss resource allocation for [Date].",
"role": "assistant"
}
] | compress | curated | 5 | v2 | |
v2-00060 | Make this release log brief. Cut out all introductory fluff. | Version [Version Number] Release Notes: Added [Feature Name] to improve [Functionality]. Fixed bug causing [Issue] during [Process]. Updated [Dependency/Tool] to [Version]. | [
{
"content": "Make this release log brief. Cut out all introductory fluff.",
"role": "user"
},
{
"content": "Version [Version Number] Release Notes: Added [Feature Name] to improve [Functionality]. Fixed bug causing [Issue] during [Process]. Updated [Dependency/Tool] to [Version].",
"role": "ass... | general | curated | 5 | v2 | |
v2-00061 | Rewrite: 'It is highly critical that all developers clean up their local branches after merging PRs so that we do not clutter the remote repository.' to be short and clear. | Please delete your local branches after merging PRs to keep our remote repository clean. | [
{
"content": "Rewrite: 'It is highly critical that all developers clean up their local branches after merging PRs so that we do not clutter the remote repository.' to be short and clear.",
"role": "user"
},
{
"content": "Please delete your local branches after merging PRs to keep our remote reposito... | general | curated | 5 | v2 | |
v2-00062 | Draft a 3-bullet-point summary of a long technical incident report. | • A database configuration error caused a 45-minute service outage at 10:00 AM. • The team restored connectivity by reverting to the previous stable schema version. • We're implementing automated validation checks to prevent similar deployment issues in the future. | [
{
"content": "Draft a 3-bullet-point summary of a long technical incident report.",
"role": "user"
},
{
"content": "• A database configuration error caused a 45-minute service outage at 10:00 AM. • The team restored connectivity by reverting to the previous stable schema version. • We're implementin... | general | curated | 5 | v2 | |
v2-00063 | Condense this: 'The purpose of this document is to outline the rules for code reviews. Code reviews are important. We must review all PRs before merging.' | This document outlines our code review rules. All PRs must be reviewed before merging. | [
{
"content": "Condense this: 'The purpose of this document is to outline the rules for code reviews. Code reviews are important. We must review all PRs before merging.'",
"role": "user"
},
{
"content": "This document outlines our code review rules. All PRs must be reviewed before merging.",
"rol... | general | curated | 5 | v2 | |
v2-00064 | Reduce this status report to just two lines of text. | We've completed the primary development phase for [Project]. Testing is underway, and we're on track for the [Date] deadline. | [
{
"content": "Reduce this status report to just two lines of text.",
"role": "user"
},
{
"content": "We've completed the primary development phase for [Project]. Testing is underway, and we're on track for the [Date] deadline.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00065 | Draft a ultra-short Slack ping asking for a design asset. Under 10 words. | Hey, could you send over that design asset? | [
{
"content": "Draft a ultra-short Slack ping asking for a design asset. Under 10 words.",
"role": "user"
},
{
"content": "Hey, could you send over that design asset?",
"role": "assistant"
}
] | chat | curated | 5 | v2 | |
v2-00066 | Shorten: 'In order to ensure that we maintain high code standards, we will be holding weekly code review workshops.' | We're holding weekly code review workshops to maintain high standards. | [
{
"content": "Shorten: 'In order to ensure that we maintain high code standards, we will be holding weekly code review workshops.'",
"role": "user"
},
{
"content": "We're holding weekly code review workshops to maintain high standards.",
"role": "assistant"
}
] | compress | curated | 5 | v2 | |
v2-00067 | Compress this customer notification down to a single sentence. | Your [Service Name] subscription will renew on [Date] at the current rate. | [
{
"content": "Compress this customer notification down to a single sentence.",
"role": "user"
},
{
"content": "Your [Service Name] subscription will renew on [Date] at the current rate.",
"role": "assistant"
}
] | compress | curated | 5 | v2 | |
v2-00068 | Draft a short post-mortem summary for a minor outage. Keep it under 60 words. | We experienced a 15-minute service disruption today due to a configuration error during the deployment of [Project]. We've rolled back the changes and implemented additional validation checks to prevent this from recurring. Thanks for your patience while we resolved the issue. | [
{
"content": "Draft a short post-mortem summary for a minor outage. Keep it under 60 words.",
"role": "user"
},
{
"content": "We experienced a 15-minute service disruption today due to a configuration error during the deployment of [Project]. We've rolled back the changes and implemented additional ... | general | curated | 5 | v2 | |
v2-00069 | Fix the grammar and awkward phrasing in this Slack message:
'Me and John done the changes but we seen some error on staging.' | John and I finished the changes, but we're seeing some errors on staging. | [
{
"content": "Fix the grammar and awkward phrasing in this Slack message:\n\n'Me and John done the changes but we seen some error on staging.'",
"role": "user"
},
{
"content": "John and I finished the changes, but we're seeing some errors on staging.",
"role": "assistant"
}
] | chat | curated | 5 | v2 | |
v2-00070 | Clean up the grammar in this draft but keep the casual, friendly tone:
'Just wanted to check if your coming tomorrow because if so we can discuss the schema, what do you think?' | Just wanted to check if you're coming tomorrow. If so, we can discuss the schema. What do you think? | [
{
"content": "Clean up the grammar in this draft but keep the casual, friendly tone:\n\n'Just wanted to check if your coming tomorrow because if so we can discuss the schema, what do you think?'",
"role": "user"
},
{
"content": "Just wanted to check if you're coming tomorrow. If so, we can discuss t... | grammar | curated | 5 | v2 | |
v2-00071 | Rewrite this for clarity. The sentence is too long and confusing:
'The server which was updated yesterday by the ops team that had the new database drivers installed is now showing memory spikes because of the connection pool settings are too high.' | The server updated by the ops team yesterday with new database drivers is showing memory spikes because the connection pool settings are too high. | [
{
"content": "Rewrite this for clarity. The sentence is too long and confusing:\n\n'The server which was updated yesterday by the ops team that had the new database drivers installed is now showing memory spikes because of the connection pool settings are too high.'",
"role": "user"
},
{
"content": ... | general | curated | 5 | v2 | |
v2-00072 | Fix typos and punctuation in this quick response:
'hey, i think we should use the new API. its much faster and it dont require auth token in header' | Hey, I think we should use the new API. It's much faster and it doesn't require an auth token in the header. | [
{
"content": "Fix typos and punctuation in this quick response:\n\n'hey, i think we should use the new API. its much faster and it dont require auth token in header'",
"role": "user"
},
{
"content": "Hey, I think we should use the new API. It's much faster and it doesn't require an auth token in the... | grammar | curated | 5 | v2 | |
v2-00073 | Rewrite this message to make it clear and grammatically correct without sounding formal:
'We was thinking about doing the migration at Friday evening, does that works for you?' | We're planning the migration for Friday evening. Does that work for you? | [
{
"content": "Rewrite this message to make it clear and grammatically correct without sounding formal:\n\n'We was thinking about doing the migration at Friday evening, does that works for you?'",
"role": "user"
},
{
"content": "We're planning the migration for Friday evening. Does that work for you?... | general | curated | 5 | v2 | |
v2-00074 | Improve the clarity of this technical explanation: 'Docker is like a VM but it doesn't have an OS inside, it shares the host OS, making it faster.' | Docker functions like a VM but lacks its own OS, instead sharing the host's kernel to run more efficiently. | [
{
"content": "Improve the clarity of this technical explanation: 'Docker is like a VM but it doesn't have an OS inside, it shares the host OS, making it faster.'",
"role": "user"
},
{
"content": "Docker functions like a VM but lacks its own OS, instead sharing the host's kernel to run more efficient... | general | curated | 5 | v2 | |
v2-00075 | Fix the punctuation and run-on structure of this bug description. | The app crashes when users attempt to upload a profile picture exceeding 5MB. This error occurs consistently on both iOS and Android devices, preventing the update from completing. | [
{
"content": "Fix the punctuation and run-on structure of this bug description.",
"role": "user"
},
{
"content": "The app crashes when users attempt to upload a profile picture exceeding 5MB. This error occurs consistently on both iOS and Android devices, preventing the update from completing.",
... | grammar | curated | 5 | v2 | |
v2-00076 | Rewrite this customer update to be grammatically correct and easier to read. | We've updated your account and the changes are now live. You can log in to view the adjustments. Let us know if you have any questions. | [
{
"content": "Rewrite this customer update to be grammatically correct and easier to read.",
"role": "user"
},
{
"content": "We've updated your account and the changes are now live. You can log in to view the adjustments. Let us know if you have any questions.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00077 | Clean up this stream-of-consciousness draft: 'So I was looking at the logs and there is a lot of timeouts, we probably should increase the database pool size or maybe optimize that query, not sure.' | I checked the logs and noticed numerous timeouts. We should either increase the database pool size or optimize the query. | [
{
"content": "Clean up this stream-of-consciousness draft: 'So I was looking at the logs and there is a lot of timeouts, we probably should increase the database pool size or maybe optimize that query, not sure.'",
"role": "user"
},
{
"content": "I checked the logs and noticed numerous timeouts. We ... | general | curated | 5 | v2 | |
v2-00078 | Fix grammar and clarity: 'Its important that we dont run migrations when traffic is high because it can lock tables.' | We shouldn't run migrations during high traffic because they can lock tables. | [
{
"content": "Fix grammar and clarity: 'Its important that we dont run migrations when traffic is high because it can lock tables.'",
"role": "user"
},
{
"content": "We shouldn't run migrations during high traffic because they can lock tables.",
"role": "assistant"
}
] | grammar | curated | 5 | v2 | |
v2-00079 | Rewrite this technical error explanation so a non-technical manager can understand it clearly. | Our system failed because it couldn't connect to the database, which acts as our central storage. This prevented the application from retrieving the data it needed to complete the user's request, causing the error. | [
{
"content": "Rewrite this technical error explanation so a non-technical manager can understand it clearly.",
"role": "user"
},
{
"content": "Our system failed because it couldn't connect to the database, which acts as our central storage. This prevented the application from retrieving the data it ... | general | curated | 5 | v2 | |
v2-00080 | Correct the grammatical errors in this quick status report: 'Yesterday I have working on the landing page, today I am going to finish it.' | Yesterday I worked on the landing page, and today I'm going to finish it. | [
{
"content": "Correct the grammatical errors in this quick status report: 'Yesterday I have working on the landing page, today I am going to finish it.'",
"role": "user"
},
{
"content": "Yesterday I worked on the landing page, and today I'm going to finish it.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00081 | Rewrite this confusing email sentence to be clear and professional. | Please provide your feedback on the attached draft by [Date] so we can finalize the project. | [
{
"content": "Rewrite this confusing email sentence to be clear and professional.",
"role": "user"
},
{
"content": "Please provide your feedback on the attached draft by [Date] so we can finalize the project.",
"role": "assistant"
}
] | email | curated | 5 | v2 | |
v2-00082 | Fix the syntax and typos in this draft reply to a GitHub issue. | Thanks for reporting this. I've looked into the issue and it seems like a bug in the input validation logic. I'm working on a fix now and should have a pull request ready shortly. | [
{
"content": "Fix the syntax and typos in this draft reply to a GitHub issue.",
"role": "user"
},
{
"content": "Thanks for reporting this. I've looked into the issue and it seems like a bug in the input validation logic. I'm working on a fix now and should have a pull request ready shortly.",
"r... | grammar | curated | 5 | v2 | |
v2-00083 | Rewrite this instructions list to make it easier for a new hire to follow. | Welcome to the team! Follow these steps to get set up: 1. Log in to your [Company] account. 2. Complete the onboarding modules in [Tool]. 3. Review the project documentation located in [Location]. 4. Schedule a sync with [Colleague] by [Date] to discuss your goals. Feel free to ask if you run into any issues. | [
{
"content": "Rewrite this instructions list to make it easier for a new hire to follow.",
"role": "user"
},
{
"content": "Welcome to the team! Follow these steps to get set up: 1. Log in to your [Company] account. 2. Complete the onboarding modules in [Tool]. 3. Review the project documentation loc... | general | curated | 5 | v2 | |
v2-00084 | Clean up the phrasing: 'We need to make sure that we have all the tests passing before we do any commit to main.' | Ensure all tests pass before committing to main. | [
{
"content": "Clean up the phrasing: 'We need to make sure that we have all the tests passing before we do any commit to main.'",
"role": "user"
},
{
"content": "Ensure all tests pass before committing to main.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00085 | Change the tone of this email from cold/formal to warm and professional:
'Your pull request has been reviewed. Several changes are required before it can be merged. Refer to the comments below.' | I've finished reviewing your pull request. There are a few updates needed before we can merge it, so please take a look at the comments below. | [
{
"content": "Change the tone of this email from cold/formal to warm and professional:\n\n'Your pull request has been reviewed. Several changes are required before it can be merged. Refer to the comments below.'",
"role": "user"
},
{
"content": "I've finished reviewing your pull request. There are a... | email | curated | 5 | v2 | |
v2-00086 | Make this message to a client less blunt and more polite:
'We cannot deliver the feature this week. We are behind schedule. It will be ready next Wednesday.' | We've run into a slight delay and won't be able to deliver the feature this week as planned. We're working to get it finished and will have it ready for you next Wednesday. | [
{
"content": "Make this message to a client less blunt and more polite:\n\n'We cannot deliver the feature this week. We are behind schedule. It will be ready next Wednesday.'",
"role": "user"
},
{
"content": "We've run into a slight delay and won't be able to deliver the feature this week as planned... | general | curated | 5 | v2 | |
v2-00087 | Rewrite this casual Slack message to be professional enough for a client email:
'hey, we had a bug with payments but we fixed it. should be all good now. let us know if it fails again.' | We identified and resolved a technical issue affecting our payment system. The service is now functioning as expected. Please let us know if you encounter any further difficulties. | [
{
"content": "Rewrite this casual Slack message to be professional enough for a client email:\n\n'hey, we had a bug with payments but we fixed it. should be all good now. let us know if it fails again.'",
"role": "user"
},
{
"content": "We identified and resolved a technical issue affecting our paym... | chat | curated | 5 | v2 | |
v2-00088 | Tone down the defensiveness in this email response to a bug report:
'The bug you reported is not a problem with our code. It is because you configured the API key wrong. Please fix your config.' | Thanks for flagging this. It looks like the issue stems from the API key configuration. Please double-check your settings, as that should resolve the error. | [
{
"content": "Tone down the defensiveness in this email response to a bug report:\n\n'The bug you reported is not a problem with our code. It is because you configured the API key wrong. Please fix your config.'",
"role": "user"
},
{
"content": "Thanks for flagging this. It looks like the issue stem... | email | curated | 5 | v2 | |
v2-00089 | Rewrite this to sound more collaborative and less demanding: 'You need to finish your code review by noon today.' | Could you please wrap up your code review by noon today? Let me know if you need any help getting it across the finish line. | [
{
"content": "Rewrite this to sound more collaborative and less demanding: 'You need to finish your code review by noon today.'",
"role": "user"
},
{
"content": "Could you please wrap up your code review by noon today? Let me know if you need any help getting it across the finish line.",
"role":... | general | curated | 5 | v2 | |
v2-00090 | Make this rejection email warmer and more encouraging. | Thanks for giving us the chance to review your application for the [Role] position. We really enjoyed learning about your background, but we've decided to move forward with other candidates who are a closer match for our current needs. We appreciate the time you put into this process and hope you'll keep an eye on our ... | [
{
"content": "Make this rejection email warmer and more encouraging.",
"role": "user"
},
{
"content": "Thanks for giving us the chance to review your application for the [Role] position. We really enjoyed learning about your background, but we've decided to move forward with other candidates who are... | email | curated | 5 | v2 | |
v2-00091 | Draft a Slack announcement about a reorganizing of teams. Make it sound exciting rather than corporate and dry. | Big news! We’re shaking things up and reorganizing our teams to better support our upcoming goals. We’re excited to see how these new structures help us collaborate and move faster. Check out the [Link] for all the details on the new setup. Let’s make this happen! | [
{
"content": "Draft a Slack announcement about a reorganizing of teams. Make it sound exciting rather than corporate and dry.",
"role": "user"
},
{
"content": "Big news! We’re shaking things up and reorganizing our teams to better support our upcoming goals. We’re excited to see how these new struct... | chat | curated | 4 | v2 | |
v2-00092 | Draft a message apologizing for a late response. Make it warm and friendly. | So sorry for the delay in getting back to you. I've been catching up on things and appreciate your patience. | [
{
"content": "Draft a message apologizing for a late response. Make it warm and friendly.",
"role": "user"
},
{
"content": "So sorry for the delay in getting back to you. I've been catching up on things and appreciate your patience.",
"role": "assistant"
}
] | general | curated | 5 | v2 | |
v2-00093 | Make this project update sound more confident and proactive: 'We are still having some trouble with the API, but we hope to fix it soon.' | We're actively troubleshooting the API and have identified the path to a fix, which we'll implement shortly. | [
{
"content": "Make this project update sound more confident and proactive: 'We are still having some trouble with the API, but we hope to fix it soon.'",
"role": "user"
},
{
"content": "We're actively troubleshooting the API and have identified the path to a fix, which we'll implement shortly.",
... | general | curated | 5 | v2 | |
v2-00094 | Draft a gentle nudge to a coworker who hasn't responded to a blocker ticket. | Hi [Colleague], I'm checking in on the blocker ticket for [Project]. Do you have an update on this? I'm currently stuck until we get that sorted. | [
{
"content": "Draft a gentle nudge to a coworker who hasn't responded to a blocker ticket.",
"role": "user"
},
{
"content": "Hi [Colleague], I'm checking in on the blocker ticket for [Project]. Do you have an update on this? I'm currently stuck until we get that sorted.",
"role": "assistant"
}... | general | curated | 5 | v2 | |
v2-00095 | Rewrite: 'Do not use this channel for random questions.' to sound polite and redirect users to the correct channel. | Please use the #[Channel Name] channel for general questions so we can keep this space focused on project updates. | [
{
"content": "Rewrite: 'Do not use this channel for random questions.' to sound polite and redirect users to the correct channel.",
"role": "user"
},
{
"content": "Please use the #[Channel Name] channel for general questions so we can keep this space focused on project updates.",
"role": "assist... | chat | curated | 5 | v2 | |
v2-00096 | Draft a request for feedback on a document. Make it open and inviting. | I've finished the draft for [Document Name] and would love to get your thoughts on it. Please let me know if you have any feedback or suggestions for improvement. I'm open to whatever changes you think are necessary. | [
{
"content": "Draft a request for feedback on a document. Make it open and inviting.",
"role": "user"
},
{
"content": "I've finished the draft for [Document Name] and would love to get your thoughts on it. Please let me know if you have any feedback or suggestions for improvement. I'm open to whatev... | general | curated | 5 | v2 | |
v2-00097 | Rewrite this formal out-of-office message to sound more natural and friendly. | Hi there! I'm out of the office until [Return Date] and won't have access to email. If you need immediate help, please reach out to [Colleague Name] at [Colleague Email]. Otherwise, I'll get back to you as soon as I'm back. | [
{
"content": "Rewrite this formal out-of-office message to sound more natural and friendly.",
"role": "user"
},
{
"content": "Hi there! I'm out of the office until [Return Date] and won't have access to email. If you need immediate help, please reach out to [Colleague Name] at [Colleague Email]. Oth... | general | curated | 5 | v2 | |
v2-00098 | Rewrite: 'We are experiencing server issues and you can't log in.' to sound professional, calm, and reassuring. | We're currently working to resolve some server issues that are affecting log-in access. We appreciate your patience and will let you know as soon as everything is back up and running. | [
{
"content": "Rewrite: 'We are experiencing server issues and you can't log in.' to sound professional, calm, and reassuring.",
"role": "user"
},
{
"content": "We're currently working to resolve some server issues that are affecting log-in access. We appreciate your patience and will let you know as... | general | curated | 5 | v2 | |
v2-00099 | Draft a welcome message for a new hire on Slack. Make it warm and excited. | Welcome to the team, [Name]! We're so excited to have you on board and can't wait to start working together. | [
{
"content": "Draft a welcome message for a new hire on Slack. Make it warm and excited.",
"role": "user"
},
{
"content": "Welcome to the team, [Name]! We're so excited to have you on board and can't wait to start working together.",
"role": "assistant"
}
] | chat | curated | 5 | v2 |
End of preview. Expand in Data Studio
humanize-rl-sft-dataset (v2)
4,835 high-quality SFT pairs for training a model to write natural, direct prose.
Part of the humanize-rl project — a two-layer scoring and alignment pipeline for training small models to generate natural, human-sounding text.
What this trains
A model that can:
- Write natural Slack messages and emails from scratch.
- Rewrite stiff/formal/corporate text into direct, human-sounding prose.
- Fix grammar without making text formal.
- Shorten and compress without losing meaning.
Domain breakdown
| Domain | Rows | % |
|---|---|---|
| chat | 2288 | 47.3% |
| 1453 | 30.1% | |
| general | 800 | 16.5% |
| creative | 255 | 5.3% |
| grammar | 26 | 0.5% |
| compress | 13 | 0.3% |
Quality
- All rows passed a deterministic heuristic quality check.
- All rows passed a Flash Lite LLM judge (naturalness ≥ 4, fact preservation, no AI tells).
- Average naturalness score: 4.91 / 5.0
- Bad-phrase rate (Certainly, Furthermore, etc.): < 0.1%
Sources
| Source | Rows |
|---|---|
| safe_expand_3000_raw | 1802 |
| stream_b | 1617 |
| safe_expand_raw | 667 |
| chat_expanded | 423 |
| curated | 326 |
safe_expand_*: generated from curated seeds using a safe prompt-based expansion (Arkaprompt_based_generator).stream_b: instruction-response pairs generated from real human-written text (wardacoder/business-email-dataset, corbt/enron-emails, liamdugan/raid human rows, euclaise/writingprompts).chat_expanded: Slack/chat focused pairs generated from hand-crafted direct seeds.curated: hand-verified base seeds.
Schema
| Field | Type | Description |
|---|---|---|
| id | str | Row ID |
| instruction | str | User task or rewrite request |
| response | str | Natural human-sounding response |
| messages | list | ShareGPT format: user/assistant turns |
| domain | str | chat / email / general / creative / grammar / compress |
| source | str | Data stream origin |
| mode | str | direct_generation or rewrite_humanize |
| naturalness_judge | int | Flash Lite judge score (1-5), null for curated rows |
| version | str | "v2" |
Previous version
v1 (1,269 rows) is available as the default config. v2 is a full rebuild with broader domain coverage and stricter quality gates.
Project
This dataset is built and maintained as part of the humanize-rl project.
- GitHub: https://github.com/jayshah5696/humanize-rl
- Goal: Train small open models (Gemma 4 E2B) to natively produce natural, human-sounding text — both from scratch and by rewriting stiff/formal drafts.
- Architecture: Two-layer scoring pipeline (Layer 1 deterministic heuristics + Layer 2 LLM judge), SFT on this dataset, optional RL post-training with DAPO.
License
Apache-2.0. Source datasets have individual licenses — see data/source_manifest_v04.json in the training repo for attribution details.
- Downloads last month
- 44