Question2report
refraction-ray/xalpha
Turn a natural-language financial question into a polished, self-contained HTML report.
Finds out why a data quality check failed or errored, looks at the rows it matched, and recommends the fix.
Install Debugging Failed Data Quality Checks
$ npx skills add PostHog/posthog-foss --skill debugging-failed-data-quality-checks -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install PostHog/posthog-foss debugging-failed-data-quality-checks --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .claude/skills && cp -r skills-src/products/data_quality/skills/debugging-failed-data-quality-checks .claude/skills/debugging-failed-data-quality-checks && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "debugging-failed-data-quality-checks" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/data_quality/skills/debugging-failed-data-quality-checks into .claude/skills/debugging-failed-data-quality-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-failed-data-quality-checks", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/PostHog/posthog-foss/tree/master/products/data_quality/skills/debugging-failed-data-quality-checksType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add PostHog/posthog-foss --skill debugging-failed-data-quality-checks -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install PostHog/posthog-foss debugging-failed-data-quality-checks --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .agents/skills && cp -r skills-src/products/data_quality/skills/debugging-failed-data-quality-checks .agents/skills/debugging-failed-data-quality-checks && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "debugging-failed-data-quality-checks" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/data_quality/skills/debugging-failed-data-quality-checks into .agents/skills/debugging-failed-data-quality-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-failed-data-quality-checks", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog-foss --skill debugging-failed-data-quality-checks -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install PostHog/posthog-foss debugging-failed-data-quality-checks --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/products/data_quality/skills/debugging-failed-data-quality-checks .cursor/skills/debugging-failed-data-quality-checks && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "debugging-failed-data-quality-checks" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/data_quality/skills/debugging-failed-data-quality-checks into .cursor/skills/debugging-failed-data-quality-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-failed-data-quality-checks", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/PostHog/posthog-foss.git --path products/data_quality/skills/debugging-failed-data-quality-checks--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add PostHog/posthog-foss --skill debugging-failed-data-quality-checks -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install PostHog/posthog-foss debugging-failed-data-quality-checks --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/products/data_quality/skills/debugging-failed-data-quality-checks .gemini/skills/debugging-failed-data-quality-checks && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "debugging-failed-data-quality-checks" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/data_quality/skills/debugging-failed-data-quality-checks into .gemini/skills/debugging-failed-data-quality-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-failed-data-quality-checks", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install PostHog/posthog-foss debugging-failed-data-quality-checksInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add PostHog/posthog-foss --skill debugging-failed-data-quality-checks -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .github/skills && cp -r skills-src/products/data_quality/skills/debugging-failed-data-quality-checks .github/skills/debugging-failed-data-quality-checks && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "debugging-failed-data-quality-checks" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/data_quality/skills/debugging-failed-data-quality-checks into .github/skills/debugging-failed-data-quality-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-failed-data-quality-checks", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add PostHog/posthog-foss --skill debugging-failed-data-quality-checks -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install PostHog/posthog-foss debugging-failed-data-quality-checks --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/PostHog/posthog-foss.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/products/data_quality/skills/debugging-failed-data-quality-checks .opencode/skills/debugging-failed-data-quality-checks && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "debugging-failed-data-quality-checks" agent skill from https://github.com/PostHog/posthog-foss/tree/master/products/data_quality/skills/debugging-failed-data-quality-checks into .opencode/skills/debugging-failed-data-quality-checks/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "debugging-failed-data-quality-checks", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
debugging-failed-data-quality-checks- GitHub stars
- 721
- Token cost
- ~2.1k tokens
- SKILL.md length
- 902 words
- Files
- 1
- Skills in repo
- 213
- Repo updated
- First seen
- Licence
- MIT
At a glance
Finds out why a data quality check failed or errored, looks at the rows it matched, and recommends the fix.
- Works in 5 steps: Read the run → Look at the failing rows → Read an errored run → …
- Asked why a check is red
- SKILL.md covers When to use this skill, Available tools, Workflow and Important notes, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Debugging Failed Data Quality Checks is an agent skill from PostHog/posthog-foss, published by the product's own GitHub organization. Finds out why a data quality check failed or errored, looks at the rows it matched, and recommends the fix. Also covers a materialized view refresh that the data quality gate did not publish. Use when asked why a check is red, what rows failed, why a view shows "Not published", why a view's data is stale after a refresh, or how to get a blocked refresh published. Trigger terms: failed check, failing rows, errored check, data quality failure, not published, blocked materialization, unpublished refresh, check keeps…
Its SKILL.md is about 2.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Data & Analytics, covering Data cleaning. It works with PostHog. The repository describes itself as: PostHog FOSS is a read-only mirror of PostHog, with all proprietary code removed. NOTE: This repo is synced automatically from the main PostHog repo. Please raise any issues and… The licence is MIT.
When your agent uses it
- Asked why a check is red
- What rows failed
- Why a view shows Not published
- Why a views data is stale after a refresh
Example prompts
- “Not published”
- “Use the debugging-failed-data-quality-checks skill to find out why a data quality check failed or errored, looks at the rows it matched, and…”
- “/debugging-failed-data-quality-checks”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 2c48221. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Debugging Failed Data Quality Checks loads about 2.1k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 902 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from PostHog/posthog-foss at commit 2c48221, republished under its MIT licence (© PostHog). 902 words, ~2,052 tokens.
Download SKILL.mdSave it as
.claude/skills/debugging-failed-data-quality-checks/SKILL.md (or your agent's skills folder).- name
- debugging-failed-data-quality-checks
- description
- Finds out why a data quality check failed or errored, looks at the rows it matched, and recommends the fix. Also covers a materialized view refresh that the data quality gate did not publish. Use when asked why a check is red, what rows failed, why a view shows "Not published", why a view's data is stale after a refresh, or how to get a blocked refresh published. Trigger terms: failed check, failing rows, errored check, data quality failure, not published, blocked materialization, unpublished refresh, check keeps failing.
Debugging failed data quality checks
A check run ends in one of four states. Read the state first, because it decides where the problem is:
| Status | Meaning | Where to look |
|---|---|---|
failed | The query ran and the assertion found bad data | The data, or the assertion itself |
errored | The query could not run, so nothing was judged | The error text (never a data problem) |
skipped | The subject is gone | Whether the table or view still exists |
passed | The assertion held | Nothing |
row_count and freshness checks judge observed_value, not failed_row_count.
A failed row_count means the count fell outside its bounds.
A failed freshness means the newest row is older than the limit.
When to use this skill
- A check or a subject shows
failedorerroredand the user wants to know why - The user wants to see the rows a check matched
- A materialized view's latest run shows an error that starts with
Not published: - A view kept serving old data after a refresh, and the data quality gate is on
- Another skill (
authoring-data-quality-checksorauditing-warehouse-view-health) found a failing check or a blocked view and handed it off
Available tools
| Tool | Purpose |
|---|---|
posthog:data-quality-check-results | A check's recent runs, with compiled_query, error and the config it ran |
posthog:execute-sql | Re-run a run's compiled_query to see the failing rows |
posthog:data-quality-check-run | Run a check now |
posthog:data-quality-check-update | Fix an assertion or change its severity |
view-get | A view's definition and status |
view-run-history | A view's materialization runs and their errors |
view-run | Materialize a view again |
To find the failing checks, query system.information_schema.data_quality_checks for last_status IN ('failed', 'errored'), or system.information_schema.data_quality_health for a subject's verdict.
Workflow
Step 1: Read the run
Call posthog:data-quality-check-results for the check.
On the newest run, read:
statusanderrorcheck_configandcheck_severity: what the run asserted, which can differ from the check todaycompiled_query: HogQL that selects the failing rows. Forrow_countit returns the count instead, so judge that check byobserved_value.audited_staged_refresh: true when the run was part of a gated audit of a refresh before it was published. An errored run can carry it too, so readstatusfirst.
Retention clears compiled_query after 30 days.
For an older run, run the check again.
Step 2: Look at the failing rows
Run compiled_query with posthog:execute-sql.
An empty compiled_query means there is nothing to replay: retention cleared it, or a gated run could not read the view's definition.
Look at what it matched before you report anything.
A failure means one of two things: the data is bad, or the assertion is wrong.
The rows tell you which.
When audited_staged_refresh is true, the query does not read the published table.
It holds the view's definition in a WITH clause and reads the view's source tables now.
The sources may have changed since the run, so the rows and the count can differ from the run.
A query that now returns zero rows does not prove that the refresh was clean.
Compare with failed_row_count on the run.
Show full SKILL.md (411 more words)Show less
Step 3: Read an errored run
An errored run did not judge the data. Match the error text:
| Error text | Cause and fix |
|---|---|
The staged files could not be read, so this data was not audited. | The gate could not reach the refresh before publish. The refresh publishes without a verdict. Run the view again. |
Metric checks cannot audit staged data. | A metric check was part of a gated refresh. It runs on its own schedule instead. |
The check query returned no rows. | The aggregate query returned nothing. Run the check again and report it if it repeats. |
A check that reads another subject needs an initiator or author… | An automatic run of a custom_sql or relationships check has no user to run as. A manual run works. An edit to the check's assertion makes the editor its author. |
| A HogQL or ClickHouse error | A column name typo, a type mismatch, or a query that ran out of time. Fix the config, or add lookback_hours. |
Two messages come with skipped: The subject was deleted. and The subject no longer resolves.
The table or view is gone.
Delete the check or point it at the replacement.
Step 4: Understand a blocked refresh
When the team turns on "Block materialization on failing checks", a materialized view's error-severity checks run on each refresh before it is published. If one fails:
- The view's run shows an error that starts with
Not published:(seeview-run-history). - The previous version of the view keeps serving queries.
- Downstream views in the same DAG are skipped for this run.
- The view's schedule is not paused. The next scheduled refresh runs the checks again.
Warn-severity checks never block a refresh.
Step 5: Recover
Fix the cause, then prove it:
- Fix the upstream data, or fix the assertion with
posthog:data-quality-check-update. If the failure is real but must not block the refresh, changeseveritytowarn. - For a blocked view, call
view-runto materialize it again. Otherwise callposthog:data-quality-check-run. - Read
posthog:data-quality-check-resultsagain and confirm the newest run passed.
Important notes
- Do not change a check's severity or assertion only to turn it green. Confirm with the user first.
erroredis never evidence of bad data, andpassedon an empty table is not evidence of good data.- A check reports against its subject, but a
custom_sqlquery can read other tables. Read the query before you blame the subject.
Related
authoring-data-quality-checks: writing and choosing checksauditing-warehouse-view-health: finding failing materialized views
© PostHog, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in products/data_quality/skills/debugging-failed-data-quality-checks of PostHog/posthog-foss.
Open the folder on GitHubat commit 2c48221
Compare with similar skills
Debugging Failed Data Quality Checks next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Debugging Failed Data Quality Checks this skillPostHog/posthog-foss | 721 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Question2reportrefraction-ray/xalpha | 2.7k | — | ~3.2k | Automated safety check: Pass | MIT | |
| Dingo VerifyMigoXLab/dingo | 757 | — | ~741 | Automated safety check: Notes | Apache-2.0 | |
| Data Validationplatonai/Browser4 | 1.2k | — | ~896 | Automated safety check: Pass | Apache-2.0 | |
| Issues DeduplicationJetBrains/ideavim | 10k | — | ~1.3k | Automated safety check: Pass | MIT | |
| Pandas ProJeffallan/claude-skills | 12k | 1 repos | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
Dingo Verify
MigoXLab/dingo
A skill your agent uses when the user wants to fact-check an article or verify factual claims in a document.
Data Validation
platonai/Browser4
Validates data against common and custom rules (required fields, formats, ranges).
- Official
Issues Deduplication
JetBrains/ideavim
Handles deduplication of YouTrack issues. An agent skill from JetBrains/ideavim.
Pandas Pro
Jeffallan/claude-skills
Handles pandas DataFrame work: cleaning, merging, groupby aggregation, pivots, time-series resampling and memory tuning, with checks on dtypes, shapes and nulls.
Openbb Data Fetcher
monarchjuno/vibe-investing
Fetch financial, market, economic, fundamental, news, options, crypto, ETF, index, and macro data through the OpenBB Python interface instead of the OpenBB MCP server.
More from PostHog/posthog-foss
All 213 skills in this repo- Official
Authoring Log Alerts
PostHog/posthog-foss
Author useful, low-noise log alerts on services in a PostHog project.
- Official
Autoresolving PR Conflicts
PostHog/posthog-foss
Operating procedure for the conflict-autoresolver agent: sweep open PostHog/posthog PRs that conflict with master, resolve the trivial conflicts (generated artifacts deterministically, source…
- Official
Diagnosing Stacktrace Symbolication
PostHog/posthog-foss
Help users debug PostHog Error Tracking stack-trace symbolication for any supported platform — JavaScript/TypeScript web, React Native (Hermes), Android (Proguard / R8), or iOS / macOS (dSYM).
- Official
Exploring Apm Traces
PostHog/posthog-foss
Investigates distributed application performance using PostHog APM (OpenTelemetry span) data via MCP.
- Official
Exploring LLM Traces
PostHog/posthog-foss
Debug and inspect LLM/AI agent traces using PostHog's MCP tools.
- Official
Investigate Metric
PostHog/posthog-foss
Diagnose why a product metric changed (dropped, spiked, or plateaued) by orchestrating breakdowns, actors, paths, lifecycle, retention, and annotations queries.
Related
Works with
Categories
Questions about Debugging Failed Data Quality Checks
What does Debugging Failed Data Quality Checks do?
Finds out why a data quality check failed or errored, looks at the rows it matched, and recommends the fix. Debugging Failed Data Quality Checks is an agent skill from PostHog/posthog-foss, published by the product's own GitHub organization. Finds out why a data quality check failed or errored, looks at the rows it matched, and recommends the fix.
When should I use Debugging Failed Data Quality Checks?
Debugging Failed Data Quality Checks fits situations like: asked why a check is red; what rows failed; why a view shows Not published; why a views data is stale after a refresh.
How do I install Debugging Failed Data Quality Checks in Claude Code?
Run `npx skills add PostHog/posthog-foss --skill debugging-failed-data-quality-checks -a claude-code`. Or copy the skill folder (products/data_quality/skills/debugging-failed-data-quality-checks in PostHog/posthog-foss) into .claude/skills/debugging-failed-data-quality-checks in your project. Claude Code loads it when a task matches its description.
How do I install Debugging Failed Data Quality Checks in Codex?
Run `npx skills add PostHog/posthog-foss --skill debugging-failed-data-quality-checks -a codex`. Or copy the skill folder (products/data_quality/skills/debugging-failed-data-quality-checks in PostHog/posthog-foss) into .agents/skills/debugging-failed-data-quality-checks in your project. Codex loads it when a task matches its description.
Can I use Debugging Failed Data Quality Checks in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add PostHog/posthog-foss --skill debugging-failed-data-quality-checks -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/debugging-failed-data-quality-checks, .gemini/skills/debugging-failed-data-quality-checks, .github/skills/debugging-failed-data-quality-checks and .opencode/skills/debugging-failed-data-quality-checks in your project.
What does Debugging Failed Data Quality Checks need to run?
SKILL.md names no scripts, command-line tools or credentials: Debugging Failed Data Quality Checks is instructions for the agent only.
Does Debugging Failed Data Quality Checks access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Debugging Failed Data Quality Checks safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Debugging Failed Data Quality Checks use?
Debugging Failed Data Quality Checks is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Debugging Failed Data Quality Checks use?
About 2.1k tokens (SKILL.md is roughly 8.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Debugging Failed Data Quality Checks?
Skills that share tags, products or a category with Debugging Failed Data Quality Checks: Question2report (refraction-ray/xalpha, 2.7k stars), Dingo Verify (MigoXLab/dingo, 757 stars), Data Validation (platonai/Browser4, 1.2k stars) and Issues Deduplication (JetBrains/ideavim, 10k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Debugging Failed Data Quality Checks?
PostHog (a GitHub organization, an official publisher) maintains it in PostHog/posthog-foss, which has 721 GitHub stars. The repository holds 213 skills in this directory. The repository was last updated on October 7, 2026.
Source: PostHog/posthog-foss on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.