hermes
26 entries · 24 prompts, 2 personas

Data exploration

Exploratory analysis: profiling a dataset, finding patterns and anomalies, analyst SQL.

  • Reconcile two datasets

    Reconciles two datasets that should agree, such as bank versus ledger or CRM versus billing, by matching records, listing mismatches and explaining likely causes. Use for month-end checks.

  • Write a dataframe transformation

    Writes pandas or polars code for a described transformation with built-in checks on row counts, nulls, key uniqueness and join cardinality. Use when reshaping, joining or aggregating data.

  • Analyse an employee engagement survey

    Analyses an employee engagement survey with group scores under minimum-group-size privacy rules, eNPS, comment themes and three priorities to act on. Use after an engagement or pulse survey closes.

  • Analyse location data

    Analyses location data for stores, customers or deliveries to find catchments, density and distance patterns, with the method, code and mapping guidance. Use for site, coverage or delivery questions.

  • Compare marketing attribution models

    Compares last-click, first-click, linear, position-based and data-driven attribution on supplied channel data and explains what each implies for budget. Use before moving marketing spend.

  • Analyse sales performance

    Analyses sales data by product, customer, region and time to find what drives revenue, seasonality, best and worst performers, and the actions worth taking. Use for a sales performance review.

  • Analyse survey results

    Analyses quantitative survey responses with cleaning, tabulation, cross-tabs and optional weighting, and states the caveats about sample and response bias. Use before reporting survey numbers.

  • Analyse website analytics

    Analyses website analytics (GA4 or similar) for traffic sources, landing pages, engagement and conversion, flags tracking problems first and gives prioritised actions. Use as a marketer or site owner.

  • Anonymise a dataset before sharing

    Plans anonymisation or pseudonymisation of a dataset before sharing, classifying identifiers, choosing techniques and assessing re-identification and residual risk. Use before data leaves your team.

  • Answer a question with SQL

    Turns a business question and a schema into an analytical SQL query, states the assumptions behind it and explains how to read the result. Use when you know the question but not the query.

  • Build a cohort retention analysis

    Builds a cohort retention analysis from event data (cohort definition, query or code, the retention triangle) and explains how to read it. Use to see whether newer customers stick around better.

  • Classify text records

    Classifies free-text records such as tickets, feedback or expenses into a given set of categories, with a confidence level and an explicit Other bucket, and returns a table.

  • Data analyst

    Acts as a data analyst who starts from the decision, sanity-checks data before trusting it and states uncertainty plainly. Use as a standing analyst persona or subagent for data questions.

  • Data scientist

    Acts as a data scientist who frames the decision first, uses the simplest valid method, validates out of sample and communicates uncertainty plainly. Use for modelling, prediction and experiment work.

  • Decompose a revenue change

    Breaks a revenue or sales change into price, volume and mix effects, and into new, lost and retained customers, with the arithmetic shown and reconciled. Use to explain why revenue moved.

  • Deduplicate messy records

    Plans and writes matching logic to deduplicate people, companies or products across messy records, with normalisation, blocking, fuzzy thresholds, merge rules and a review queue. Use for CRM cleanup.

  • Detect anomalies in data

    Finds anomalies in a metric or dataset with methods that fit its shape (thresholds, seasonality, robust z-scores), ranks them, and separates data errors from real events. Use when monitoring data.

  • Explore a dataset

    Runs a first-pass exploratory analysis of a dataset (column profiles, missingness, distributions, outliers) and lists the questions worth asking next. Use when you get new data.

  • Extract fields from documents into a table

    Extracts named fields such as dates, amounts, names and IDs from emails, invoices or letters into a table, leaving blanks where a value is absent rather than guessing. Use to turn paperwork into data.

  • Find churn drivers

    Finds which behaviours and attributes predict churn in customer data, simple comparisons first and a model only if justified, with an action and a test per driver. Use at subscription businesses.

  • Review analytical SQL

    Reviews an analytical SQL query for logic errors that give wrong numbers, such as join fan-out, misplaced filters, NULLs, double counting and date or time-zone boundaries. Use before sharing results.

  • Run a market basket analysis

    Runs market basket analysis on transactions to find products bought together, explains support, confidence and lift, and suggests bundles or placement to test. Use for retail and e-commerce.

  • Run a Pareto (80/20) analysis

    Runs a Pareto analysis on products, customers, defects or causes, with the cumulative table, chart instructions and which vital few to act on. Use to find where effort will pay off most.

  • Segment customers

    Proposes and builds a customer segmentation (RFM, rules or clustering) with interpretable segment profiles and a suggested action for each. Use to target retention, pricing or marketing work.

  • Write an analysis plan

    Writes an analysis plan before touching data, covering the decision, questions, metrics, data, method, comparisons, pitfalls and the result that would change the decision. Use when scoping a request.

  • Write a data request brief

    Turns a vague stakeholder ask into a clear data request with the decision, exact metric definitions, filters, time range, format and deadline, plus open questions. Use when a data ask arrives vague.

Not: building pipelines or tuning queries (data).