Update to Formula Genius
Snapshot Nov 9, 2026 · 00:12 UTC · version 1.4.0
Collection source: downloaded plugin package.
Instructions updated for diagnose-formula
Full description — Now says: Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior. Do not use for writing a...
Observed in instructions or declared skills. Runtime behavior has not been tested.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Oct 24, 2026 · 12:51 UTC
Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior.
Nov 9, 2026 · 00:12 UTC
Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior. Do not use for writing a new formula from scratch (lookup-and-match-formulas, version-aware-formula) or s...
Skill instructions
Oct 24, 2026 · 12:51 UTC
description: "Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior."
Nov 9, 2026 · 00:12 UTC
description: "Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior. Do not use for writing a new formula from scratch (lookup-and-match-formulas, version-aware...
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,6 +1,6 @@ --- name: diagnose-formula -description: "Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior." +description: "Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior. Do not use for writing a new formula from scratch (lookup-and-match-formulas, version-aware-formula) or scanning a whole attached file (check-workbook-health)." --- Use `explain_formula` for explanation-only requests. For repair requests, collect the formula, error (if any), and intended result; use `debug_formula` with `formula`, optional `error`, and `expected`. Include relevant application/version context and a small user-provided expected-versus-observed example in the expected-behavior text when useful.
Full technical diff · 2 changed fields
changed /description
"Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior."
"Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior. Do not use for writing a new formula from scratch (lookup-and-match-formulas, version-aware-formula) or scanning a whole attached file (check-workbook-health)."
changed /skill_md_contents
"---\nname: diagnose-formula\ndescription: \"Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior.\"\n---\n\nUse `explain_formula` for explanation-only requests. For repair requests, collect the formula, error (if any), and intended result; use `debug_formula` with `formula`, optional `error`, and `expected`. Include relevant application/version context and a small user-provided expected-versus-observed example in the expected-behavior text when useful.\n\nThe debug tool proposes a correction; it does not run those examples as tests. Do not invent a `samples` parameter or a `repair_formula` tool. Distinguish the proposed correction from verified behavior and explain the material change. If the user wants to compare two alternatives, use `compare_formulas` with `formulaA`, `formulaB`, `description`, and `criteria`.\n\nWhen the user supplies explicit sample cells and expected answers, use `check_formula_samples` with `formula`, `platform` (`excel` or `sheets`), `intendedResult`, and `sampleCases` containing `{label?, cells, expected}`. Up to three cases are allowed, with at most 100 supplied cells within A1–Z100 each. Expected answers must be supplied or approved by the user: preserve numbers, text, booleans and null distinctly; do not invent missing cells or replace an expectation with the formula's actual output. Report each returned `sample_matched`, `sample_mismatch`, `unsupported`, or `not_checked` status and its actual/expected values or unsupported reason. This authenticated deterministic checker makes no generation-model call and neither saves work nor executes Excel/Sheets. Do not describe it as a full-workbook verification.\n\nFor requested broader generated-case verification without explicit expected samples, use `validate_formula` with the proposed formula and intended behavior. That existing tool has its own allowance and scope; the sample checker is not a fallback to evade its quota denial. Respect authentication/entitlement responses and report actual coverage, including unsupported functions. Do not turn a prediction into a passed test or claim the workbook was changed. Ask for minimal non-sensitive examples rather than requesting an entire confidential workbook. Create a share link only when explicitly requested.\n""---\nname: diagnose-formula\ndescription: \"Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior. Do not use for writing a new formula from scratch (lookup-and-match-formulas, version-aware-formula) or scanning a whole attached file (check-workbook-health).\"\n---\n\nUse `explain_formula` for explanation-only requests. For repair requests, collect the formula, error (if any), and intended result; use `debug_formula` with `formula`, optional `error`, and `expected`. Include relevant application/version context and a small user-provided expected-versus-observed example in the expected-behavior text when useful.\n\nThe debug tool proposes a correction; it does not run those examples as tests. Do not invent a `samples` parameter or a `repair_formula` tool. Distinguish the proposed correction from verified behavior and explain the material change. If the user wants to compare two alternatives, use `compare_formulas` with `formulaA`, `formulaB`, `description`, and `criteria`.\n\nWhen the user supplies explicit sample cells and expected answers, use `check_formula_samples` with `formula`, `platform` (`excel` or `sheets`), `intendedResult`, and `sampleCases` containing `{label?, cells, expected}`. Up to three cases are allowed, with at most 100 supplied cells within A1–Z100 each. Expected answers must be supplied or approved by the user: preserve numbers, text, booleans and null distinctly; do not invent missing cells or replace an expectation with the formula's actual output. Report each returned `sample_matched`, `sample_mismatch`, `unsupported`, or `not_checked` status and its actual/expected values or unsupported reason. This authenticated deterministic checker makes no generation-model call and neither saves work nor executes Excel/Sheets. Do not describe it as a full-workbook verification.\n\nFor requested broader generated-case verification without explicit expected samples, use `validate_formula` with the proposed formula and intended behavior. That existing tool has its own allowance and scope; the sample checker is not a fallback to evade its quota denial. Respect authentication/entitlement responses and report actual coverage, including unsupported functions. Do not turn a prediction into a passed test or claim the workbook was changed. Ask for minimal non-sensitive examples rather than requesting an entire confidential workbook. Create a share link only when explicitly requested.\n"Full snapshot data
{
"description": "Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior. Do not use for writing a new formula from scratch (lookup-and-match-formulas, version-aware-formula) or scanning a whole attached file (check-workbook-health).",
"included_files": [
{
"relative_path": "agents/openai.yaml",
"size_in_bytes": 222
}
],
"name": "diagnose-formula",
"skill_md_contents": "---\nname: diagnose-formula\ndescription: \"Explain or debug an Excel or Google Sheets formula that produces an error or unexpected result, using the user's expected behavior. Do not use for writing a new formula from scratch (lookup-and-match-formulas, version-aware-formula) or scanning a whole attached file (check-workbook-health).\"\n---\n\nUse `explain_formula` for explanation-only requests. For repair requests, collect the formula, error (if any), and intended result; use `debug_formula` with `formula`, optional `error`, and `expected`. Include relevant application/version context and a small user-provided expected-versus-observed example in the expected-behavior text when useful.\n\nThe debug tool proposes a correction; it does not run those examples as tests. Do not invent a `samples` parameter or a `repair_formula` tool. Distinguish the proposed correction from verified behavior and explain the material change. If the user wants to compare two alternatives, use `compare_formulas` with `formulaA`, `formulaB`, `description`, and `criteria`.\n\nWhen the user supplies explicit sample cells and expected answers, use `check_formula_samples` with `formula`, `platform` (`excel` or `sheets`), `intendedResult`, and `sampleCases` containing `{label?, cells, expected}`. Up to three cases are allowed, with at most 100 supplied cells within A1–Z100 each. Expected answers must be supplied or approved by the user: preserve numbers, text, booleans and null distinctly; do not invent missing cells or replace an expectation with the formula's actual output. Report each returned `sample_matched`, `sample_mismatch`, `unsupported`, or `not_checked` status and its actual/expected values or unsupported reason. This authenticated deterministic checker makes no generation-model call and neither saves work nor executes Excel/Sheets. Do not describe it as a full-workbook verification.\n\nFor requested broader generated-case verification without explicit expected samples, use `validate_formula` with the proposed formula and intended behavior. That existing tool has its own allowance and scope; the sample checker is not a fallback to evade its quota denial. Respect authentication/entitlement responses and report actual coverage, including unsupported functions. Do not turn a prediction into a passed test or claim the workbook was changed. Ask for minimal non-sensitive examples rather than requesting an entire confidential workbook. Create a share link only when explicitly requested.\n"
}SHA-256 of public snapshot: 0f495e32dd385bd989594a2e793c29ca1c4b1abd596171e45e293a1185b60a68