data-quality-audit
Audit a dataset for the quality problems that silently break analysis — missingness, duplicates, outliers, type and range errors, consistency, and freshness — and produce a prioritised fix list. Use when asked to assess data quality, audit a dataset, check data before analysis, or explain why numbers look off. Produces a structured quality report across the standard dimensions, the specific issues found (with the checks to run), severity, and how to fix each.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/data-quality-audit && cp -r /tmp/data-quality-audit/plugins/pm-data/skills/data-quality-audit ~/.claude/skills/data-quality-auditSKILL.md
# Data Quality Audit Skill Bad analysis usually starts with bad data nobody checked. This skill audits a dataset across the dimensions that matter, names the specific issues (and the exact check to confirm each), and prioritises fixes by how much they distort the answer. ## Working from a brief Given a dataset description, sample rows, or a schema, **produce the full audit anyway** — infer the likely issues for that kind of data and give the concrete check (SQL/pandas-style) to verify each. If given actual data, ground the findings in it. Never just say "check for errors"; specify them. ## Required Inputs Ask for (if not already provided): - **The dataset** — schema, a sample, or a description (what each column is, the grain) - **What it'll be used for** (the analysis/decision it feeds — focuses the audit) - **Source & freshness** (where it comes from, how often it updates) - **Known issues** the user already suspects ## Output Format ### 1. Summary Overall read (🟢 usable / 🟡 fix-first / 🔴 don't trust yet) and the one issue most likely to mislead. ### 2. Quality scorecard | Dimension | Check | Finding | Severity | |---|---|---|---| | Completeness | nulls / missing per key column | | | | Uniqueness | duplicate rows / keys | | | | Validity | type, format, range, allowed values | | | | Consistency | cross-field & cross-table agreement | | | | Accuracy | sanity vs known totals / reality | | | | Timeliness | freshness, gaps in the time series | | | ### 3. Specific issues For each real issue: what it is, **the check to confirm it** (a concrete query/snippet), why it matters for the intended use, and severity. ### 4. Fix plan (prioritised) Ordered by impact-on-the-decision: what to fix first, how (drop / impute / dedupe / cast / clamp / re-source), and what to flag rather than fix. ### 5. Guardrails 2–3 automated checks to add so these issues get caught next time (e.g. a not-null assertion, a row-count delta alarm, an allowed-values test). ## Quality Checks - [ ] Covers all six dimensions, not just missing values - [ ] Each issue comes with a concrete check to confirm it, not just a label - [ ] Severity is judged against the intended use of the data - [ ] Fix plan is prioritised by impact and says fix-vs-flag - [ ] Recommends guardrails to prevent recurrence ## Anti-Patterns - Only checking for nulls and calling it done - "Clean your data" with no specific issues or checks - Treating all issues as equally severe regardless of the decision - Fixing data silently with no record of what was changed
Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.
Structure AI and ML product decisions with the rigour of any product decision. Use when building AI-powered features, evaluating LLM integrations, designing AI products, or assessing AI readiness. Produces a complete AI product canvas covering problem definition, model approach, data requirements, evaluation framework, UX design, responsible AI checklist, and launch monitoring plan.
Transform feature briefs into structured design briefs that give designers the context they need before opening Figma. Use when asked to write a design brief, create a design handoff, brief a designer on a new feature, or translate a PRD into design requirements. Produces a brief with user goal, emotional context, success criteria, constraints, edge cases, and out-of-scope boundaries.
Design statistically rigorous A/B tests and interpret experiment results. Use when asked to design an experiment, run an A/B test, calculate sample size, interpret test results, or assess whether an experiment was successful. Produces a complete experiment design with hypothesis, sample size, run time, success criteria, and risk flags — or a results interpretation with ship/iterate/kill recommendation.
Synthesises user signals from multiple research sources into a unified, weighted insight brief. Use when you have data from interviews, support tickets, NPS verbatims, app reviews, or sales calls and need to reconcile contradictions, surface the underlying need behind requests, or answer 'what are users really telling us'. Produces ranked insights with confidence ratings, source weighting rationale, divergent signal analysis by user segment, and a research gap identification section.
Structure a product data analysis, metric deep-dive, funnel analysis, or cohort study. Use when asked to analyse product metrics, investigate a drop in conversion, explain a data change to stakeholders, or find the root cause of a metric movement. Produces a structured analysis with question, root cause, confidence level, and recommended action.
Interpret product metrics against goals and surface actionable signals. Use when asked to analyse product health, review key metrics, investigate a performance issue, produce a health report, or assess product-market fit signals. Produces a structured health report with RAG status, trend analysis, root cause hypotheses, and prioritised actions.
Structure a retention analysis, churn investigation, or engagement deep-dive for any product team. Use when asked to analyse user retention, investigate churn, measure DAU/MAU, or build a retention improvement plan. Produces a retention snapshot with root cause hypotheses, aha-moment correlation, and prioritised interventions.