Sigma Workbook QA
A Claude skill for the last check before a Sigma workbook is shared. It looks at every page, names the defects, ties headline numbers to the warehouse and signs off on the published version.
Runs in your own Claude account
What it does
- 1Asks whether there is a benchmark to compare against, who reads the workbook, which numbers matter most and whether to fix or only report.
- 2Renders every page top to bottom and lists defects such as default titles, raw column names, KPIs with no comparison and mixed formats.
- 3Ties out every headline KPI against an independent warehouse query and checks joins for duplicated rows.
- 4Changes every control, tests drill-downs and input tables, and checks embedded views as the viewer.
- 5Fixes or reports the defects, re-renders, and runs the client-ready checklist on the published version.
What it needs
- Access to the published Sigma workbook, through a Sigma MCP connector, a browser or screenshots.
- Read access to the warehouse for tie-out queries.
- The HTML benchmark, if one exists.
Prompts to try
- “QA this Sigma workbook before it goes to the client.”
- “Something looks off on the revenue page. Audit it and tie the numbers to Snowflake.”
- “Check this embedded Sigma dashboard as a guest user and confirm row-level security.”
What you get back: A defect list by page and element, tie-out numbers for each headline KPI, and the client-ready checklist marked pass or fail.
How to install it
- Claude on the web or desktop
- Download the .zip. In Claude, open Settings, find Skills under Capabilities, and upload the file. Then ask Claude one of the prompts above.
- Claude Code
- Unzip the folder into ~/.claude/skills/ so the file sits at ~/.claude/skills/sigma-workbook-qa/SKILL.md. Claude Code picks it up in the next session.
- Read it first
- The skill is a plain text file of instructions. Open SKILL.md to see exactly what it tells Claude to do before you install it.
- Change it
- Edit the definitions or the output format to match how your team counts things. It is yours to adapt.
Common questions
What does the skill check?
Layout and labels on every page, number and date formats, headline numbers against the warehouse, every control and drill-down, input tables, and embedded views as the viewer.
Does it fix problems or only report them?
It asks first. It can report only, or fix the defects in order of impact, starting with wrong numbers, and re-render to confirm each fix.
Why check the published version?
Drafts and edit mode can differ from what a client opens. The skill signs off only on what the reader will actually see.
Want Claude connected to your own data?
We set up read-only access to Snowflake, the curated tables Claude should use, and checks so the answers match your reports.