Turns a described spreadsheet calculation into a working Excel formula plus a plain-language walkthrough of every function, operator and reference it uses.
Version 1 · 3 variables · 2 required
Fill in the values below — the customized prompt updates as you type. marks a required value.
What the formula should work out, in plain language. e.g. "total revenue per sales rep for Q4 2025 shipped orders only".
Sheet names, column letters and row ranges the formula will read, plus where the result goes.
Excel version, error handling, performance limits, anything the formula must or must not do. Default: must be robust to blank cells and return 0 instead of an error
Fill in Calculation you want, Input data / cell references to copy the customized prompt.
Showing all 1 public result on version 1.
Contributor notes: Illustrative example — not an actual model run. Written to show the shape of a good answer so the prompt can be judged before you spend a call on it. Attribution: adapted from https://github.com/f/prompts.chat by f (Fatih Kadir Akın), licensed CC0-1.0. Source file: https://github.com/f/prompts.chat/blob/main/PROMPTS.md
Reports go to moderators and are never shown publicly.
```csv quarter,line,units_produced,defects,defect_rate_pct,shift_pattern Q1,Line A,14200,318,2.24,"Two shifts, weekdays" Q1,Line B,11850,402,3.39,"Two shifts, weekdays" Q1,Line C,9600,151,1.57,"One shift, weekdays" Q1,Line D,UNCLEAR,88,UNCLEAR,"One shift, weekends" Q2,Line A,15040,295,1.96,"Three shifts, weekdays" Q2,Line B,12310,377,3.06,"Two shifts, weekdays" Q2,Line C,9880,143,1.45,"One shift, weekdays" Q2,Line D,4120,96,2.33,"One shift, weekends" ``` **Notes** - **UNCLEAR cells:** row 5 (Q
Extracts a table from a screenshot or scanned page into a flat, copy-paste-ready CSV, unmerging cells, stripping units into their own columns and flagging anything unreadable instead of guessing.
# Checkout redesign A/B test — analysis plan and interpretation ## What the design supports Two independent groups, roughly 6,200 per arm, with a binary primary outcome (completed purchase) and a continuous secondary outcome (order value, right-skewed as order values almost always are). Randomisation at the session level with a 21-day run covering three full weekly cycles is sound. One caveat that limits every conclusion below: sessions, not users, were randomised, so a returning visitor could
Applies a senior statistician's workflow to your data: descriptive summary, justified test selection, models, effect sizes with confidence intervals, and a plain-language reading of what is practically significant.
## 1. Technical Audit & Business Context | Column | Smell | Business impact | |---|---|---| | `churn_date` | Populated only for churned accounts | This is the label in disguise. Any model that sees it will score ~perfectly in training and be useless in production. | | `mrr` | Right-skewed, a long tail of enterprise accounts | Mean imputation would drag small accounts upward and understate churn risk in the SMB segment, which is where outreach capacity actually sits. | | `signup_date` | Mixed `Y
Audits a raw dataset for data smells, ties each issue to its business impact, then proposes an imputation, encoding and scaling strategy with a leakage-safe pandas and scikit-learn pipeline.
Converts a natural-language data requirement plus a table schema into a syntactically correct SQL query for a named database, with its assumptions stated up front.
Oldest first · one level of replies
Sign in to join the discussion. Share what you learned or made with this prompt.
No comments yet
Be the first to share how this prompt worked for you.