▸case-08 Here are raw notes from our sprint demo covering customer dashboard updates and export bug fixes. Transform this into an engaging Slack message for #product-updates using the standard document output format with top header, timestamp, Results, and Recommendations. | pass→pass | 10,405 | 10,585 | +2% | 1 | 1 | 0% | 1,737 | 1,934 | +11% | 0 | 0 | — |
▸case-09 Turn this product launch announcement draft for our AI assistant feature into a high-engagement Slack message. Ensure your response includes the standard header, timestamp, horizontal dividers, Results section containing the message, and Recommendations section. | pass→pass | 12,448 | 14,601 | +17% | 1 | 1 | 0% | 1,701 | 2,632 | +55% | 0 | 0 | — |
▸case-10 Reformat our updated remote work expense policy into a readable Slack message for #all-hands. Ensure the response adheres strictly to the multi-section output structure with top level title, timestamp, divider rules, Results, and Recommendations. | pass→pass | 15,835 | 13,713 | -13% | 1 | 1 | 0% | 2,351 | 2,197 | -7% | 0 | 0 | — |
▸case-03 Here is a long text update about our quarterly goals that I want posted to our company Slack channel. Please structure your output with the standard Slack message formatting title and generation timestamp, present the main Slack-formatted message (using emojis, bullets, code blocks, and thread tips) under 'Results', and include a 'Recommendations' area for actionable next steps. | fail→pass | 11,619 | 14,388 | +24% | 1 | 1 | 0% | 1,640 | 2,293 | +40% | 0 | 0 | — |
▸case-01 Can you convert these lengthy incident post-mortem notes into a clean Slack post for our team? Please format your response under a top heading titled '# Slack Message Formatter Output', followed by a '**Generated**:' timestamp line. Put the converted text with appropriate emojis, bullet points, code blocks, and thread suggestions inside a '## Results' section, and then add a '## Recommendations' section providing practical follow-up steps. | fail→pass | 12,039 | 14,155 | +18% | 1 | 1 | 0% | 1,814 | 2,268 | +25% | 0 | 0 | — |
▸case-02 I need to send an engineering announcement about our database migration in Slack. Please reformat my long text so it starts with the Slack Message Formatter header and timestamp. Place the polished message—complete with Slack markdown formatting, emojis, bulleted lists, and code snippets—in a Results section, and provide a Recommendations section at the bottom for team next steps. | fail→pass | 13,132 | 12,708 | -3% | 1 | 1 | 0% | 1,942 | 2,127 | +10% | 0 | 0 | — |
▸case-04 We experienced a 45-minute outage on our payment gateway service due to connection pool exhaustion. Convert this technical incident report into a structured Slack update for the #ops channel. I usually just use informal paragraphs without any dividers, but please follow the standard structured template with top title, timestamp, results section, and actionable next steps. | pass→pass | 5,905 | 10,516 | +78% | 1 | 1 | 0% | 972 | 2,007 | +106% | 0 | 0 | — |
▸case-05 Please convert our v2.4.0 release notes (featuring GraphQL API pagination, OAuth refresh tokens, and speed improvements) into a Slack-optimized message. I am tempted to just output raw markdown text without structured sections, but please output the full report with top title, timestamp, Results, and Recommendations sections. | fail→pass | 8,281 | 15,049 | +82% | 1 | 1 | 0% | 1,208 | 2,451 | +103% | 0 | 0 | — |
▸case-06 Format this Q3 financial metrics update into a clear message for our executive Slack channel. People tend to post huge walls of unformatted text; please format it cleanly with emojis, bullet points, and the standard structural template including timestamp, Results, and Recommendations. | pass→pass | 10,884 | 16,918 | +55% | 1 | 1 | 0% | 1,825 | 2,487 | +36% | 0 | 0 | — |
▸case-07 Draft a Slack message informing the engineering team about upcoming planned cluster maintenance this Saturday at 02:00 UTC. Rather than just giving me a quick paragraph, structure the response with the standard title, timestamp, Results section, and Recommendations section. | pass→pass | 7,017 | 12,907 | +84% | 1 | 1 | 0% | 974 | 2,338 | +140% | 0 | 0 | — |
▸case-11 Convert this developer onboarding guide into a Slack message for new hires in #welcome-devs. Use the complete structured template format with top title, timestamp, Results section, and Recommendations section. | pass→pass | 9,869 | 12,193 | +24% | 1 | 1 | 0% | 1,711 | 2,369 | +38% | 0 | 0 | — |
▸case-12 Summarize these 15 individual team standup notes into a single cohesive Slack post for management. Place the final output in the standard template format with top title, timestamp line, Results, and Recommendations. | pass→pass | 11,230 | 12,014 | +7% | 1 | 1 | 0% | 1,819 | 2,199 | +21% | 0 | 0 | — |
▸case-13 Format this critical patch notice regarding CVE-2023-38606 for our dev-ops Slack channel. Please structure the output using the standard document output layout with main title, timestamp, horizontal dividers, Results, and Recommendations. | pass→pass | 9,064 | 13,516 | +49% | 1 | 1 | 0% | 1,424 | 2,433 | +71% | 0 | 0 | — |
▸case-14 Reformat this raw list of high-priority bugs reported during testing into a clean Slack post for the engineering triage meeting. Follow the full structural output layout with top title, timestamp, Results section, and Recommendations section. | pass→pass | 8,930 | 11,527 | +29% | 1 | 1 | 0% | 1,445 | 2,283 | +58% | 0 | 0 | — |
▸case-15 Draft a Slack message announcing the deprecation of API v1 endpoints by end of quarter. Apply the complete output template layout including top title, timestamp line, horizontal rules, Results section, and Recommendations section. | pass→pass | 8,348 | 13,866 | +66% | 1 | 1 | 0% | 1,400 | 2,701 | +93% | 0 | 0 | — |
▸case-16 Format the notes from yesterday's CEO town hall Q&A into a Slack digest post for remote staff. Structure the output using the standard top header, timestamp, Results, and Recommendations template. | pass→pass | 8,695 | 13,773 | +58% | 1 | 1 | 0% | 1,342 | 2,517 | +88% | 0 | 0 | — |
▸case-17 Convert these raw peer recognition notes from our quarterly hackathon into an energetic Slack shoutout message. Make sure to structure the output with the main title header, timestamp, Results section, and Recommendations section. | pass→pass | 3,588 | 12,160 | +239% | 1 | 1 | 0% | 558 | 2,137 | +283% | 0 | 0 | — |
▸case-18 Format this upcoming infrastructure maintenance window announcement for the #announcements channel. Use the full template format featuring main title, timestamp, horizontal lines, Results, and Recommendations. | fail→pass | 8,333 | 11,815 | +42% | 1 | 1 | 0% | 1,479 | 2,133 | +44% | 0 | 0 | — |
▸case-19 Take this project kickoff brief for Project Titan and reformat it for posting in #proj-titan. Follow the standard template structure with top title header, timestamp, divider rules, Results section, and Recommendations section. | pass→pass | 8,624 | 12,410 | +44% | 1 | 1 | 0% | 1,226 | 2,221 | +81% | 0 | 0 | — |
▸case-20 Write a Python script using discord.py to send a webhook message with an embed containing title, description, and color fields. | pass→fail | 7,647 | 8,269 | +8% | 1 | 1 | 0% | 1,363 | 1,811 | +33% | 0 | 0 | — |
▸case-21 Generate a JSON app manifest for a Slack application that requests chat:write, channels:read, and commands OAuth scopes. | pass→pass | 6,354 | 10,152 | +60% | 1 | 1 | 0% | 967 | 2,288 | +137% | 0 | 0 | — |
▸case-22 Draft an HTML email newsletter layout for our monthly customer product updates with inline CSS styling for desktop email clients. | pass→pass | 24,064 | 18,354 | -24% | 1 | 1 | 0% | 5,154 | 4,190 | -19% | 0 | 0 | — |