Checks every chart in the open workbook against what its title and labels claim: truncated or inverted axes, inconsistent scales across a set, missing baselines, a series whose range does not match the data it claims, dual axes that imply a relationship, and colours carrying unexplained meaning. Changes nothing. Use when the user asks to review charts before a deck, a pack or a publication.
Sweeps a data range in the open workbook for conditions that break reporting: mixed types in a column, numbers and dates stored as text, duplicates on the apparent key, inconsistent category spellings, out of range values, blanks that are meaningful, and inconsistent date formats. Corrects nothing. Use when the user asks to check data quality, find problems in a dataset, or audit a table before analysis.
Builds one decision slide that sets out the question, the options, the criteria, a comparison, the recommended option with its risks, and the decision required from a named owner by a date, labelled DRAFT and built only after the user approves the content. Use when the user asks for a decision slide, options slide, recommendation slide or a slide asking a committee or sponsor to decide.
Sweeps the open presentation for the inconsistencies a reader notices and an author stops seeing: a term used two ways, acronyms never expanded, mixed date and number formats, product names spelled differently, and headings that change grammatical shape. Proposes fixes and applies none without approval. Use when the user asks to proofread, tidy or make a deck consistent before it goes out.
Reads a whole deck and reports whether it carries one message, whether the slides support it in order, and whether it ends with a clear ask. Names the message the deck actually makes, which is often not the one the author intended, and lists every slide that does not serve it. Reports only; changes nothing. Use when the user asks whether a deck lands, hangs together, has a storyline, makes its point, or is ready to present.
Proposes which slides to cut, merge or move to an appendix so a deck fits its slot and its argument, using repetition, slides carrying no message, and slides that do not support the stated conclusion as the criteria. Deletes nothing. Use when the user says a deck is too long, needs to fit a time slot, or asks what can be cut. Not for relocating detail to an appendix; use appendix-split for that.
Reads the whole open presentation and drafts one executive summary slide of three to five points, each traced to the slide it comes from, then inserts it after the title slide once the user approves. Use when the user asks for an executive summary, leadership overview, one-slide recap or TL;DR slide of a deck.
Reviews the formulas in the open workbook for the faults that silently produce wrong answers: constants typed inside expressions, ranges that stop short of their block, inconsistent formulas across a row, volatile and fragile functions, and error values hidden behind IFERROR. Changes no formula. Use when the user asks to review, audit or sanity-check the formulas or the build quality of a spreadsheet. Not for tracing one output cell back to its inputs; use model-map for that.
Checks every lookup in the open workbook for the faults that return a wrong row rather than an error: approximate match left on by default, duplicate keys on the lookup side, keys that exist in one table and not the other, mismatched types, and ranges that shift when rows are inserted. Changes nothing. Use when the user asks to check lookups, joins, references between tables, or why two sheets disagree.
Traces the calculation chain behind a chosen output cell in the open workbook, back through every intermediate step to the inputs it ultimately depends on, and reports the path, the sheets crossed, and anything that breaks the chain such as hardcoded overrides or external references. Changes nothing. Use when the user asks how a number is calculated, what drives it, or what would change if an input moved. Not for reviewing every formula in the workbook; use formula-risk-review for that.
Turns pasted content into diagram slides built from native PowerPoint shapes and connectors, in the deck's own theme. Offers a menu of ten layouts (process, timeline, cycle, hierarchy, matrix, funnel, hub and spoke, layered stack, comparison, grouped boxes), proposes one per slide, waits for approval, then draws editable shapes, never a picture and never SmartArt. Use when the user asks for a diagram, process flow, timeline, roadmap, cycle, org chart, 2x2, funnel, architecture or 'make this visual', or builds a deck from pasted content.
Audits the open presentation for every number, date, percentage, quote and factual claim, records where each appears and whether a source is given, and lists unsourced or inconsistent items for the presenter to resolve. Never changes a figure. Use when the user asks to fact-check, verify numbers, check sources or audit claims in a deck before it is presented or sent.
Drafts a numbered slide outline from a brief or source document, waits for the user to approve or edit it, and only then builds the slides. Use when the user asks to create, draft or start a presentation or deck from notes, a brief, a document or a topic, and the content matters more than speed.
Re-adds every stated total in the open workbook against its components, checks that cross-sheet figures agree, and lists each line that does not tie with both values and their cell references. Never changes a number. Use when the user asks to tie out, reconcile, cross-check or verify that totals in a spreadsheet add up before it is sent or reported. Not for unit, scaling or currency mixing; use units-and-rounding-check for that.
Builds a base, downside and upside scenario scaffold wired to the workbook's existing input cells, with a single switch driving which case is live, and leaves every scenario value blank for the user to populate. Invents no assumption. Use when the user asks to add scenarios, sensitivities or cases to a model that currently holds one set of numbers.
Drafts speaker notes for each slide in the open presentation from what the slide actually shows, marks where a note would need a fact the slide does not contain, and flags any existing note that contradicts its slide. Adds nothing to the slides themselves. Use when the user asks for speaker notes, talk track, or help preparing to present a deck.
Builds a short steering committee status deck (overall RAG status with reasons, milestones, risks and issues, budget if supplied, decisions and asks) from a status report, tracker export or notes, labels it DRAFT, and builds slides only after the user approves the status summary. Use when the user asks for a status update deck, steering committee pack, project board slides or monthly programme update.
Checks the open workbook for unit and rounding faults: thousands mixed with millions, more than one currency added together, percentages stored inconsistently, displayed rounding that makes totals appear not to add, and hardcoded conversion factors. Changes no value. Use when the user asks to check units, scaling, currency consistency, or why a total looks one out. Not for re-adding totals against their components; use reconciliation-check for that.
Explains the movement between two periods or between plan and actual in the open workbook by splitting it into the drivers the data supports, reconciling the named drivers back to the total, and reporting the remainder as unexplained rather than attributing it. Invents no driver. Use when the user asks why a number moved, to bridge two periods, or to explain a variance.
Writes the note that should have been in the file: what the workbook is for, which sheet to start on, where the inputs are, what is calculated, what must be refreshed and on what cadence, what is known to be fragile, and who to ask. Records only what the workbook evidences. Use when a model is being handed over, archived, or picked up by somebody new.
A folder with a SKILL.md file: a name, a description of when to use it, and instructions. Claude loads a skill only when the task matches its description.
How do I use one I find here?
Copy the folder into your project's .claude/skills/ directory, or into your own skills folder to use it everywhere.
What do the warnings mean?
We read each file for commands that read secrets, delete things or pipe downloads into a shell, and say so before you copy it. No warning is not a promise that a file is safe.
Which skills worked for people?
Open a skill to see its discussion. Reports from people and their agents are coming.
kesslernitySkill