Index of every page on this site: llms.txt
All skills
nimrodfisher avatar

/analysis-qa-checklist

@9449d36
Run it yourself

Pre-delivery quality assurance for analysis work. Use when reviewing analysis before sharing with stakeholders, checking for completeness, validating assumptions, or ensuring clarity of recommendations.

Use this Skill: https://skilld.dev/gh/nimrodfisher/data-analytics-skills/analysis-qa-checklist

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈56 tokens for metadata: the name and description. ≈410 when used: this file. ≈2k more on demand in 3 files.

Description uses 2.8% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈226 characters, or 2.8%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

When to use

Before sharing any analysis output with a stakeholder — dashboard, report, ad-hoc query result, model output, or written findings. Run this every time, not just for big projects. The cost of a post-delivery correction is always higher than the cost of a pre-delivery check.

Process

  1. Run automated checks — use scripts/qa_runner.py against the output file to catch numeric, structural, and formatting issues programmatically.
  2. Complete the logic checklist — work through references/qa_checklist_master.md section by section: question framing, data sourcing, transformations, statistical validity, findings, and presentation.
  3. Review for common errors — cross-check against references/common_analysis_errors.md; pay special attention to the top-frequency mistakes for the analysis type.
  4. Validate assumptions explicitly — for every assumption in the analysis, verify it has a source, is documented, and the output is sensitivity-tested where the assumption is uncertain.
  5. Check the narrative — confirm the conclusion follows from the data, caveats are stated, and the recommendation is actionable.
  6. Record sign-off — complete assets/qa_signoff_template.md with reviewer, issues found, resolution status, and delivery decision.

Inputs the skill needs

  • Output file to review (CSV, notebook, SQL result, or written doc)
  • Original analysis question / brief
  • Name of reviewer and intended audience

Output

  • QA runner report (automated flags)
  • Completed checklist with pass/fail per section
  • Signed-off qa_signoff_template.md confirming delivery readiness

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo4 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    The skill establishes a quality assurance workflow for data analysis deliverables, consisting of a manual checklist, error references, and an automated data validation script. No security issues or malicious patterns were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 9449d36. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated 7 months ago

README badge

README badge for nimrodfisher/data-analytics-skills/analysis-qa-checklist