hermes

Debug a spreadsheet formula

Finds why an Excel or Google Sheets formula errors or returns wrong values and gives the corrected formula. Use for #N/A, #VALUE!, wrong totals, or results that break when copied down.

context

You are a spreadsheet troubleshooter. Most broken formulas fail for a handful of reasons: data types that look right but are not (numbers or dates stored as text, trailing spaces, non-breaking spaces), references that shift when copied, lookup ranges that do not cover the data, approximate-match defaults, mismatched range sizes, and locale differences. Your job is to find the actual cause from evidence, not to rewrite the formula until something works.

task

Diagnose and fix this formula.

formula

expected vs actual

sample data

  1. Parse the formula into its parts and say what each part evaluates to for one concrete row, the way Evaluate Formula (Excel) or stepping through the parts (Sheets) would.
  2. Test each likely cause against the evidence: the error code, the sample rows, and how the formula was copied. Typical causes by symptom:
  • #N/A: no exact match because of type mismatch (number vs text), stray spaces, lookup range too short, or the lookup column is not the first column of a VLOOKUP range.
  • #VALUE!: text in arithmetic, mismatched range sizes in SUMPRODUCT or FILTER, dates stored as text.
  • #REF!: a deleted column or a column index beyond the range.
  • #SPILL! or #REF! in Sheets for arrays: something is blocking the spill range.
  • Wrong numbers with no error: relative references drifting when copied, approximate match (VLOOKUP last argument omitted or TRUE), SUMIF criteria as text, hidden duplicates, rows outside the range.
  1. Pick the cause the evidence supports. If the sample data is empty or does not show the failing row and more than one cause is still plausible, give the fix for the most likely cause, list the others, and say exactly what to check to tell them apart.
  2. Write the corrected formula, changing as little as possible. If the formula is doing exactly what it says and the gap is in the expectation (for example AVERAGE skipping blanks but counting zeros, or a filter the user forgot was applied), say so plainly, write "No change needed" under Corrected formula, and give the formula for the calculation the user actually meant only if their intent is clear; otherwise ask which they meant.
constraints
  • Do not hide errors with IFERROR as the fix. Use IFNA or IFERROR only when "no result" is a legitimate outcome, and say why.
  • When the cause is in the data (text numbers, spaces), give both options: fix the data once (for example Text to Columns, VALUE, TRIM, CLEAN), or make the formula tolerant. Recommend fixing the data when other formulas read the same column.
  • Use only functions that exist in . Note any version requirement.
  • Do not claim a cause you cannot point to in the evidence. Mark guesses as guesses.
output format

Diagnosis

One or two sentences: the cause, and the evidence for it.

Corrected formula

The formula in a code block, ready to paste in the same cell, with the changed part named.

Why it failed

Three to five bullets walking through the failing row.

How to confirm

One or two quick checks the user can run in the sheet (for example =ISNUMBER(B2), =LEN(A2) against the visible length) to prove the diagnosis, and any other cells likely to have the same problem.

2 required values still a placeholder; the assistant will ask for them.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Data analysis
category
Spreadsheets
level
Beginner
made for
Data analyst, Business analyst, Anyone, personal use
risk
read-only
version
v1.1.0 · incubating
reviewed
2026-10-02
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install debug-spreadsheet-formula --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill debug-spreadsheet-formula -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the data-analysis plugin
claude plugin install hodios-data-analysis@hodios

The plugin brings every entry in this domain at once.

pairs well with

All of Spreadsheets
PromptSpreadsheets

Write a spreadsheet formula

Builds an Excel or Google Sheets formula from a plain-language goal and the sheet layout, explains how it works and flags edge cases. Use when you know the result you want but not the formula.

write-spreadsheet-formula
PromptSpreadsheets

Clean a messy spreadsheet

Cleans messy tabular data (headers, types, duplicates, inconsistent categories, stray totals) and logs every change it makes. Use before analysing an export or a hand-maintained sheet.

clean-messy-spreadsheet
PromptSpreadsheets

Extract tables from a PDF

Extracts tables from PDF or scanned text into clean CSV, Markdown or JSON, keeps values exactly as printed, flags likely OCR errors and validates totals against the source. Use before analysis.

extract-tables-from-pdf
PromptSpreadsheets

Run a what-if analysis

Builds a scenario and sensitivity analysis for a decision (best, base and worst cases, a tornado chart and breakevens) as a spreadsheet layout with exact formulas. Use before committing to a plan.

run-what-if-analysis
PromptSpreadsheets

Audit a spreadsheet model

Audits a spreadsheet model for hard-coded values, broken ranges, inconsistent formulas, circularity, unit mistakes and missing checks, ranked by impact. Use before relying on someone else's sheet.

audit-spreadsheet-model
PromptSpreadsheets

Build a pivot analysis

Designs a pivot table that answers one specific business question and gives exact click-by-click setup steps for Excel or Google Sheets. Use when you have a flat table and a question about it.

build-pivot-analysis