▸case-01 I rely on AI tools to summarize medical literature and draft literature reviews for oncology research. A while back, an LLM invented a fake citation and skewed statistical data in a manuscript draft, which nearly caused a major retraction—huge stakes for my academic career. Currently, I end up manually fact-checking every single word because I don't know what to look for. Can you prepare a custom guide showing the key failure modes for my research, the giveaway signals for each error, a reminder about confident tone, a streamlined audit approach for high-risk claims, and a calibrated trust level for my different research tasks? | fail→fail | 31,520 | 25,413 | -19% | 1 | 1 | 0% | 4,436 | 4,291 | -3% | 0 | 0 | — |
▸case-02 I regularly use LLMs for writing Python scripts, generating cloud infrastructure configs, and debugging API integrations. Recently, an AI gave me a deprecated function from a library update that broke our staging build, costing me hours of debugging. The impact of a bad script can cause deployment downtime, and currently I am way too trusting with code snippets that look polished. Please give me an analysis of where AI fails in coding tasks, the subtle indicators or signals that give away a mistake, how to navigate overly confident answers, a quick verification workflow for risky scripts, and a calibrated trust plan for different dev tasks. | fail→fail | 30,235 | 21,841 | -28% | 1 | 1 | 0% | 3,836 | 3,739 | -3% | 0 | 0 | — |
▸case-03 I work as a financial analyst using AI to digest quarterly earnings reports, run quick unit economics calculations, and draft client memos. A few weeks ago, an AI confidently messed up a multi-step compound growth rate calculation while sounding entirely certain, which almost derailed a client deck. Since client trust and regulatory compliance are on the line, missing a mistake is very costly, though I currently alternate between complete cynicism and total reliance depending on my workload. Please provide a customized guide detailing the specific failure modes relevant to financial analysis, the giveaway signals to spot them quickly, how to address uniformly confident tone, a rapid verification method for high-risk figures, and a realistic trust calibration across my tasks. | fail→pass | 36,940 | 22,244 | -40% | 1 | 1 | 0% | 5,130 | 3,796 | -26% | 0 | 0 | — |
▸case-04 I am building an automated evaluation pipeline using MMLU and GSM8K benchmarks to measure LLM accuracy across model releases. How should I structure the Python script using the `lm-evaluation-harness` library to execute these evaluations and log scores to MLflow? | pass→pass | 25,519 | 37,197 | +46% | 1 | 1 | 0% | 4,238 | 6,745 | +59% | 0 | 0 | — |
▸case-05 We want to reduce factual errors in our internal customer support bot by fine-tuning a Qwen 2.5 7B model using QLoRA. What hyperparameters (learning rate, rank r, alpha) and data formatting should we use in Hugging Face TRL SFTTrainer? | pass→pass | 24,750 | 40,303 | +63% | 1 | 1 | 0% | 4,019 | 7,087 | +76% | 0 | 0 | — |
▸case-06 Our RAG system is returning irrelevant chunks from Elasticsearch, causing answer hallucination. Should we switch from BM25 sparse search to hybrid search with dense embeddings and a BGE reranker, and how do we implement the reranking step in Python? | pass→pass | 22,349 | 46,229 | +107% | 1 | 1 | 0% | 3,303 | 8,193 | +148% | 0 | 0 | — |
▸case-07 I'm worried about AI getting things wrong in my daily work. Can you make me a guide on how to spot AI errors? | fail→pass | 22,571 | 5,652 | -75% | 1 | 1 | 0% | 2,552 | 1,866 | -27% | 0 | 0 | — |
▸case-08 I draft enterprise proposal responses using AI. Yesterday I asked 'Don't you agree that our 99.9% uptime SLA is superior to AWS standard EC2 terms?' and the AI instantly agreed and wrote a pitch claiming AWS only offers 99.0% (which is false). I almost sent it to a prospect. Can you build an error-spotting guide for RFP writing that highlights why AI agreed so fast, how to catch leading-question traps, and how to verify competitor SLA claims? | fail→fail | 25,926 | 25,822 | -0% | 1 | 1 | 0% | 3,429 | 3,561 | +4% | 0 | 0 | — |
▸case-09 As a corporate paralegal, I use AI to summarize indemnification clauses in vendor agreements. Last week, AI cited a non-existent state supreme court precedent with an exact case volume and page number, sounding completely authoritative. What are the failure patterns for legal analysis, the giveaway signals for fake precedents, how to handle the authoritative tone, a rapid verification protocol for liability terms, and a domain trust model? | fail→fail | 28,118 | 24,385 | -13% | 1 | 1 | 0% | 3,678 | 3,520 | -4% | 0 | 0 | — |
▸case-10 I use AI to generate practice math problems and step-by-step solutions for high school algebra students. An AI recently provided a beautifully formatted 6-step quadratic formula solution that contained an arithmetic subtraction error in step 3, but concluded with a clean round integer answer that looked totally correct. How do I build a mistake-detection plan for math problem generation, spot arithmetic slips, avoid the confidence trap, and establish verification checks? | fail→fail | 15,548 | 26,500 | +70% | 1 | 1 | 0% | 2,593 | 3,755 | +45% | 0 | 0 | — |
▸case-11 I write technology news reports using AI to summarize recent tech industry press releases and earnings calls. In a recent article draft, AI reported an outdated CEO name from 2022 as current, stating it with total certainty. High accuracy is essential for news credibility. Please provide a mistake-spotting guide for tech journalism detailing outdated fact signals, uniform tone warnings, fast checks for high-risk facts, and domain calibration. | fail→fail | 23,203 | 21,233 | -8% | 1 | 1 | 0% | 3,511 | 3,327 | -5% | 0 | 0 | — |
▸case-12 I generate Terraform scripts and Kubernetes manifests with AI. Recently an AI generated an AWS IAM policy with an obsolete syntax block that caused a silent security misconfiguration in staging. I usually copy-paste code if it looks well-indented. Give me a custom mistake guide for infrastructure-as-code, including deprecated syntax signals, navigating polished output, verification checks for high-stakes IAM policies, and task trust levels. | fail→fail | 28,950 | 24,011 | -17% | 1 | 1 | 0% | 3,840 | 3,508 | -9% | 0 | 0 | — |
▸case-13 I use AI to write Pandas data transformation pipelines. An AI script performed an inner join instead of a left join, silently dropping 15% of our customer records while outputting clean, error-free execution logs. How can I map failure modes for data engineering tasks, catch subtle logical errors, address confident output, and set up a fast audit pipeline? | fail→fail | 21,237 | 21,820 | +3% | 1 | 1 | 0% | 3,381 | 3,703 | +10% | 0 | 0 | — |
▸case-14 I manage marketing copywriting and brand communications. AI generated a blog draft that included false statistical claims about industry growth rates, presented in a polished, persuasive voice that almost tricked our copy editor. I need an error-spotting guide for marketing copywriting that covers false precision, giveaway signals, tone traps, fast checks for marketing claims, and calibrated trust. | fail→fail | 24,758 | 21,079 | -15% | 1 | 1 | 0% | 3,783 | 3,406 | -10% | 0 | 0 | — |
▸case-15 I analyze security logs and write incident response summaries using AI. An AI once suggested an outdated log analysis command syntax for Splunk that produced zero search results, leading us to believe there was no breach when there actually was. Please structure a failure analysis guide for incident response, noting syntax tells, uniform confidence warnings, quick verification for threat logs, and calibrated trust across security tasks. | fail→fail | 38,329 | 15,208 | -60% | 1 | 1 | 0% | 4,448 | 3,315 | -25% | 0 | 0 | — |
▸case-16 I draft HR policies and employee handbooks with AI assistance. Last month, AI drafted a leave policy that referenced obsolete state labor laws, sounding completely authoritative and legal. What are the failure patterns in HR policy drafting, the tells for outdated statutory references, how to bypass the tone trap, a fast check for legal compliance, and domain trust recommendations? | fail→fail | 24,167 | 18,635 | -23% | 1 | 1 | 0% | 3,457 | 3,722 | +8% | 0 | 0 | — |
▸case-17 I curate internal knowledge base articles for customer support agents. An AI generated a troubleshooting guide for our SaaS product that included imaginary settings menu options that don't exist in our current software version. Please build an error-spotting guide for SaaS documentation, identifying imaginary feature tells, uniform confidence alerts, high-risk workflow checks, and task trust levels. | fail→fail | 26,669 | 15,828 | -41% | 1 | 1 | 0% | 3,474 | 3,365 | -3% | 0 | 0 | — |
▸case-18 I write academic history papers using AI to organize background research on 19th-century diplomatic relations. AI confidently attributed a quote to Bismarck that was actually written by a 20th-century historian. How do I spot historical quote hallucinations, avoid tone traps, quickly audit cited sources, and calibrate trust in history research? | fail→fail | 22,411 | 15,856 | -29% | 1 | 1 | 0% | 3,083 | 3,474 | +13% | 0 | 0 | — |
▸case-19 I prepare regulatory filings for pharmaceutical clinical trials. An AI draft hallucinated a specific FDA guidance document number and misstated trial phase statistical power thresholds, which could result in regulatory rejection. Prepare a failure spotting guide for FDA regulatory drafting covering fake guidance numbers, giveaway signals, confidence warnings, high-stakes verification methods, and domain calibration. | fail→fail | 37,245 | 21,939 | -41% | 1 | 1 | 0% | 5,682 | 3,775 | -34% | 0 | 0 | — |
▸case-20 I perform commercial real estate appraisals using AI to summarize local zoning laws and comparable property sales. AI stated that a commercial property parcel was zoned for mixed-use residential when it was actually strictly industrial, citing a plausible-sounding municipal code number. Give me a failure spotting guide for commercial real estate, detailing zoning hallucination tells, tone warnings, high-risk verification for property data, and task trust. | fail→pass | 27,612 | 20,339 | -26% | 1 | 1 | 0% | 3,482 | 3,861 | +11% | 0 | 0 | — |
▸case-21 I optimize global shipping routes and customs compliance using AI. An AI generated customs clearance documentation with an invalid HS (Harmonized System) tariff code, which caused a shipment delay at port. Create a mistake-spotting guide for logistics management covering tariff code errors, tells, confidence traps, fast verification for customs docs, and calibrated trust. | fail→fail | 25,241 | 16,971 | -33% | 1 | 1 | 0% | 3,821 | 3,464 | -9% | 0 | 0 | — |
▸case-22 I design science curriculum materials for middle school teachers. AI generated a lesson plan on photosynthesis that confused light-dependent and light-independent reactions while sounding expert and encouraging. What are the failure modes in science curriculum generation, giveaway signals for concept confusion, how to handle polite/confident tone, fast checks for lesson plans, and trust levels? | fail→fail | 20,841 | 22,173 | +6% | 1 | 1 | 0% | 3,053 | 4,265 | +40% | 0 | 0 | — |
▸case-23 I design commercial buildings and use AI to reference ADA accessibility guidelines and local building codes. AI misstated the required minimum hallway width for wheelchair clearance by 6 inches while citing standard code formatting. Build an error-spotting guide for architectural compliance, including code slip tells, tone traps, rapid checks for high-risk dimensions, and domain trust. | fail→fail | 24,039 | 16,797 | -30% | 1 | 1 | 0% | 3,649 | 3,327 | -9% | 0 | 0 | — |
▸case-24 I write Unity C# gameplay scripts using AI. An AI generated a vector calculation for character movement that worked fine in simple testing but caused floating point overflow during long gaming sessions. How can I spot Unity scripting failure modes, catch subtle physics/math bugs, avoid polished code traps, check critical scripts fast, and calibrate trust across game systems? | fail→fail | 29,163 | 19,285 | -34% | 1 | 1 | 0% | 3,750 | 4,011 | +7% | 0 | 0 | — |
▸case-25 I write grant proposals for a non-profit environmental organization. AI hallucinated demographic statistics about our service region in a federal grant application. Please construct a mistake-spotting guide for grant writing detailing demographic data tells, uniform tone cautions, fast checks for grant applications, and calibrated trust. | fail→fail | 23,001 | 18,251 | -21% | 1 | 1 | 0% | 3,375 | 3,471 | +3% | 0 | 0 | — |
▸case-26 I work in internal audit and use AI to generate audit sampling methodology descriptions and statistical risk models. AI recommended an inadequate sample size calculation for revenue testing, using an incorrect formula while sounding authoritative. Please provide a guide covering audit calculation errors, giveaway signals, confidence trap warnings, rapid checks for high-risk audit steps, and trust calibration. | fail→fail | 29,337 | 19,980 | -32% | 1 | 1 | 0% | 4,278 | 3,889 | -9% | 0 | 0 | — |